Re: execline-1.05 non-root installation problem

Laurent Bercot <[email protected]> wrote:
>  then sp-install modifies only the first line in depend_*.

Right.

> Making my packages comply to that would mean deeply reworking
> my build system, and frankly, I'm fed up with working on build systems
> instead of useful code.

I'm sure I would be too, if I were editing all my build scripts by
hand. :)

>  Or that would mean two or three depend_foobar files per dependency,
> which I'll do if we can't find another agreement, but I find it
> cumbersome for me _and_ for the users.

They all have a common prefix for the containing package, though,
don't they?  I think configurability of the prefix is all the user
really needs (or even wants).  Then the build scripts can use
-I"$configured_prefix"/include, etc.  That's essentially how I do it
(though, as I mentioned, I use a symlink instead of a shell variable).
Even if the files are split up for sharability, etc., there's no
reason the user can't also create symlinks so the package appears to
be all in one place.  If you make different parts of the same package
separately configurable, then in the common case where the package is
all in one place, the user has to express the same information (i.e.,
the custom prefix) multiple times.

>  If you make sp-install handle every line in depend_* until the
> first empty line (which still allows for comments below the useful
> lines), then no problem.

Yes, though that will complicate the code.  I'm not sure when I'll get
to that.


paul