Hi PeterC,
[snip]
>1. Don't bother - don't make it widely available, and hope the fact it
> announces 1.5.0 as a version (for my git HEAD + ... +
> cairo_experiment branch code) won't cause too much grief with a
> restricted distribution.
>
>2. Leave the version string as is (I'm not sure if we have
> infrastructure to add a git SHA1 to the version?), and patch the
> code which prints in the log, and the about box, to make clear what
> the release really is.
I do not really care much for the above two options as then the
poor user doesn't know what version they are running and you won't either.
>
>3. Try to add something to the version string:
> 1.5.0.20080706~79384bb59399cb084c6d6ccebe9725080d363c99
Yikes!
>
> (Perhaps truncating the SHA1 at some point)
>
> or:
>
> 1.5.0.20080706~pcjc2.cairo_experiment.release1
That might be okay. You can achieve a custom branding/version of gEDA/gaf
by going into libgeda/include/defines.h and modifying (line 46):
#define PREPEND_VERSION_STRING ""
Please define a string that includes at least: "pcjc2".
Also, I would really prefer it the w32 releases be hosted on server
that you control or, as you suggested, given out on-demand.
Thanks,
-Ales
_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
