Bug#584590: salome: New binary package organization

Denis Barbier bouzim at gmail.com
Wed Jun 16 17:04:35 UTC 2010

On 2010/6/16 Adam C Powell IV wrote:
>> IMO the main problem just now is that this package is very difficult
>> to manage due to its size and to the resources needed to build it.
>> I modified debian/rules to help with testing packaging changes.  New
>> targets are provided for each salome module individually: reconfigure
>> (by calling build_configure), configure, build and install.  I added
>> AM_MAINTAINER_MODE into all configure.ac files so that one can modify
>> Makefile.am files without having to always rebuild everything, this
>> can save a lot of time.  This work has been done in the 'dev' branch
>> of a cloned repo, see
>>    http://git.debian.org/?p=users/barbier-guest/salome.git;a=log;h=refs/heads/dev
>> It has not been fully tested, some things may have to be fixed, but I
>> believe that this branch should be committed anyway.
> This sounds good to me.  Is there a way you can make this into a patch
> or two?  That will make it easier for me to get it into alioth.

Hi Adam,

It is IMO much better to keep logical patchsets.  You can run these commands:
  git remote add barbier git://git.debian.org/users/barbier-guest/salome.git
  git fetch barbier
  git checkout -b dev barbier/dev
to retrieve my changes and then you can play with patches as usual.
If you really want to squash patches together, you can run
  git rebase -i master dev
This opens up an editor containing this text:
  pick 92fa1d3 New target: reconfigure-stamp
  pick bacf6e6 Add AM_MAINTAINER_MODE into all configure.ac files
  pick 6bb56d8 Add --disable-dependency-tracking to configure flags
Replace all 'pick' words but the first one by 'squash', and voila.


More information about the debian-science-maintainers mailing list