Last days I reinstalled my Gentoo in my desktop computer, a Dell Dimension C521 using the new package handler pkgcore.
The last months I’ve use official portage, and also new replacement called paludis. The main advantage of this one is being written entirely in C++, so paludis is very fast, but also you can detect some problems when you need to compile some “specials” packages, such qemu, which requires to be compiled with gcc3. If you compile paludis with another version of gcc, you can find a beauty error related to dynamic linking. Obviously, you can solve this problem by hand or with sonme tricks 
, but I don’t like tricks in production machines.
hario 1:58 am on 15 May 2008 Permalink |
OMG! The configuration file is a good reason not to use pkgcore… yet
I took a quick look at Pkgcore recently, but for now Paludis is doing a good job for me, so I will stick with it at least until a saner configuration syntax is added to Pkgcore – and no, the Portage compatibility is not enough for me, hehe.
Donnie Berkholz 8:45 am on 17 May 2008 Permalink |
I don’t even use pkgcore.conf, just the existing make.conf from portage.
ajdiaz 4:22 pm on 17 May 2008 Permalink |
Wel, I want to manage my repositories using pkgcore directly, without layman (only for testing
) and I think that need pkgcore.conf to do it. 
Am i right to do so?
Brian Harring 4:34 am on 6 December 2008 Permalink |
The ini format you used is pretty damn low level- frankly there isn’t any reason to drop down to that level unless you actually need to do something fairly crazy.
Even then, you can intermix formats easily enough- in other words you could do an ini override of make.conf for example.
Either way, ini is not the intended format for majority of users- it’s pretty much the intended format for if you need to do something fairly hanky (remote configuration, complex cache setups, etc).