[pkg-kolab] Questions about packages

[Jeroen van Meeuwen]

On Monday, June 25, 2012 10:46:09 AM Christopher Reichert wrote:
> Well, I was referring to http://git.kolabsys.com/server.git/. When I
> look here I am still confused. There are tags and branches for versions
> 2.3 and lower. I was expecting something like this as a clear branch for
> 2.4. Is Kolab 2.4 just in master? Sorry for the confusion but there are
> a lot of packages with different information and I want to make sure I
> am 100% clear.
> 
> Just so I am absolutely clear I need just a bit more detail on exactly
> which source to use. For example, say I clone the server repo,
> 
> $ git clone git://git.kolabsys.com/git/server.git
> 
> Then where should I be to make sure I have the exact same sources as the
> redhat packages? Maybe I still misunderstand slightly.
> 

2.4 isn't in 'server.git' at all. It's not in kolab-server.git either. Those 
two repositories are OpenPKG 

Please see http://git.kolab.org - I've now made it so the 2.x repositories are 
distinctly marked as "2.x prior to 2.4".

The relevant repositories for code we are upstream for are at the top;

- kolab-schema - Kolab LDAP schema extensions,
- kolab-wap - Web Administration Panel + API,
- pykolab - the Server and utilities implementation,
- roundcubemail-plugins-kolab - the plugins needed for Roundcube to become a 
Kolab client.

Naturally, we also care about the dependencies for these packages - hence the 
version matrix mentioned earlier.

> > I think we should perhaps try and encapsulate things in a
> > Debian_Packages wiki page. I've thought about this before but I found
> > there's too few dimensions to a table to encapsulate all information -
> > perhaps we just start with what packages we want and what git repo to
> > use (and branches?).
> 
> Ya, sounds good. I can go ahead and create a new branch
> debian/hosted-kolab-2.4. My plan is to start updating packages that are
> already in Debian and then finish making packages for the corresponding
> src.rpms you linked to.
> 

Well, considering most packages have rendered somewhat irrelevant (kolabd, 
libkolab-perl, kolab-webadmin), I don't think that's necessarily the best 
approach.

Please consider the aforementioned, and the work already done in various APT 
packaging repositories.

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/attachments/20120625/148a2b28/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/attachments/20120625/148a2b28/attachment-0001.pgp>