hugin-devs team mailing list archive

[Bruno Postle <1052231@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi, a couple of minor issues with the enblend autotools setup, fixing
these would make things easier for packagers:

The mercurial repository contains generated files (enblend.1,
enblend.info etc...), these get rebuilt locally, resulting in a conflict
that needs to be resolved every time we pull from the sourceforge
repository. Ideally the repository wouldn't contain these files, though
it makes sense for the dist target to build the info and man pages and
include them in the tarball.

The dist target does a full build of the executables even though they
are not included in the tarball, this means creating a tarball for
packaging as rpm/deb takes twice as long as it needs to.

The dist target creates a tarball with the mercurial revision in the
filename, e.g. enblend-enfuse-4.1-1bcd3b5cb866.tar.gz, this is a bit
unusual but ok for development snapshots. The problem is it also
includes a directory called 'enblend-enfuse-4.1-1bcd3b5cb866' even when
the tarball is renamed for a stable release. So when we are packaging
enblend it is necessary to change the rules every time to account for
this variable directory name.

** Affects: enblend
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1052231

Title:
  info and man pages in mercurial

Status in Enblend:
  New

Bug description:
  Hi, a couple of minor issues with the enblend autotools setup, fixing
  these would make things easier for packagers:

  The mercurial repository contains generated files (enblend.1,
  enblend.info etc...), these get rebuilt locally, resulting in a
  conflict that needs to be resolved every time we pull from the
  sourceforge repository. Ideally the repository wouldn't contain these
  files, though it makes sense for the dist target to build the info and
  man pages and include them in the tarball.

  The dist target does a full build of the executables even though they
  are not included in the tarball, this means creating a tarball for
  packaging as rpm/deb takes twice as long as it needs to.

  The dist target creates a tarball with the mercurial revision in the
  filename, e.g. enblend-enfuse-4.1-1bcd3b5cb866.tar.gz, this is a bit
  unusual but ok for development snapshots. The problem is it also
  includes a directory called 'enblend-enfuse-4.1-1bcd3b5cb866' even
  when the tarball is renamed for a stable release. So when we are
  packaging enblend it is necessary to change the rules every time to
  account for this variable directory name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/1052231/+subscriptions