Re: [Linuxcoe-devel] Update on packaging

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

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

> Bruno,

Hello Bryan !

> On Tue, Oct 09, 2007 at 08:10:53AM +0000, Cornec, Bruno (Linux Consultant) wrote:
> > This is called ProjectBuilder (aka pb). Cf:
> > http://trac.project-builder.org
> > 
[...]
> 
> This is all great work Bruno  !!

Well, it will be when it'll reach v1.0.0 ;-)
(I passed 0.8.0 yesterday to improve Debian support).

> We totally agree and have been meaning to move those out of the
> package space for awhile now.

Good. Now you have a customer pushing ;-)

> 	SystemDesigner/bin/make-images

Found it !

[...]
# I'm planning to port this to PERL
# once it's roughly working
[...]

May I contribute here ? Not that my perl is at the level of yours or
Lee's, but I have a bit of time to work on it till end of year, so want
to benefit of the opportunity to advance as much as I can.

> although I don't think it's functional yet.  There is already
> a README under images that talks about how to create them.

Ok, will try to work on it taking Mandriva as a pretext to learn more on
that process, and bring a new function.

> At thist point, I can certainly remove the "images" from the
> package/install perspective (and leave them only in the "make dist"
> tarball view), so that you can proceed.  

Well the rpm build also call make integrate, so I'm not sure it will be
sufficient. Anyway I already take it ;-)

> Then step two, I will move
> them out of CVS, and use up some more of our graciously provided
> "instalinux" disk quota to directly host them for download.  Step

We will compete for the quota ;-) But anyway you have priority over my
VMs.

> 3 can then provide a script to generate them.  This stepwise approach
> will allow you to continue working on this very visible portion of
> the project, yes allow us to smoothly transition out of "vending"
> distro images :)

I can begin to help on this I think.

My problem is that I need to develop a Stack for end December using
LinuxCOE+MOndo (aka dploy.org), and I want to povide a clean way to
install everything on the server. So RPMs are mandatory for me.

So Step 3 is the most interesting ;-)

> > WDYT ?
> 
> Above steps seem reasonable?

Yeah, as long as 1 is done tomorrow and 2 friday, I could have a working
setup early next week ;-)

Seriously I follow what you say. I think I can not help that much for
1&2 as my knowledge is not yet sufficient. However helping Louis for 3
seems more reasonable.

> 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,

Great. My questions was of course on tool support, but also from a
project perspective. What is the roadmap in term of versions, what is
the version numbering schema adopted (4.0 vs 4 alone vs 4.x.y ...)

And then which are the files impacted in the project by such a choice ?

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