| 1 |
On Thursday 26 May 2005 07:47, Jonas Geiregat wrote: |
| 2 |
> Alec Warner wrote: |
| 3 |
> >-----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
> >Hash: SHA1 |
| 5 |
> > |
| 6 |
> >Jonas Geiregat wrote: |
| 7 |
> ><snip ChrisWhite> |
| 8 |
> > |
| 9 |
> >>I gave this a quick look, and aren't you talking about bash scripts in |
| 10 |
> >>general rather then .bashrc files using /etc/portage/bashrc as reference |
| 11 |
> >>for this document. |
| 12 |
> >>Also I can't see the real use , that's why I started reading then |
| 13 |
> >>quickly scanned through it .. and now I'm writting this email .. |
| 14 |
> > |
| 15 |
> >normal bash scripts aren't sourced by portage when ebuilds are being |
| 16 |
> >processed. Only PORTAGE_BASHRC ( current /etc/portage/bashrc ) is |
| 17 |
> >sourced. Thus you can do cool stuff like print debug info, over-ride |
| 18 |
> >default functions, and otherwise other fun stuff that normally would be |
| 19 |
> >a complete PITA, especially if you don't know portage internals well. |
| 20 |
|
| 21 |
Not knowning portage internals well means that this file should be off limits. |
| 22 |
|
| 23 |
> No such file on my system, is that the reason why I should use the cvs |
| 24 |
> version of portage, so the new version will source /etc/portage/bashrc |
| 25 |
> when it comes out of cvs ? |
| 26 |
|
| 27 |
You need to create it yourself. |
| 28 |
|
| 29 |
Regards, |
| 30 |
Jason Stubbs |
Archives