What about starting to use project-builder for native packages? (was: Re: Next Suse Kolab version?)
Gunnar Wrobel
wrobel at pardus.de
Mon Apr 12 23:47:57 CEST 2010
Hi (especially to the native packagers),
would it be okay to start building (or at least to start trying to
build) packages via project-builder (http://trac.project-builder.org/)?
I looked a little bit closer at the tool at the end of last week and I
got the impression that this would serve us well. I admit this was not
yet an in-depth check but at the moment I'm pretty convinced it should
allow us to create simple packages for several distributions at the
same time.
Mathieu suggested using this tool a while ago. Richard suggested using
the OpenSUSE build system. While I like that system it does not
deliver packages for a specific distribution that is (still) critical
to the Kolab server: OpenPKG. project-builder is probably slightly
more complicated but it also is somewhat more flexible.
What I would like to start with - and this is the reason why I respond
specifically to this mail of Richard - is to package the PEAR based
packages via project-builder. Richards confusion is justified: The
PEAR packages are not being downloaded from pear.horde.org at the
moment. The Horde Project will only use full blown PEAR packaging for
Horde 4. Currently I derive the Horde PEAR packages from CVS and
upload the snapshots to files.kolab.org.
But building packages for several distributions should be rather
trivial as I already reduced the PEAR package specs to a package.info
file containing some package specific variables and a generic
spec-file template. project-builder is not that different from that
approach.
So if we could collaborate on getting a first set of packages for the
Kolab server this way I believe the native packagers could benefit
from the work I'm doing on the PEAR packaging.
Cheers,
Gunnar
Quoting Richard Bos <ml at radoeka.nl>:
> Hi Carsten,
>
> Op dinsdag 30 maart 2010 10:57:23 schreef Carsten Burghardt:
>> I am currently in the process to move my Kolab installation (2.2.2) to
>> another server and noticed that 2.2.3 is not available for the Suse
>> packages. According to the explanation on the Suse webpage this is
>> because only the trunk version is packaged. Does anybody know when the
>> packages will be updated? I am a bit hesistant to setup a new server
>> based on a version which is already outdated.
>
> I guess that I should now that, as I package kolab for openSUSE. I
> don't have
> the intention to package 2.2.3 as that is rather different than trunk. I
> think that kolab:unstable is up to date till about 2 - 4 weeks ago.
>
> I'm a little confused at the moment, because I see commits to files that I
> expect to the appear at http://pear.horde.org, but are added as patches to
> kolab openpkg rpms. I hope that these updates are transferred to
> http://pear.horde.org before kolab-2.3 is released. If the patches are not
> transferred, it will be difficult to create suse rpms of the kolab-2.3
> release. But that is the answer, if al goes well openSUSE kolab rpms will be
> provided when kolab-2.3 is released. They should appear in their own stable
> repository (e.g. server:Kolab:Kolab_2_3
>
> --
> Richard
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
--
______ http://kdab.com _______________ http://kolab-konsortium.com _
p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de Dr. Gunnar Wrobel
Tel. : +49 700 6245 0000 Bundesstrasse 29
Fax : +49 721 1513 52322 D-20146 Hamburg
--------------------------------------------------------------------
>> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.kolab.org/pipermail/users/attachments/20100412/8c2f9a3c/attachment.sig>
More information about the users
mailing list