On Thu, Oct 13, 2011 at 10:55 PM, W. Martin Borgert <deba...@debian.org> wrote: > On 2011-10-13 21:31, anatoly techtonik wrote: >> There is a long standing bug in trac-bitten [1] to make a spin off a >> bitten-slave package from the same source that will include just slave >> client for running builds, which is independent of Trac [2]. Usually, >> you can build bitten-slave with: >> >> python setup.py --without-master install >> >> But how to specify that in debian/rules - >> http://anonscm.debian.org/viewvc/python-apps/packages/trac-bitten/trunk/debian/rules?revision=4711&view=markup >> ? > > You don't have to specify anything in debian/rules! :~) > > Just change debian/control (I just checked in my working copy, > see r7647). However, one has to have one or two install files > in the debian directory. These determine, which files will go > into which package.
Nice. But how do you create these install files? Can stdeb tool help with that? > Note: Because master and slave use some Python files in common, > you need these files either in a third package > (trac-bitten-common) or we just keep these files in the slave > package. This only means, that on the master machine also a > slave must be installed, which doesn't hurt size-wise. The master package description can be improved ,) - This package contains the master, which integrates into Trac. + This package contains the master implemented as Trac plugin. I'd keep full package in master package and strip slave to required files only. I wonder that will happen with shared files if you install trac-bitten + trac-bitten-slave and then remove slave? Is Debian smart enough to detect that these files are still belong to another package? -- anatoly t. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capkn8xk206esd5njvwoz9o66whkwxmpjgkfzhm5thvkhk__...@mail.gmail.com
