[Linuxcoe-devel] RFC re: packaging

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

FYI,

I just got my second usable .deb package created (for
systemdesigner-docs).  So now that I can see how to
scale the packaging across the other modules, I thought
I would step back and ask for some feedback.

In the SystemDesigner CVS module, I actually checked
in the debian sub-tree (which is where the debian
packaging magic happens) mostly just as a way to keep
the work around.  What I am proposing to do moving
forward is a bit different, so that the developers
and package maintainers can work in different spaces.
Basically this was the advice of a seasoned Debian
Maintainer, so that the package process can rev as needed
independently from the project itself.  Couple that
with the intent to create .rpm packages next, and
I think you may see further justification.

So, I am ready to create a "packaging" CVS module
to house all of the packaging artifacts:

  CVS/
    packaging/
      <module-name> (like docs, SystemDesigner)
        debian/
	  ...
        <module-name>.spec
	  (perhaps even with various distro suffixes)

In this way, the packaging maintainers would have
ready reference to:

  - tweak packaging artifacts distinct from the package
    itself
  - possibly even make targets within this space to
    create an easy way to have the necessary inputs
    for package maintainers (plus, of course, needing
    the .tar.gz from the main package modules)
  - CVS tags could then be used to synchronize what
    packaging version is tied to what package release
    (when we are ready to commit such "releases")

What do others think?  Are there better approaches?

bryang

P.S. I took a quick SWAG at a SystemDesigner.spec
	file yesterday as well.  While it only
	packaged a single file from that module,
	the remainder seemed pretty straightforward
	(sans postinst logic which would need to
	be similar to the make integrate functionality).
	So I could offer that as a seed in that
	packaging space as well.