On Saturday 03 March 2007 20:39:01 Michal 'vorner' Vaner wrote: > But there may be situations where this possibility could be used in some > other ways. You may want nostrip for few packages only (need of debug > symbols, and you do not want to have them for the whole system), or the > make check fails for one package you critically need just now and have > no other choice than to use it anyway. > > In my opinion, it should be possible to configure all the variables > according to the package name.
The cases you've mentioned here (nostrip, splitdebug, test) are handled on the
bash side of portage which means disabling them in /etc/portage/bashrc on a
per package basis (or in /etc/portage/env/*) is possible.
# grep -C 1 env $(portageq portdir)/profiles/base/profile.bashrc
for conf in ${PN} ${PN}-${PV} ${PN}-${PV}-${PR}; do
[[ -r ${PORTAGE_CONFIGROOT}/etc/portage/env/${CATEGORY}/${conf} ]] \
&& . ${PORTAGE_CONFIGROOT}/etc/portage/env/${CATEGORY}/${conf}
done
So e.g this would work:
# mkdir -p /etc/portage/env/${CATEGORY}/ && \
echo 'FEATURES=nostrip' > /etc/portage/env/${CATEGORY}/${PN}`
FEATURES=userpriv, however, is handled on the python side and hence that won't
work. In order to persuade someone to change this you'll probably need a
better use case than -userpriv which ultimately should be either fixed or
restricted in the ebuild.
> But in other words, if I want such functionality, I have to hack it in
> somehow. Or I will have a look at paladius, or how is that thing called
> (will test it in virtual machine first…)
eix can help you if even if you cannot spell... ;)
# eix --fuzzy paladius
[I] sys-apps/paludis
Available versions: (~)0.16.2 (~)0.18.1 (~)0.20.0 (~)0.20.1
Installed: 0.20.1 [...]
Homepage: http://paludis.pioto.org/
Description: paludis, the other package mangler
--
Bo Andresen
pgpqXs88lId3C.pgp
Description: PGP signature
