[Debian GNUstep maintainers] Misc issues with gnustep-base

Eric Heintzmann heintzmann.eric at free.fr
Fri Sep 29 20:46:13 UTC 2017



Le 29/09/2017 à 22:30, Yavor Doganov a écrit :
> Eric Heintzmann wrote:
>> Le 29/09/2017 à 00:36, Yavor Doganov a écrit :
>>> I suggest to move them to gnustep-base-doc.
>> Where will you install these examples ?
>> (|Policy suggests /usr/share/doc/package/examples )
> As I said, /usr/share/doc/gnustep-base-doc/examples in the
> gnustep-base-doc package.

OK, then I have no objection

>
>>> 2. debian/control -- It is not possible to regenerate it with a simple
>>> command now as it is part of the override_dh_auto_configure recipe.
>> Yes it is an issue of -base and -gui and -back.
>> Since the debian new maintainer guide says "Please limit explicit
>> targets to override_dh_* targets and completely independent ones, if
>> possible. ", I failed to find an elegant solution.
>> But if you have one, it is welcome
> Well, it says "if possible" -- IOW, it's not forbidden.  I agree that
> having separate rules for all other generated files is redundant.  But
> debian/control is special, it always was.
>
>>> 3. Where is the Git history?
>> Yes it was, using
>>
>>   *gbp import-dscs* --debsnap gnustep-base
>>
>> The goals was to support the use of pristine-tar, and to quickly import
>> a long history of NMUs
> 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"

> I used to import
> NMUs, there was no problem. 
I know, but I had to do it on a lot of gnustep related packages.
It was really simpler to do with only one command line by package.





More information about the pkg-GNUstep-maintainers mailing list