You are not logged in.
Pages: 1
I plan on reinstalling Arch, here's my question:
What's the easiest and minimalist way to use arch as a source distro. (like gentoo)?
Personally, I'd rather be back in Hobbiton.
Offline
I plan on reinstalling Arch, here's my question:
What's the easiest and minimalist way to use arch as a source distro. (like gentoo)?
ABS(Arch Build System) plus source AUR packages. Only way to know if the AUR is using the source of a program is to check the PKGBUILD(which you should do in the first place, anyway). I believe that there is a way to customize the systems CFLAGS and CXXFLAGS so that you can optimize according to your processor, which is the main benefit of recompiling anyway, but someone else is going to have to say what file that is that contains such info, since I've never done that myself...
17:23 < ConSiGno> yeah baby I release the source code with your mom every night
17:24 < ConSiGno> you could call them nightly builds if you know what I mean
Offline
You might be interested in pacbuilder, which you can also get from the aur.
Edit: Building options like CFLAGS are in /etc/makepkg.conf
Last edited by Statix (2009-11-08 03:49:21)
Madly in love with Arch64, Openbox, DotA, and of course... penguins!
Happy to help if you're not a Help Vampire. Use your wonderful resources like ArchWiki, Google, and our wonderful search page.
Offline
I used to use gentoo, but I don't consider having all the build scripts minimalist. The benefit of gentoo is that it makes detailed configuration easy, but it is not, at least in my definition, minimal.
Offline
yaourt will also build from both AUR and ABS if you tell it to.
yaourt -Sb <packagename> #to compile from ABS
yaourt -S <packagename> #to build packages from AUR (also to install binarys from the main repos)
Nai haryuvalyë melwa rë
Offline
Why use yaourt? I mean is there any reason? Faster? Nope. Less typing? How?
You type:
yaourt -S packagename and here you will have to type
makepkg -s PKGBUILD
same amount of effort I think and much more secured.
Offline
I used to compile everything (and i have ALOT of pkgs) for like 6 months out of spite to see if i could.
Conclusion... utter waste of time!
ABS is there if you want to _change_ something, not to recompile the whole system when arch provides excellent pkgs already.
Last edited by Chrysalis (2009-11-08 06:20:14)
Offline
I use ABS to compile a few "not so popular nd hence not upgraded faster" packages, eg-> clamav. It's still on version 0.95.2 in repo but I compiled 0.95.3
Another example is branding of firefox. Also a few other packages I like to keep more up-to-date.
Offline
I used to compile everything (and i have ALOT of pkgs) for like 6 months out of spite to see if i could.
Conclusion... utter waste of time!
ABS is there if you want to _change_ something, not to recompile the whole system when arch provides excellent pkgs already.
I want answers; not opinions. So basically, I can use pacbuilder to keep everything up to date, correct? Because I'm aware that upgrading from a abs package with pacman will replace the source with a binary.
Personally, I'd rather be back in Hobbiton.
Offline
Yes, you can use pacbuilder to keep your system up to date; I have had an all-source pacbuilder system in the past.
Offline
Why use yaourt? I mean is there any reason? Faster? Nope. Less typing? How?
You type:
yaourt -S packagename and here you will have to type
makepkg -s PKGBUILDsame amount of effort I think and much more secured.
I agree, another benefit to makepkg is storing package cache, which yaourt doesn't seem to do.
Offline
I want answers; not opinions.
And in an ideal world, that's what you would get. This, however, is a public discussion forum, and Chrysalis, along with anyone else who's sufficiently interested, is entitled to express his opinion - just as you are entitled to ignore it.
Offline
sHyLoCk wrote:Why use yaourt? I mean is there any reason? Faster? Nope. Less typing? How?
You type:
yaourt -S packagename and here you will have to type
makepkg -s PKGBUILDsame amount of effort I think and much more secured.
I agree, another benefit to makepkg is storing package cache, which yaourt doesn't seem to do.
Well there is a way which requires a little bit of effort, after you let yaourt compile the package for you [installing all the dependencies,etc.] just before it asks you if you would like to "Continue with the installation [y/n]?" you can go to the /tmp/yaourtbuild/ folder and copy the package cache to somewhere else and then continue with the installation. As I have noticed that yaourt automatically cleans the temp working directory.
Offline
Pages: 1