| 1 |
On Sunday 05 March 2006 23:38, MIkey wrote: |
| 2 |
> |
| 3 |
> That is of course always an option. |
| 4 |
> |
| 5 |
> But, I have a dream... That some day, some way, I will be able to |
| 6 |
> control _everything_ I need relating to building and installing via USE |
| 7 |
> flags and package.use. |
| 8 |
> |
| 9 |
> I don't think using _anything_ in the environment should ever be |
| 10 |
> allowed because there is no way to track it during upgrades or |
| 11 |
> automated building (catalyst, installing from pre-packaged binaries, |
| 12 |
> for examples). Not to mention the environment is not exactly clean. |
| 13 |
> Keeping track of the myriad of ways you can alter a package |
| 14 |
> build/install is a headache, I would prefer it all be done through one |
| 15 |
> consistent interface... From what I can tell, the use of |
| 16 |
> FEATURES="noman nodoc noinfo" is being deprecated anyway. |
| 17 |
|
| 18 |
Take a look at the options offered by a custom /etc/portage/bashrc. One |
| 19 |
can do almost anything there. You can have it read in configuration files |
| 20 |
and whatever. The documentation is kindof lacking, but most portage |
| 21 |
features could actually be removed in favour of a custom bashrc. It would |
| 22 |
just confuse the hell out of users. |
| 23 |
|
| 24 |
Paul |
| 25 |
|
| 26 |
-- |
| 27 |
Paul de Vrieze |
| 28 |
Gentoo Developer |
| 29 |
Mail: pauldv@g.o |
| 30 |
Homepage: http://www.devrieze.net |
Archives