Summary: | DOC: Assign of specific CFLAGS per ebuild | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Florian Evers <florian-evers> |
Component: | Documentation | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | alan.schmitt, deathwing00, ed, kanelxake, langthang, robmoss, schmitt, swegener |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic.php?t=173377 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 51095 | ||
Bug Blocks: |
Description
Florian Evers
2004-05-14 08:53:22 UTC
What about CXXFLAGS? What about MAKEOPTS? What about LINGUAS? I'd like to support and, if necessary, implement the request. good feature, but i don't think that many people really need this. if you really need this you can do it de following way: from man 5 portage: /etc/portage/ bashrc If needed this file can be used to setup a different environment for ebuilds than the root environment. Syn- tax is the same as any other bash script. if you put something like this in /etc/portage/ bashrc for MY_ENV in ${PN} ${P} ${PF}; do if [ -f /etc/portage/env.d/${CATEGORY}/${MY_ENV} ]; then . /etc/portage/env.d/${CATEGORY}/${MY_ENV} fi done you'll be able to set variables via /etc/portage/env.d that influences the ebuild. files will be sourced in this order, taken openoffice as a example: 1. /etc/portage/env.d/app-office/openoffice 2. /etc/portage/env.d/app-office/openoffice-1.1.0 3. /etc/portage/env.d/app-office/openoffice-1.1.0-r2 you can put for example LANGUAGE=<language code e.g. GER> in /etc/portage/env.d/app-office/openoffice and openoffice will alway be built in that language. that's what i'm already doing for several months. :) some variable won't work, e.g. LINGUAS because it is expanded to use flags before /etc/portage/bashrc will be sourced. sven However /etc/profile.env overrides some settings including (in my case) LANGUAGE. See the linked bug 51095 for the obvious solution. We should probably have a tips and tricks section for environment vars. Comment #3 should go in it. i dont think users should have to learn bash and/or jump through hoops to accomplish this (which comment #3 requires ... not a bad idea, i just dont think it's for everyone) Nicholas, could you modify portage so that /etc/portage/bashrc is sourced before environment variables e.g. LINGUAS are be expanded to USE flags? Also I'm thinking about a feature like I proposed in bug 51370 comment 7. This would clean out /etc/env.d which is sometimes used for the wrong purpose in my opinion. *** Bug 63861 has been marked as a duplicate of this bug. *** Solar's bashrc accomplishes this nicely... http://dev.gentoo.org/~solar/portage_misc/bashrc Why isn't solar's bashrc feature for package.cflags buit-in portage? It's been a year since this was proposed in this bug ticket... 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. ;) *** Bug 114112 has been marked as a duplicate of this bug. *** Duping. *** This bug has been marked as a duplicate of 44796 *** |