Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 82189 - Special File for Custom ENV vars to pass options to ebuilds.
Summary: Special File for Custom ENV vars to pass options to ebuilds.
Status: RESOLVED DUPLICATE of bug 44796
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Ebuild Support (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-15 17:53 UTC by Doug Goldstein (RETIRED)
Modified: 2005-07-17 13:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Doug Goldstein (RETIRED) gentoo-dev 2005-02-15 17:53:47 UTC
Let me give you an example first... Take lirc for instance. To compile it you need to compile it like such..

LIRC_OPTS='--with-x --enable-debug --with-driver=hauppauge --with-major=61 --with-port=none --with-irq=none' emerge lirc

a bit long for a command line flag... what happens if you accidently emerge without all that (as I have done) and it's a headless box with just a remote control.. Well it doesn't work anymore.. I need to ssh in and correct it.

Users and Devs have long come up with alternate places to put this stuff. One example is /etc/make.conf, another is /etc/env.d/, yet another I've seen is .bashrc.

None of that makes sense... what I propose is to add a file, /etc/portage/env.opts

where users can specify these FLAGS. There a several other packages that exist like this. This also will allow other overrides in packages which aren't as well noted.

Reproducible: Always
Steps to Reproduce:
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2005-02-15 18:06:58 UTC

*** This bug has been marked as a duplicate of 44796 ***