On 11/01/2010 12:14 PM, Brian Gough wrote:
At Sat, 30 Oct 2010 00:57:37 +0200,
Henrik Sandklef wrote:
Before pushing/comitting the new settings and sha256 into the main
trunk I wonder if if anything has been decided on how to generate the
sha256sums in a "formalised" way?
You can make them with
make makesums
>
Thanks!
Guess I should have seen that...
If you need to skip the GPG check,
make makesums GPGV=/bin/true
For the main trunk the packages are only supposed to be release
versions. I haven't decided how to handle alpha versions yet. There
are two options - a separate directory for alpha releases, or put them
in the same makefile somehow (e.g. with conditionals).
I wouldn't mind the option of being able to test BOTH one alpha AND one
"real" release. I'd prefer one Makefile (to rule them all) without
conditionals, e.g
GARNAME = xnee
GARVERSION = 3.07
GARVERSION_ALPHA = 3.07.91
MASTER_SITES = $(MASTER_GNU)
MASTER_SITES_ALPHA = $(MASTER_GNU_ALPHA)
MASTER_SUBDIR = xnee/
MASTER_SUBDIR_ALPHA = xnee-alpha/
.... Doing tests on nightly "CVS" dists is, IMHO, overkill in this case
I think.
/hesa
