I would like to separate the debian package building so that each package is built separately. There are a couple touchy packages in there that never build for me without a fair amount of fiddling and I need to build packages from source quite a bit since I have to push out pd updates to 15+ debian boxes.
Here's my idea: Separate each package out into its own "debian" directory which will compile only one package: externals/debian externals/cyclone/debian externals/flext/debian externals/footils/debian (aka pd-flext-ext; this might to be renamed pd-footils for this to work) externals/OSCx/debian externals/pdp/debian externals/pidip/debian externals/unauthorized/debian
Then a Makefile in packages/debian could run "dpkg-buildpackage -b" for each of these, copy the "debian" dir to the pd src, and compile it too.
This system would make it easier to add new debian packages and have them automatically build, since all of the necessary files would be totally separate, with the exception of a couple lines in packages/debian/Makefile
.hc
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Here's my idea: Separate each package out into its own "debian" directory which will compile only one package: externals/debian externals/cyclone/debian externals/flext/debian externals/footils/debian (aka pd-flext-ext; this might to be renamed pd-footils for this to work)
Puh, I fought hard with Guenther to *not* name the package pd-footils which is how it was called once. ;) I'd see a pd-flext-ext package as a package of externals that depend on flext. This doesn't have to be just my externals, in fact, xsample, pool and such should go there as well. They then could build-depend on pd-flext.
externals/OSCx/debian
What is the reason to not package OSC inside pd-externals? It doesn't depend on anything special, just std-C-headers, not even any of Pd's "private" headers.
ciao
On Thursday, Mar 18, 2004, at 13:36 America/New_York, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Here's my idea: Separate each package out into its own "debian" directory which will compile only one package: externals/debian externals/cyclone/debian externals/flext/debian externals/footils/debian (aka pd-flext-ext; this might to be renamed pd-footils for this to work)
Puh, I fought hard with Guenther to *not* name the package pd-footils which is how it was called once. ;) I'd see a pd-flext-ext package as a package of externals that depend on flext. This doesn't have to be just my externals, in fact, xsample, pool and such should go there as well. They then could build-depend on pd-flext.
externals/OSCx/debian
What is the reason to not package OSC inside pd-externals? It doesn't depend on anything special, just std-C-headers, not even any of Pd's "private" headers.
I think this is mostly because its easiest to work along the lines of the build system used. Each debian package represents a different build system. It may not be pretty, but it makes building the packages easier. That's why I ended up doing the same thing with the MacOS X installer.
.hc
ciao
Frank Barknecht _ ______footils.org__
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Thursday, Mar 18, 2004, at 13:36 America/New_York, Frank Barknecht wrote:
What is the reason to not package OSC inside pd-externals? It doesn't depend on anything special, just std-C-headers, not even any of Pd's "private" headers.
I think this is mostly because its easiest to work along the lines of the build system used. Each debian package represents a different build system. It may not be pretty, but it makes building the packages easier. That's why I ended up doing the same thing with the MacOS X installer.
Actually I would prefer it to have as few packages as possible, each containing as much stuff as needed. I kind of hate having to install lots of small packages when one package could do. Of course, at least on Debian this could be handled with metapackages, so called "tasks". But in general I guess, most package users will prefer not having to download lots of packages as well.
That's why I would prefer, if we could somehow find a build system, that allows externals to install in one common place. The "build" directory isn't that bad in this regard, I think. It just needs maintainance and isn't that fit for flext externals or library dependent externals.
For making Debian packages, it actually isn't that hard to collect externals from various places into one package. It "just" requires several lines like: ... (cd zexy/src; $(MAKE) -f makefile.linux LINCLUDE="-I ../../build/include") # Build flext (cd grill/flext; $(MAKE) -f makefile.pd-linux PDPATH=../../build/include STK="" ) ... in the build and similar ones in the install targets. Now if we could agree on naming conventions, we could even get rid of some of these like let LINCLUDE=PDPATH and so on. This shouts a bit for autoconf, though. ;)
ciao
On Thursday, Mar 18, 2004, at 13:07 America/New_York, Hans-Christoph Steiner wrote:
I would like to separate the debian package building so that each package is built separately. There are a couple touchy packages in there that never build for me without a fair amount of fiddling and I need to build packages from source quite a bit since I have to push out pd updates to 15+ debian boxes.
Here's my idea: Separate each package out into its own "debian" directory which will compile only one package: externals/debian externals/cyclone/debian externals/flext/debian externals/footils/debian (aka pd-flext-ext; this might to be renamed pd-footils for this to work) externals/OSCx/debian externals/pdp/debian externals/pidip/debian externals/unauthorized/debian
Then a Makefile in packages/debian could run "dpkg-buildpackage -b" for each of these, copy the "debian" dir to the pd src, and compile it too.
This system would make it easier to add new debian packages and have them automatically build, since all of the necessary files would be totally separate, with the exception of a couple lines in packages/debian/Makefile
Ok, I am responding to my own email because I just realized that I left something out: the debian autobuilders. AFAIR, the externals build files need to be contained within the 'externals' directory. So with that in mind, I revise this above idea. Maybe externals/debian/rules could call dpkg-buildpackage for the other packages? I need docs on the auto build process, anyone have a good links? I didn't find anything by browsing through the docs.
.hc
-
Frank Barknecht -
Hans-Christoph Steiner