Re: [Linuxcoe-devel] Update on packaging

[Bruno C. <Bru...@hp...>]

Bryan Gartner said on Tue, Oct 16, 2007 at 12:49:47PM -0600:

> > ./packaging/SystemDesigner/debian/prerm: /usr/share/linuxcoe-sysdes/4.1/bin/post-actions -u
> 
> At one point, all of this was being handled by auto* processing, but
> in order to make it easier for a real Debian maintainer, this was
> pulled out of the module space and into a distinct location.  So,
> yes, back to hardcoded values (at least until PB shows me that light).

I'm right now working on having a single spec file for all my 21 rpm
based VMs. Once it's done, adapting your debian build files to pb will
be easy, and as you're on Debian based systems, you'll then be able to
benefit from what I'm doing.

And I try to avoid hard coded values (except when I do mistakes as in
the previous mail ;-)

> I will probably need a quick tutorial in order to implement this.

I guess you won't be alone ;-) I want to first have a working
environment, and then will re-work the documentation on trac.
>From that, the tutorial should be quicker (and you'll be able to update
trac to fill missing parts ;-)

> FWIW, what is currently in CVS, does in fact build usable .deb
> for the "-common" + "-docs" modules.

FWIW, what is currently in CVS,under pb builds not completely usable
rpms, due to the problems we are addressing in these mails ;-)
But we're not far from it, just that some details remain annoying for
really working packages.

> > Now the problem for all of you will be that you'll have to use pb to
> > generate the tar ball file that you need to work with. Is that an
> > acceptable constraint, or too much ?
> 
> I'd like to get a bit more creative, in that if PBVER is defined
> the auto*/build/tar "process" uses it, and if not, falls back to the existing
> convention if we can.

Ah ! Well, generally it's the reverse I do. PBVER is a macro substituted
by pb before calling the build process, when preparing the tar file.

Extremely short tutoral:

pb -p linuxcoe cms2build does:

- export content from CVS (cvs export)
- get the log from CVS
- create all build files instantiated from pbconf, applying filtering by
  default on them, and also on every file specified as having to be filtered
  (This is where PBVER disappear and is replaced by 4.1)
- executes a script if requested to (e.g. autogen.sh)
- create a tar.gz file from the result.

pb -p linuxcoe build2pkg does:

- get the underlying distribution
- extract the tar file
- setup the build files for that distro from the tar file.
- call the build process of the underlying distro

Now, if we can find a way to satisfy your needs, I'd be more than happy.
Let think about it.

Bruno.
-- 
Linux Profession Lead EMEA  / Open Source Evangelist \        HP C&I EMEA IET
http://www.mondorescue.org / HP/Intel Solution Center \  http://hpintelco.net
Des infos sur Linux?  http://www.HyPer-Linux.org      http://www.hp.com/linux
La musique ancienne?  http://www.musique-ancienne.org http://www.medieval.org