[opensuse-buildservice] Keyword Substitution for OSB (osc) like CVS/RCS?!
Is there a keyword substitution in OSB (osc) for inserting revision information into the source codes like in CVS/RCS?! And if not, when we will get it?! Here an example: The source of 'testprog' by User 'testuser' at first 'check in': # $Header$ # $Log$ # $Date$ # $Author$ print "VERSION ".'$Revision$'."\n"; And then after later 'check out' of revision 1.3: # $Header: /RCS/testprog 1.3 2010/08/18 12:00:00 testuser Exp $ # $Log: testprog $ # Revision 1.3 2010/08/18 12:00:00 testuser # Description of changes of this revision... # # ... # # Revision 1.1 2010/08/18 12:00:00 testuser # Initial revision # # $Date: 2010/08/18 12:00:00 $ # $Author: testuser $ print "VERSION ".'$Revision: 1.3 $'."\n"; Regards Guenther -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2010-08-19 10:19:42 +0200, Degenfelder, Guenther wrote:
Is there a keyword substitution in OSB (osc) for inserting revision information into the source codes like in CVS/RCS?!
no
And if not, when we will get it?!
can you send a patch?:) darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thursday 19 August 2010 10:19:42 Degenfelder, Guenther wrote:
Is there a keyword substitution in OSB (osc) for inserting revision information into the source codes like in CVS/RCS?!
And if not, when we will get it?!
I hope never. Please don't send a patch. Keyword substitution is one of the worst mis-features of rcs/cvs. It was meant to allow to identify the status of files even after they are taken out of version control (by, say, shipping them in a tarball). Except that when the files are further modified (for example, by applying patches), that information suddenly becomes wrong. The substituted fields are a real pain when looking at changes with diff: you end up with special versions of diff that can ignore substituted keywords, except when you don't think of it or don't have an "appropriate" version of diff around. And then there are some files which break when they are keyword substituted, so you need to be able to enable/disable keyword substitution on a per-file basis.
print "VERSION ".'$Revision: 1.3 $'."\n";
You can easily include rpm metadata in binaries if desired (version, release, etc.). Thanks, Andreas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Andreas Gruenbacher -
Degenfelder, Guenther -
Marcus Rueckert