Jonas Geiregat posted <[EMAIL PROTECTED]>, excerpted below, on Thu, 26 May 2005 00:47:06 +0200:
> Alec Warner wrote: >> >>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. >> > 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 ? The purpose is simply to provide a method for local portage users aka local system admins to modify portage's behavior, if desired, without delving into its innards. Thus, it won't exist by default, as it then would be part of the default portage, not simply a method by which the local Gentoo user can change portage's behavior without digging into portage itself. <g> -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-dev@gentoo.org mailing list
