[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-devel
Subject:    Re: [Kolab-devel] Separating sources from OpenPKG packaging
From:       Gunnar Wrobel <wrobel () pardus ! de>
Date:       2010-02-09 7:47:36
Message-ID: 20100209084736.16225kze2spohc00 () webmail ! pardus ! de
[Download RAW message or body]

This message is in MIME format and has been PGP signed.

[Attachment #2 (multipart/signed)]
This message is in MIME format and has been PGP signed.


Quoting Thomas Arendsen Hein <thomas@intevation.de>:

> * Gunnar Wrobel <wrobel@pardus.de> [20100108 16:12]:
>> Quoting Thomas Arendsen Hein <thomas@intevation.de>:
>>
>>> * Richard Bos <ml@radoeka.nl> [20091209 08:51]:
>>>> So, actually what you want to do is to move the directories
>>>>  server/kolabd/kolabd           to src/kolabd
>>>>  server/kolab-admin/kolab-admin to src/kolab-admin
>>>>  and
>>>>  server/perl-kolab              to src/perl-kolab
>>>
>>> Please keep everything somewhere below server, I don't want a
>>> different module (or directory) here, only subdirectories of server.
>>>
>>
>> Can you detail why?
>>
>> Keeping them on the same level would indicate to me that the source
>> directories have similar content to the packaging directories. Which
>> they don't.
>
> In the past (before you moved much code to the Horde repositories)
> all code specific to Kolab Server lived in "server". Now to see all
> code I already have to look in other places.

The code I moved to the Horde repository is not "Kolab specific".  
Free/Busy is something other projects do as well. Resource management  
is also not specific to the Kolab server. Horde offers the same  
features - albeit currently not in the same complexity as the Kolab  
server does. Merging our libraries with the Horde code is an ongoing  
effort.

>
> When you move some things to "src" next to "server", I will have to
> checkout yet another repository (even if on the same CVS server) and
> have to do tagging/branching/thinking/whatever in two separate
> places.

I wanted to move the source code into "server/src".

We discussed the same issue on the phone yesterday and we agreed that we would
simply use the structure currently in place in "kolabd" and  
"kolab-webadmin". Having a second level directory that contains the  
source which is named in the same way as the top level directory. So  
the only change of the current system would be to add  
"server/perl-kolab/perl-kolab" and move the source code into that  
directory.

We'd build source tars in server/perl-kolab/perl-kolab (using  
Makefile.PL) and publish them on files.kolab.org. The Makefile and  
spec-file in "server/perl-kolab" would then download the source from  
there and package it.

Thomas mentioned he won't move directories on the server so I'll do it  
on the client side.

Cheers,

Gunnar
>
> Thomas
>
> --
> thomas@intevation.de - http://intevation.de/~thomas/ - OpenPGP key:  
> 0x5816791A
> Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck,  
> HR B 18998
> Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>



-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p@rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p@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@rdus <<
--------------------------------------------------------------------


[Attachment #5 (application/pgp-signature)]

_______________________________________________
Kolab-devel mailing list
Kolab-devel@kolab.org
https://kolab.org/mailman/listinfo/kolab-devel

[prev in list] [next in list] [prev in thread] [next in thread]