Re: [gentoo-portage-dev] backend support for FEATURES=debug-build (again)
Mike Frysinger wrote: > yes, it's a user-friendly interface issue: > we have *no* *sane* way of doing a debug emerge I don't find this particular implementation very user-friendly either, since AFAIK the FEATURES settings still aren't remembered or settable on a per-package level. That's why x-modular.eclass has USE=debug to accomplish the same thing. Thanks, Donnie signature.asc Description: OpenPGP digital signature
Re: [gentoo-portage-dev] backend support for FEATURES=debug-build (again)
On Wednesday 10 May 2006 12:21, Zac Medico wrote: > Mike Frysinger wrote: > > no one responded last time about this patch so lets try one more time :P > > > > backend support for FEATURES=debug-build ... no hooks/hacks/etc... > > included here to handle a user interface `emerge --debug-build` > > This type of thing can already be done quite easily via > /etc/portage/bashrc. so ? you cant expect every user who wants to do debug building to add hacks to their own bashrc > Is it really necessary to add support for small > environment tweaks like this on the python side? yes, it's a user-friendly interface issue: we have *no* *sane* way of doing a debug emerge -mike -- gentoo-portage-dev@gentoo.org mailing list
Re: [gentoo-portage-dev] backend support for FEATURES=debug-build (again)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Frysinger wrote: > no one responded last time about this patch so lets try one more time :P > > backend support for FEATURES=debug-build ... no hooks/hacks/etc... included > here to handle a user interface `emerge --debug-build` > -mike This type of thing can already be done quite easily via /etc/portage/bashrc. Is it really necessary to add support for small environment tweaks like this on the python side? Zac -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEYhMC/ejvha5XGaMRAu8pAJ0S4sAf+G41GYA0M5XNG1HEkvbmfwCeIAwB gXd5JjURKQYAJPKYBUYkrr8= =zSZM -END PGP SIGNATURE- -- gentoo-portage-dev@gentoo.org mailing list
