|
From: Frank V. C. <fr...@co...> - 2000-11-15 23:28:45
|
Hans? (BTW: Congrats on the work!, where there any stumbling parts?) Christophe? Here is what I propose assuming all code, configure.in, ChangeLog, and README are checked in or valid for the next release: Frank: Create libcorelinux 0.4.30 rpm (with the exception of the doc.rpm) Create CoreLinux++Docs 0.4.30 Create libclfw 0.2.5 rpms (docs build on this one as it is still small) I'll ftp direct to download.sourceforge.net/incoming Christophe: Create libcorelinux 0.4.30 debs (the woody/potato combo) Create libclfw 0.2.5 debs (the woody/potato combo) Create libcorelinux 0.4.30 doc rpm You can either put these in /home/groups/corelinux/packages/debian or ftp direct to download.sourceforge.net/incoming Christophe, I don't know if you need to update the debian/rules file for each package? If so, I will wait to see the CVS update before I tag all the files. Also, if this is not something you will be doing soon, let me know as I will stagger the updates to download.php Wow, big stuff. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |