Re: execline-1.05 non-root installation problem

Laurent Bercot <[email protected]> Tue, 29 Jul 2003 18:26:14 +0200
Newsgroups gmane.comp.djb.package
Message-ID <[email protected]>
> I could do that, but it would be easier if each dependency were
> configured in a separate file, since sp-install already has code to
> handle that.  I also think it's more useful to users that way.  E.g.,
> idtools has conf-compile/depend_bglibs and
> conf-compile/depend_skalibs.  Among other things, this lets the build
> system track changes more precisely, so rebuilds don't do unnecessary
> work.  Would it take much work to convert your packages to this
> scheme?

 In a certain sense, yes.
 If I understand the relevant part of sp-install correctly, i.e.

###
    for x in "$dir"/conf-compile/package_home "$dir"/conf-compile/depend_* \
             "$dir"/src/conf-home; do
      test -f "$x" || continue
      tmp=`sed q < "$x"`
      if match_ '$SP_ROOT/*' "$tmp"; then continue; fi
      { echo_ "$SP_ROOT$tmp"
        sed 1d < "$x"
      } > "$x{new}"
      mv -f "$x{new}" "$x"
    done
###

 then sp-install modifies only the first line in depend_*. Which won't
do for my system, since I usually have two (and occasionally three)
lines per dependency (include, library, and sometimes sysdeps).
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.
 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.
 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. Your depend_* files will have slightly
different semantics than mine, but that shouldn't matter for SP_ROOT.


> Some dependencies may be installed in $HOME/package while others are
> in /package, etc., so I think it's best if packages let each
> dependency be independently configurable, even though sp-install
> doesn't currently take advantage of that.

 conf-compile/import lets you configure each line independently. :)

-- 
 Ska