Re: [Linuxcoe-devel] Update on packaging

[Bryan G. <Bry...@HP...>]

Bruno,

I am a little short on context for some of the following, but will
still make educated guesses.

> > # from previous configure run
> >         export prefix=/var/www/linuxcoe-sd
> >         export exec_prefix=${prefix}
> >         export bindir=${exec_prefix}/bin
> >         export sbindir=${exec_prefix}/sbin
> >         export libexecdir=${exec_prefix}/libexec
> >         export datadir=${datarootdir}
> >         export datarootdir=${prefix}/share
>
> Isn't the order here reversed ?

These look ok-ish to me (assuming they match what you specified for
configure).  Not sure what you mean about "order"?

> >         export MKISOFS=SKIP
> >         export SENDMAIL=SKIP
> >         export APACHE=SKIP
> >         export APACHECTL=SKIP,
> >         export APACHE2CTL=SKIP
> >
> > Shouldn't those SKIP be replaced by what is also in binaries.pm ?

If all of the above is in config.state, these look ok, as they were
meant to capture what you "configured" for later reference.  And you
are, in fact, correct, that the post-install will only modify the
binaries.pm file to migrate SKIP -> paths to binaries (at least those
it can now find on the target install system).

> Still answering myself. Probably not. Because that script is especially
> used to create the correct binaries.pm, so point is void.
> 
> > The diff with the working machine gives (< works, > doesn't)
> >
> > 13c13
> > <       export localstatedir=/var/lib
> > ---
> > >       export localstatedir=/var
> 
> That still look strange to me.

Hmm, don't you specify the --localstatedir=<SomeDir> in your package
builds ?  FWIW, I typically don't for either CVS/tar installs or debian
package builds (as the default actions do the "right" thing for me).

bryang