[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Merging GRASS upstream packaging with DebianGIS

On Tue, Jul 21, 2015 at 3:22 PM, sebastic <sebastic@xs4all.nl> wrote:
On 2015-07-21 15:11, Ivan Minčík wrote:
I am trying to adjust rules file for 'grass/daily' branch and I have found
multiple lines moving some files which contain hardcoded GRASS version on
one side of the command. Example:

 mv debian/tmp/usr/lib/grass70/gui/wxpython/iclass/iclass_frame.jpg

What is the reason not using VERSION variable ? If I will change it to the
another hardcoded value, I would have a problem to merge with development

I don't like automatically generated packaging during the build. I like changes to the packaging to be explicit and documented in the VCS history (not hidden from sight in the pbuilder chroot); the packaging in git should be the same as included in the resulting package.

Changing the path for a new upstream release (e.g. 7.1) should be done in a commit that changes all occurrences.

Since GRASS upstream maintains 3 branches (6.4, 7.0 & 7.1) using branches for each seems better than using a single packaging branch for all.

Thank you very much for explanation. BTW, I have fixed some typo [1]. Hope it is ok.

1 - http://anonscm.debian.org/cgit/pkg-grass/grass.git/commit/?h=experimental&id=83382f83e0d568294ff240fa9ef1edfd25b95f7d


Reply to: