He's not dead, he's resting
Paludis is about Choices
Paludis 0.32 will include a new mechanism called ‘choices’. Examples of choices on Gentoo include use flags, the various
USE_EXPAND settings (
video_cards and so on) and a shiny new setting called
build_options. For use flags and the
USE_EXPAND settings, there’s no change from a user perspective, and you can carry on using
use.conf as normal — choices are merely a more general mechanism for handling package settings.
On Exherbo, things do change a bit, and if you’re one of those naughty people who ignored the “Exherbo has no users” warning you’d better have been paying attention.
So what’s this
build_options thing? You’ll see it cropping up for most packages:
* net-print/cups::gentoo [U 1.3.8-r1 -> 1.3.8-r2] <target> Reasons: app-text/ghostscript-gpl-8.62:0::installed, net-print/foomatic-filters-3.0.20080507:0::installed, 2 more X acl -avahi -dbus -gnutls -java jpeg -kerberos -ldap pam perl -php png ppds python -samba -slp ssl -static -tiff -xinetd -zeroconf LINGUAS: -de en -es -et -fr -he -id -it -ja -pl -sv -zh_TW build_options: -optional_tests split strip
Packages using 0-based EAPIs will usually have three build options:
optional_tests. This handles what
--checksused to do. If this choice is set,
src_testwill be run.
split. This used to be
strip. This used to be
Packages using kdebuild-1 or exheres-0 will have
recommended_tests instead of
optional_tests, which defaults to being enabled rather than disabled.
Despite what you might expect from older Paludis versions, these are not use flags. You can set them in
use.conf, though — this means you can select whether to run tests or whether to keep debug information on a per-package basis, which was tricky to do with the old commandline options.