Re: Same source package building plugins for main and contrib

2013-04-22 Thread Boris Pek
>>> Should I produce 2 different source packages >>> for main and contrib from the same upstream project? >> >> Short answer: >> Yes, this is the best solution in such case. >> (If there is no any possibility to avoid non-free dependencies.) > > That's only if they're _build_ dependencies. Ru

Re: Same source package building plugins for main and contrib

2013-04-22 Thread Adam Borowski
On Mon, Apr 22, 2013 at 02:28:14PM +0300, Boris Pek wrote: > Hi Nicolas, > > > Should I produce 2 different source packages > > for main and contrib from the same upstream project? > > Short answer: > Yes, this is the best solution in such case. > (If there is no any possibility to avoid non-fre

Re: Same source package building plugins for main and contrib

2013-04-22 Thread Boris Pek
Hi Nicolas, > Should I produce 2 different source packages > for main and contrib from the same upstream project? Short answer: Yes, this is the best solution in such case. (If there is no any possibility to avoid non-free dependencies.) Some additional thoughts: If tarball is quite small, you

Re: Same source package building plugins for main and contrib

2013-04-22 Thread Andrey Rahmatullin
On Mon, Apr 22, 2013 at 12:56:25PM +0200, Nicolas Bourdaud wrote: > My question is simple... Should I produce 2 different source packages > for main and contrib from the same upstream project? AFAIK yes. -- WBR, wRAR -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org wi

Same source package building plugins for main and contrib

2013-04-22 Thread Nicolas Bourdaud
Hi all! I am facing the problem of how to package a project that builds some plugins that are completely free and some that have non-free dependencies, although the source code of the plugins themself is available under a free license. To simplify the explanation, I have in the end 2 binar