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

Bug#930595: RFS: uacme/1.0.15-2 [ITP]



On Mon, Jun 17, 2019 at 05:59:17PM +0800, Paul Wise wrote:
One should always build everything from source as often as possible.
Also remove build products from upstream VCSen and tarballs (except
autotools cruft).

I generate the original tarball by tagging master with 'vX.Y.Z', then './configure' and 'make dist' (note master does NOT include a /debian directory). Then I feed the tarball to gbp import-orig, which automatically updates the upstream/latest, pristine-tar and debian/master branches. The end result is that the contents of any pristine tarball uacme_X.Y.Z.orig.tar.gz are archived as upstream/X.Y.Z and the tarball can be regenerated at any time from the repository by pristine-tar. I always build with 'gbp buildpackage' from the debian/master branch which does a full build from source every time.

When I want to make a debian release I update and commit debian/changelog on the debian/master branch, then use gbp buildpackage --git-tag which builds the package and additionally makes a tag of the form 'debian/X.Y.Z-N'

Regarding the manual pages (uacme.1 and uacme.1.html), they are rebuilt from their source (uacme.1.txt) by default unless configure is run with --disable-docs.


You may want to read through our upstream guide:

https://wiki.debian.org/UpstreamGuide

Yes, I've gone through this, thanks.

To conclude, is there anything else I need to change to make it worthy of inclusion in debian?


Reply to: