[Debian GNUstep maintainers] Misc issues with gnustep-base

Yavor Doganov yavor at gnu.org
Sun Oct 29 08:50:56 UTC 2017


Hi Eric,

On Fri, 29 Sep 2017 23:46:13 +0300,
Eric Heintzmann wrote:
> Le 29/09/2017 à 22:30, Yavor Doganov a écrit :
> > Why it was necessary to replace the old repository?  
> 
> The main goal was to support the use of pristine tar,
> and AFAIK it is not possible to add  it "on the fly"

AFAICS there's gbp-pristine-tar which makes it possible to switch from
a classic git-buildpackage workflow to pristine-tar.

But I fail to see the benefit from using pristine-tar.  I get the
tarball with uscan or from the Debian archive, in cases when it's no
longer available upstream.  Thus, the orig tarball is always in the
parent directory and is not recreated from the Git tree.  NMUs are
imported in the same manner, so there's no difference whether
pristine-tar is used or not.

Am I missing something?




More information about the pkg-GNUstep-maintainers mailing list