From: Nicolas B. <ni...@bo...> - 2005-09-02 09:22:04
|
Hello Roberto, Back at work... (sorry for the delay) On Thu, 2005-08-25 at 13:35 -0400, Roberto C. Sanchez wrote: > On Thu, Aug 25, 2005 at 03:48:26PM +0200, Nicolas Boichat wrote: > > > > Now, about the idea of splitting the project in modules, I'm not sure of > > what you mean... Do you suggest to split the project in different > > tarballs?? If so, I disagree. I think two tarballs (ddccontrol and > > ddcontrol-db) are already enough to download, and as their size is > > relatively limited I don't see any problem (if you only want some parts > > of ddccontrol, you can enable them with configure flags). > > Of course, if a packager want to split the project, there is no problem > > (you often see this with RPMs: ddccontrol-lib, ddccontrol, > > ddccontrol-devel...). > > > I would also like to know about this. I am working on the Debian > packaging and should have something ready by this weekend. However, if > the project is going to be split into different packages, I think it may > be worthwhile to wait. What do you think? The project will not be splitted in the CVS. But from the packaging point of view, you may want to split the project in different parts, for example: - ddccontrol-base: basic command line ddccontrol tool, and libddccontrol.so - ddccontrol-devel: header files to build apps against libddccontrol.so (for the moment it is not needed as no other app use the library) - ddccontrol-gnome: gddccontrol and gnome-ddcc-applet You may want to create even more packages (Christian presented an alternative), or just create one for the moment. Best regards, Nicolas |