Public SourceMage Discussion List

[Seth Alan Woolley <seth AT positivism.org>]

Hi SMGLers,

I propose we support a PATCHLEVEL variable, entirely optional, but if it
is set, it would add a suffix to the VERSION for what gets recorded in
the sorcery state information (for gaze version and when to figure out
when to recompile).

This would mean a spell that has a SOURCE_DIRECTORY of $SPELL-$VERSION
wouldn't need to be edited all over the place to add a simple patchlevel
for a security update that is not part of the standard vendor
distribution path (say the vendor is on a break or something or it's a
long time between releases even with security updates in the queue).

This would eliminate the need to use UPDATED or CREATED.  Both of these
are covered in the HISTORY as far as I'm concerned, and it seems like
unneeded maintanence.  If PATCHLEVEL goes in, I'd like to see these two
fields deprecated and removed from devel/test after the next stable
integration.

I don't have a patch to implement this yet, but I could whip one up. 

Implementation would just require that PATCHLEVEL (and optionally
FULL_VERSION) be added to the list of variables that are cleared in
run_details and have some small magic after run_details until cast is
complete and written to the sorcery state information to change VERSION
to FULL_VERSION, where FULL_VERSION="$VERSION-$PATCHLEVEL" if PATCHLEVEL
is defined, else FULL_VERSION="$VERSION".  At the same time, one could
check to see if FULL_VERSION is set at that point and opt to use it
instead of doing the VERSION-PATCHLEVEL concatenation if say the version
used in the filename is so far off whack you want to totally rewrite it.

Comments?

-- 
Seth Alan Woolley [seth at positivism.org], SPAM/UCE is unauthorized
Key id EF10E21A = 36AD 8A92 8499 8439 E6A8  3724 D437 AF5D EF10 E21A
http://smgl.positivism.org:11371/pks/lookup?op=get&search=0xEF10E21A
Security Team Leader Source Mage GNU/Linux http://www.sourcemage.org

Attachment: pgpwj0lmmKBh8.pgp
Description: PGP signature