Re: [Linuxcoe-devel] Update on packaging

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

Bryan Gartner said on Tue, Oct 09, 2007 at 09:41:40AM -0600:

> > Another problem I have is with the versioning of the LinuxCOE project.
> > Where are those version number handled ? Is there a subverion ? When a
> > new package is released, will it be 4.1 ? 4.0.1 ? What granularity do
> > you want ?
> 
> The autoconf/automake currently handles the versioning, but my plan all
> along has been to use CVS tags (since we don't use subversion) to denote
> versioning.  Seems like now might be the right time to begin that
> implementation as well,


>From a quick look at the sources of today, I remarked that:

./docs/configure.ac:AC_INIT([linuxcoe-sysdes-docs],[4.1],[bry...@hp...])
./SystemDesigner/configure.ac:AC_INIT([linuxcoe-sysdes],[4.1],[bry...@hp...])
./packaging/SystemDesigner/debian/prerm: /usr/share/linuxcoe-sysdes/4.1/bin/post-actions -u
./packaging/SystemDesigner/debian/postinst: /usr/share/linuxcoe-sysdes/4.1/bin/post-actions -i
./packaging/SystemDesigner/debian/rules: --prefix=/usr/share/linuxcoe-sysdes/4.1 \
./packaging/SystemDesigner/debian/rules: --sysconfdir=/etc/linuxcoe-sysdes/4.1 \
./packaging/SystemDesigner/debian/conffile: /etc/linuxcoe-sysdes/4.1/linuxcoe.rc
./packaging/SystemDesigner/debian/conffile: /etc/linuxcoe-sysdes/4.1/includes/config.state
./packaging/SystemDesigner/debian/conffile: /etc/linuxcoe-sysdes/4.1/includes/LinuxCOE-SystemDesigner.conf
./packaging/SystemDesigner/debian/conffile: /etc/linuxcoe-sysdes/4.1/includes/sudoers
./packaging/SystemDesigner/debian/dirs:/usr/share/linuxcoe-sysdes/4.1
./packaging/SystemDesigner/debian/dirs:/etc/linuxcoe-sysdes/4.1
./packaging/SystemDesigner/debian/dirs:/usr/share/linuxcoe-sysdes/4.1/var
./packaging/SystemDesigner/debian/dirs:/var/cache/linuxcoe-sysdes/4.1
./packaging/SystemDesigner/debian/dirs:/var/lib/linuxcoe-sysdes/4.1
./packaging/SystemDesigner/debian/dirs:/var/lib/linuxcoe-sysdes/4.1/profiles
./packaging/SystemDesigner/debian/dirs:/var/log/linuxcoe-sysdes/4.1


What I'd like to propose is to use (later on, when ready ;-) the
Project-Builder macro PBVER to replace all those hardcoded values with
it. That way all packages generated will just use the declaration in
pbconf/linuxcoe.pb to get the project version and filter all the files
accordingly.

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 ? 

Looking for feedbacks ;-)

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