[Debian GNUstep maintainers] gnustep-base transition
Yavor Doganov
yavor at gnu.org
Wed Sep 27 20:16:17 UTC 2017
Eric Heintzmann wrote:
> Le 27/09/2017 à 09:31, Yavor Doganov a écrit :
> > In any case gnustep-base must pass through the NEW queue anyway.
>
> and with a new soname gnustep-gui too
At the time I wrote the message I didn't know about the -gui issue
yet.
> So let's migrate to .dgbsym
OK, I'll make the changes in -base. For -gui I suggest to wait and
see how we proceed first.
> Well I don't know the good practices, if there are any, for
> debian/changelog in git repo.
Well, I was asking what way do you prefer. I don't insist that mine
is correct; I guess it's inherited from GNU practice where every
code change must include a corresponding ChangeLog entry.
Some other unrelated questions:
What's the reason to move some files under debian/templates? I guess
it was to avoid cluttering debian/ but I find this approach slightly
confusing: it is not immediately evident that some files under debian/
are generated so a potential NMUer may not know that debian/control is
a generated file. Perhaps we should put some comments or document it
in a separate file.
I don't actually understand how this new debian/copyright stuff with
these .yml files works. I assume that the intention is to maintain
the copyright file (semi-)automatically, but running `cme update
dpkg-copyright' generates a lot of differences, some of them
meaningless. Am I doing something wrong or I completely misunderstood
the whole thing?
More information about the pkg-GNUstep-maintainers
mailing list