[Kolab-devel] debian packaging scripts in kdepim enterprise branch SVN

[Bernhard Herzog]

Hi,

As part of the development of the enterprise branch, Intevation regularly 
builds new debian etch packages from that branch.  The status of the 
packaging is shown on http://kolab.org/mill/.

Now, part of the packaging process is the maintenance of the debian build 
scripts.  We would like to put those files under version control.  The best 
place would probably be the KDE SVN.  But exactly how should they be managed 
there?  The most obvious way would be to have them a debian subdirectory 
under kdepim.  This has some drawbacks, though.  They're do not describe the 
official debian packages and they're only for one distribution (etch).  This 
could be alleviated by not having them in SVN as the "debian" subdirectory 
directly.  Instead there could be a subdirectory "packaging" with further 
subdirectories as needed for the various distributions.

However, there's a nother drawback that isn't solved by this.  The build 
scripts are usually slightly out of date because they're maintained by 
different development teams.  Therefore, outdated copies may end up in 
releases (tarballs or SVN tags).  It may be better to manage the build 
scripts in directories parallel to the kdepim and kde-l10n.  E.g. they could 
be put into SVN as branches/kdepim/enterprise/kdepim-debian-etch 
(and .../kde-l10n-debian-etch respectively).

How is this handled for other parts of KDE?

  Bernhard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20070626/fca91bec/attachment.sig>