| 1 |
On Wed, 29 Jun 2011 07:38:45 +0100 |
| 2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Wed, 29 Jun 2011 02:36:05 -0400 |
| 5 |
> Mike Frysinger <vapier@g.o> wrote: |
| 6 |
> > On Wed, Jun 29, 2011 at 02:14, Ciaran McCreesh wrote: |
| 7 |
> > > On Wed, 29 Jun 2011 02:07:52 -0400 Mike Frysinger wrote: |
| 8 |
> > >> /etc/init.d/functions.sh has existed for the last decade, and was |
| 9 |
> > >> long ago decided as the canonical public entry point for scripts |
| 10 |
> > >> external to baselayout (as opposed to a path in /sbin/). it isnt |
| 11 |
> > >> going anywhere, and painting it as something in flux at this |
| 12 |
> > >> point is disingenuous. |
| 13 |
> > > |
| 14 |
> > > Is it documented and specified? If not, can it be? |
| 15 |
> > |
| 16 |
> > the file path ? or the API that it provides ? |
| 17 |
> |
| 18 |
> Both. There's code in Paludis that duplicates a bunch of that stuff |
| 19 |
> simply because I wasn't sure what I could and couldn't rely upon. |
| 20 |
|
| 21 |
I'm not sure if it is a good idea to source a script mangling PATH |
| 22 |
there. |
| 23 |
|
| 24 |
-- |
| 25 |
Best regards, |
| 26 |
Michał Górny |
Archives