hi,yap, this is my first time with debian, so i'm a little lost here.i found my sources.list a little too much empty :Phow can i learn a little about debian repos, in relation to #!, what's good to do, and what it's not, and so on?
ethail wrote:I think you should consider :a) You need a Trusted User or Arch Developer to adopt it in order to be moved from AUR to [community] or [extra]b) If no TU or Dev is interested on it, it won't get to binary repos.b1) Some packages will never get to the repos whatever the number of votes they have (i.e.
I've seen where compiling programs in Debian is seen as a "dirty way to do things" in Debian. Is there any reason for this logic? After I compile things in Debian apt sees it and I can remove the package that way if I want, so it doesn't seem like it just floats in the ether.I'm just compiling programs (ex.
XPERIA ARC/S JELLY BEAN 4.1.2 V01 VERY STABE AND NICE V02
Rom Infomation
ROM:
V01..........................(SORY IT DELETED BY ADMIN BECAUSE I USED PAIR OF SOFTWARE)
- This rom not base from FXP rom.
I'll start at the end with #4. Of course on the arch forums you will get people who are biased towards liking arch - but I think if you ask in other communities you will regularly hear that arch's package management system is its greatest strength. Pacman is the primary tool for this, but we also have makepkg for things in the Arch User Repository (AUR), and the Arch Build Sy
I have an Asus G75VW laptop with Arch Linux Kernel-CK x64 and the official Nvidia (CK) driver installed. (Newest package versions as of yesterday, no testing repos.) When I run startx, the Nvidia logo flashes briefly, and then the screen turns black and the backlight turns off.
That's a big project, it takes about 30 mins compile by "make -j4" on Ubuntu.Compare to Ubuntu, Arch take more 20 mins compile time!The only different thing is Arch installed in SSD (project code too), Ubuntu in traditional disk.Due to the project can't compile with 64bit system, Arch and Ubuntu all is 32bit OS.The Arch already installed PAE kernel from AUR.Anyone can help?
In my opinion, docs should only be included in a package if they are small, maybe a few hundred kilobytes, and should otherwise be split into seperate $pkgname-docs packages. Only about 22 packages in the repos use seperate -doc or -docs packages right now.
If you do not have time to read the wiki and manual, you will experience a great deal more breakage - and waste a lot more time - than you need to.That said, if you did not have time to keep Debian up to date, why on Jupiter did you choose Arch?I do not mean to be unwelcoming. Of course, you are most welcome, if you really want to use Arch. But do you?
Email this page
