<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Sans Serif'; font-size:12pt; font-weight:400; font-style:normal;">Op donderdag 10 december 2009 09:25:36 schreef Gunnar Wrobel:<br>
> I don't quite follow. If you look at the current directories in CVS <br>
> HEAD then nearly all of them only contain OpenPKG related stuff. The <br>
> build Makefile, the spec file, additional patches etc. They are all <br>
> used to build an RPM from these components.<br>
><br>
> The three packages I mentioned differ from that structure as they <br>
> contain source code. For all other packages source code is being <br>
> downloaded as *.tar.{gz,bz2} from an external server.<br>
><br>
> So the goal would be to move the sources to a separate directory where <br>
> we do the *.tar.gz packaging and upload to files.kolab.org.<br>
><br>
> The remaining directories server/{kolabd, kolab-webadmin, perl-kolab} <br>
> would then only contain the build machinery in the same way the other <br>
> packages do.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Clear. Moving the sources to the directory src, seems a good thing to do :)<br>
Which actually means that in the future if someone does not deal with openpkg he or she does not need to check out the cvs module server, but only the module src.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
Richard</p></body></html>