Summary: | Add incremental support for revdep-rebuild enviroment variables | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Paul Varner (RETIRED) <fuzzyray> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | 2.0 | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://bugs.gentoo.org/show_bug.cgi?id=62644 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paul Varner (RETIRED)
2005-06-18 09:54:37 UTC
i dont see the point those variables are *only* used by revdep rebuild so exporting them via env.d entries is wrong you should setup a system where packages can dump files into say /etc/portage/revdep-rebuild/ and then have your revdep-rebuild script parse those The point is to make it easier for both devs and users to be able to customize revdep-rebuild to match their gentoo systems and thus hopefully reduce some bug reports. I have had requests to be able have these variables in the profiles and environment from other devs. To me, the best method was to let portage handle that since it already does it for other variables. Having said all that, I'm not attached to any specific method of implementation and I won't be offended if this enhancement request is rejected. to 'let portage handle it' means to install env.d entries and have that variable make it into profile.env which all users will have in their environment which is wrong the amount of work to have an ebuild guy install a custom file into /etc/env.d or into /etc/portage/revdep-rebuild is the same ... it would just take a bit of work on your part to have revdep-rebuild add all the files together Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;) Reopening to resolve as wontfix. I'm going with Spanky's suggestion. revdep-rebuild will use its own files instead of /etc/env.d files. |