You are not logged in.
Pages: 1
Has anybody built Arch from source? Does anybody build packages from ABS (doesn't install it from official repo)?
Sorry, if my English is not very well.
Offline
you may find this thread interesting: http://bbs.archlinux.org/viewtopic.php?id=48957
All design goals must be phrased in such a way that it is hard to use them as slogans to justify stupidity.
Offline
Does anybody build packages from ABS (doesn't install it from official repo)?
I do that for some performance-critical packages like mplayer or for packages which aren't up to date yet, but from which i need the new features anyway(wine and the nvidia-drivers for instance). Actually building something source instead of binary is quite simplified by using yaourt(search the forums), since you only have type "yaourt -Sb package" to do it, although this is currently broken for community packages due to the repo migration from cvs to svn.
I don't see much sense in doing that for all packages though, because the difference from i686 to your architecture should not be noticable in most cases, especially if you don't have a very new chipset. This in my opinion waste of time when compiling _everything_ was actually the main reason that made me leave gentoo for archlinux.
Last edited by Asgaroth (2008-06-18 16:57:47)
Offline
When rice is the sole reason for compiling from source naturally it's a waste of time. Arch is "i686" optimised but nobody around here seems to comment that there's pretty much 0 performance gain as far as regular packages are concerned. The only thing Arch manages to achieve is to not let i486 / i586 users run the distribution.
Offline
We have come a long way. I don't see anyone running anything lower than a P3. Even third-world nations have low-cost machines with post-Y2K architecture.
I need real, proper pen and paper for this.
Offline
Pages: 1