On Mon, Jun 18, 2007 at 04:28:09PM -0400, Christian Convey wrote:
> I could create Yet Another Source Package, "myproject-common-src.deb",
> that contains *only* those files that are in common. I.e., it would
> only contain "make-functions{1,2}.mk" and perhaps the top-level
> Makefile. Then package like "libraryA-src.deb" could have a package
> dependency on myproject-common-src.deb.
You could also just copy the file to the different source packages
when releasing the source, no? Or are they so big and are there so
many packages that will use them?
> Is this just too goofy of an approach? Should I bit the bullet and
> make the whole entire project contains just three packages?
> (myproject.deb, myproject-dev.deb, and myproject-src.deb) ?
The biggest problem of this approach (IMHO) is that you only can
update them all at once. You need to increase the version number of
every binary package built from the source even though only one of
them might really have been changed. So it is generally a good idea
to modularize ones source packages (see e.g. X.org)
Gruesse,
--
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
