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 >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). >OK, I'm going to update gnustep make to do improvements you suggested. >Since I am not familiar with mentors rules, I have a question : >Should I prepare a new revision (ie 2.6.8-2) or should I update the >2.6.8-1 revision and reupload it ? please upload -1 revision until it gets sponsored! thanks, G.
