| Summary: | Add an option to apply an /etc/portage/env file from a command-line option | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Fat-Zer <fatzer2> |
| Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
| Status: | UNCONFIRMED --- | ||
| Severity: | enhancement | CC: | gentoo, mva |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
It would be very convenient if there were an option to apply an /etc/portage/env file from a command line. Imaging you need to one-time build a single package foo/bar or a group of packages for a debug/testing. In that case you have to do something like: CFLAGS="-Og -ggdb" CXXFLAGS="-Og -ggdb" FEATURES="splitdebug installsources" emerge foo/bar Or you could put this into files: /etc/portage/env/debug.conf: CFLAGS="-O0 -ggdb" CXXFLAGS="-O0 -ggdb" FEATURES="splitdebug installsources" /etc/portage/package.env: foo/bar debug.conf and than `emerge foo/bar`. But this uproach has some disadvantages: - It's too permanent (in case you want to debug the package right now, not on the next rebuild) - It requires root access (which isn't needed i.e. if you want just to just try `ebuild foo/bar compile` with specific flags ) I wish there were an option so It would be possible to apply an env config from a command line i.e. `emerge --env debug.conf foo/bar` and/or an env var: `PORTAGE_ENV=debug.conf ebuild /path/to/foo/bar/bar-0.ebuild compile`. Reproducible: Always