Hello All.
In my package (opencpn) there are couple of binary files
without source code/with unfree license that is required
only for OS X and Windows builds (those are some dlls and
redistributable files).
Upstream does like to keep them in original tarball and in
the git version control system
On 06/12/11 19:13, Anton Martchukov wrote:
> Hello All.
>
> In my package (opencpn) there are couple of binary files
> without source code/with unfree license that is required
> only for OS X and Windows builds (those are some dlls and
> redistributable files).
>
> Upstream does like to keep the
Den 12. juni 2011 19:13, skrev Anton Martchukov:
> In my package (opencpn) there are couple of binary files
> without source code/with unfree license that is required
> only for OS X and Windows builds (those are some dlls and
> redistributable files).
>
> Upstream does like to keep them in origi
Hi Anton,
On Mon, 2011-06-13 at 22:30 +0200, Ove Kåven wrote:
> Den 12. juni 2011 19:13, skrev Anton Martchukov:
> > In my package (opencpn) there are couple of binary files
> > without source code/with unfree license that is required
> > only for OS X and Windows builds (those are some dlls and
>
On 06/15/2011 03:27 PM, Kilian Krause wrote:
>
> Definitely. And name your version with suffix +debian or ~debian as you
> see fit.
>
We are very often using +dfsg in the version, as in:
+dfsg-
This way, you have the possibility to have to be
increased if some day,
you find out that you miss
Hi Thomas,
On Wed, 2011-06-15 at 21:16 +0800, Thomas Goirand wrote:
> On 06/15/2011 03:27 PM, Kilian Krause wrote:
> >
> > Definitely. And name your version with suffix +debian or ~debian as you
> > see fit.
> >
>
> We are very often using +dfsg in the version, as in:
-(snip)-
right. Mixed th
6 matches
Mail list logo
