Re: elegant ways to build a package two times

2008-04-22 Thread Josselin Mouette
Le lundi 21 avril 2008 à 19:22 +0200, Marco d'Itri a écrit : > On Apr 15, Josselin Mouette <[EMAIL PROTECTED]> wrote: > > You don???t need automake for this to work, it???s just that automake does > > things right by default. Fixing the package to get out-of-tree builds to > > work using VPATH shou

Re: elegant ways to build a package two times

2008-04-21 Thread Marco d'Itri
On Apr 15, Josselin Mouette <[EMAIL PROTECTED]> wrote: > You don???t need automake for this to work, it???s just that automake does > things right by default. Fixing the package to get out-of-tree builds to > work using VPATH should be feasible. Can you point me to a good example of a package usin

Re: elegant ways to build a package two times

2008-04-15 Thread Josselin Mouette
Le dimanche 13 avril 2008 à 17:50 +0200, Marco d'Itri a écrit : > INN uses autoconf but not automake, so mkdir bin && ./configure does > not generate working makefiles. (I suppose you mean ../configure) You don’t need automake for this to work, it’s just that automake does things right by default

Re: elegant ways to build a package two times

2008-04-13 Thread Guus Sliepen
On Sun, Apr 13, 2008 at 05:50:39PM +0200, Marco d'Itri wrote: > I am looking for *elegant* ways to build both packages from the same > source with the least possible duplication of the code in debian/rules > and of the debian/ debhelper files (the package is complex and needs > much work before an

elegant ways to build a package two times

2008-04-13 Thread Marco d'Itri
The inn2 packages is not as useful as it should be, since it does not support LFS which is mandatory for large servers. I cannot just enable LFS support since there is no transition path for some classes of users, so we need both inn2 and inn2-lfs packages. I am looking for *elegant* ways to build