> Date: Fri, 15 Aug 2014 15:52:29 -0500 > From: Bruce Dubbs <[email protected]> > To: BLFS Development List <[email protected]> > Subject: Re: [blfs-dev] postlfs/profile.html : ~/bin append/prepend > > akhiezer wrote: > > > On svn blfs page: > > > > http://www.linuxfromscratch.org/blfs/view/svn/postlfs/profile.html > > > > , in section '/etc/profile.d/extrapaths.sh' there is: > > > > pathprepend ~/bin > > > > , and in section '~/.bash_profile' there is: > > > > append $HOME/bin > > > > Also, that 'append()' function in '~/.bash_profile' looks like it would > > prefix a ':' if starting PATH was either empty or equal to the dir that > > one is trying to append. > > The very first variable set in /etc/profile is > > export PATH=/bin:/usr/bin > > So if you are following the book, PATH will always be set. FBBG. > > Yes, that construct is bash specific. >
Yes, was taking the context as-read. The (fairly obvious?) point was that in one place you pre-pend and in the other ap-pend. Educationally, perhaps better to be consistent there. As for the empty-vars/&c: yes, again, taking as-read the book context. But the (again, fairly obvious?) point is that as a piece of 'education', it's not good to have a function that presumes such input - and indeed when it's so readily fixed-up. Follow good coding practices: good coding practices good. Akhiezer > -- Bruce > -- -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
