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