Re: [Linuxcoe-devel] Update on packaging

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

Bruno,

On Fri, Nov 16, 2007 at 07:01:14AM +0000, Cornec, Bruno (Linux Consultant) wrote:
> Bryan Gartner said on Thu, Nov 15, 2007 at 03:46:55PM -0700:
> 
> > > What about adding  anoption to configure (for packager, which means me
> > > atm) allowing for bypassing those checks ? That would of course not be
> > > on by default.
> > >
> > > Would that work for you ?
> >
> > Those kinds of checks are already there, IIRC (./configure --help)
> >
> >   --without-APACHE        skip auto-integratation with Apache webserver
> >   --without-SUDOERS       skip auto-integration with sudo

Okay I have now setup:

      --without-APACHE	      skip auto-integration with Apache webserver
      --without-APACHECTL     skip check for apache*ctl
      --without-SUDOERS	      skip auto-integration with sudo
      --without-SUDO          skip checks for apache*ctl

I believe that the --without-APACHECTL and --without-SUDO will
do what you requested.

> I want the integration. What I don't want is the check that apache
> exists.
> 
> With the integration activated it will make a symlink to LInuxCOE.conf
> httpd file correctly, anf thus when I install the package on a machine
> with an apache server (which is a requirement of my package) it just
> works. sudo is indeed less a problem as it's nearly mandatory in distro
> nowadays.

Actually there are a whole set of commands that are beyond mandatory
in a base installation that SystemDesigner relies upon.  You just
happen to have most of these in your qemu packaging building instances ;)

If you peek at configure.ac, you will see these broken out by groupings.
In reality, I should do similar checks for all those not required by
FHS, however I drew the line at Apache/Sudo since those two I have to
directly integrate with for a functioning SystemDesigner.  The other
checks were left as a failure if not found.

In general, this seems to be somewhat grey area WRT to package builders.
For the debian crowd, this seems to be handling quite gracefully, as
any package build environment starts at the same base level, and uses
the package description to fill in build dependencies, before trying
to create a given package.  I am less familiar on how the rpm-based
distributions handle their package builds.

> If I remove the integration, I'll have to add it myself and won't be
> abelt to use the post-action script. Which is of course another
> possibility.

With any luck now, the skip checks will still do the right thing
on the installing host now (including the post-install integration).

bryang