Hi Gianfranco,
Le 16/05/2016 21:15, Gianfranco Costamagna a écrit :
> Hi Eric,
>
>
>> I think there are too many changes in this release.
>> Is it okay to remove autoreconf for now,
>> and replace autotools-dev by autoreconf at next release ?
>
> it is, just a side note: I never had issues with that move, and in general issues
> arises when: the configure/Makefiles are patched (because you obviously need to patch
> configure.ac and Makefile.am instead), or bad config.guess/config.sub files
> (and usually the result is a build failure on some ports).
>
> As you wish, you can switch in a later upload, or do it now and maybe fix/revert in
> case of troubles
Finally, I'm going to swith to autoreconf now.
>> Reorg: gnustep-common and gnustep-make existed; move one file from
>> gnustep-common to gnustep-make; new gnustep-common does not require new
>> gnustep-make
>> Breaks: gnustep-make (<<2.6.8-1)
>> Breaks: gnustep-common (<<2.6.8-1)
>>
>> Is it okay to do that?
>
> I don't think so, but I can review a patch/package, because some lines without their
> context have no meaning (you need to put the breaks+replaces in the right binary
> package).
Finally, I reflected and I think we should not mix different version of
gnustep-make and gnustep-common binary packages.
It is unsupported by upstream andI could lead to strange bugs.
gnustep-common will Breaks: gnustep-make (<< {source:Version})
and
gnustep-make will Depends: gnustep-common(>= {source:Version}
It should prevents the mix of versions and thus Break or Replaces are
now useless
Thanks
Eric
Attachment:
signature.asc
Description: OpenPGP digital signature