On Wed, Feb 16, 2011 at 04:12:20PM +0100, firstname.lastname@example.org wrote: > Hello, > > > What's the proper way to package a plug-in that require the application's > sources > to compile and both come in a separate tarball ? > > Note : The application and the plug-in will be built in a separate package. Try to convince the maintainer of the application package to provide an additional package, usually named foo-source or something, which basically contains the archived source of the application just as it is before the build is started (e.g. after applying patches and similar). For an example, pick any of the packages listed by e.g.: apt-cache search --names-only -- -source | fgrep -ve 'kernel module' -e driver I believe the gcc*-source packages are provided for this exact purpose - a base for cross-compiling development environments for embedded systems and such. G'luck, Peter -- Peter Pentchev email@example.com roam@FreeBSD.org firstname.lastname@example.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 "yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation.
Description: Digital signature