If you can't stand how the automake-generated
"dist" target works, simply whip up your own.
Change all necessary "Makefile.am"; just make
sure you don't break existing functionality of
our build-system.
You have commit rights to the repo, so go ahead.
For extra points assign this issue to yoursel
No, I create a tarball and use this to create a rpm package in a clean
mock chroot. Among other things this tests the full build from source,
tests the dist target, and verifies all the dependencies. These snapshot
packages get tested by people using the Hugin snapshots, so there are no
surprises w
I assume you build within the source tree. Prefer VPATH-builds
and the issue of overwritten *.1 and *.info files will go away.
The version labeling, e.g. "enblend-4.1-123deadbeef", is completely
intentional; it distinguishes and (almost) uniquely identifies
development versions. If you are fed u
3 matches
Mail list logo
