[Kolab-devel] Separating sources from OpenPKG packaging

[Gunnar Wrobel]

Quoting Richard Bos <ml at radoeka.nl>:

> On Tue, Dec 08, 2009 at 11:15:29PM +0100, Gunnar Wrobel wrote:
>> All I need in order to do this soon (once we released 2.2.3) would be
>> a decision how the structure should look like. I would propose to add
>> a new directory "src" in our "server" CVS module. So we would have
>>
>>   - server/src/perl-kolab
>>   - server/src/kolabd
>>   - server/src/kolab-webadmin
>>
>> These would be used to provide *.tar.gz packages that can be uploaded
>> to files.kolab.org.
>>
>> We'd keep the old
>>
>>   - server/perl-kolab
>>   - server/kolabd
>>   - server/kolab-webadmin
>>
>> but they'd just contain the OpenPKG RPM build machinery.
>>
>> In principle I don't consider this a big deal and would just do it
>> this way but I thought I'd ask to make sure nobody disagrees.
>
>
> 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

Correct.

>
> I assume that the openpkg packaging stuff is located in
> server/kolabd and server/kolab-admin.  For perl-kolab it seems
> to be mixed.

Correct.

>
> Thinking Out Loud:
> Everything related to the server is located in the cvs root 'server',
> why should the above 3 mentioned modules be removed from there?
> Wouldn't it be possible to leave the current structure and store
> the openpkg stuff in a cvs module called openpkg?  Like:
> server/{kolabd, kolab-webadmin, perl-kolab}
> openpkg/{kolabd, kolab-webadmin, perl-kolab}
>
> server/openpkg/{kolabd, kolab-webadmin, perl-kolab}

I don't quite follow. If you look at the current directories in CVS  
HEAD then nearly all of them only contain OpenPKG related stuff. The  
build Makefile, the spec file, additional patches etc. They are all  
used to build an RPM from these components.

The three packages I mentioned differ from that structure as they  
contain source code. For all other packages source code is being  
downloaded as *.tar.{gz,bz2} from an external server.

So the goal would be to move the sources to a separate directory where  
we do the *.tar.gz packaging and upload to files.kolab.org.

The remaining directories server/{kolabd, kolab-webadmin, perl-kolab}  
would then only contain the build machinery in the same way the other  
packages do.

>
> If you stay with your proposal, how would you move modules?
> I hope that you'll move them on the server, to leave the cvs
> history untouched.

Probably also depends on when we could switch to mercurial. That would  
make such things easier.

Cheers,

Gunnar

>
> --
> Richard
>
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
______ 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/devel/attachments/20091210/efc69494/attachment.sig>