script classification ...

Hello,

I have written an add-on script for the `Revision Control System' (RCS)
package. For more information about its functionality, see the README part
below.

I would suggest the following script categories

Version Control
Software Configuration Management
Software Development


From the README:
----------------
rcsfreeze.pl is a perl script to freeze a configuration of
sources checked in under RCS.

This perl script is a complete rewrite of the rcsfreeze.sh shell
script contained in the RCS package with its RCS ID:
$Id: rcsfreeze.sh,v 4.6 1993/11/03 17:42:27 eggert Exp $.
The major differences between the shell script and the perl
script are the following:
the input argument "symb revision number"
- is optional for the shell script. Internally an unique
revision number is used.
- is mandatory for the perl script. Only this symbolic
revision number is used.
the log message
- is saved by the shell script in its own file
rcsfreeze.log. But there are no tools available to
retrieve the log messages for a given revision number.
- is saved by the perl script amongst the other RCS log
messages. Therefore they can be retrieved with the
appropriate rlog command.


I am looking forward to your comments.

Norbert
--
+------------------------------------------------------------------+
+------------------------------------------------------------------+

Dear all,

on Sept 17th and on Sept 28th, I have sent a query to this mailing list
about the classification for my perl script. But I never got any reply :-(

Did I anything wrong ??? I would appreciate any information.

Thank you in advance.

Norbert Gruener
--
+------------------------------------------------------------------+
+------------------------------------------------------------------+

Hello,

I have written an add-on script for the `Revision Control System' (RCS)
package. For more information about its functionality, see the README part
below.

I would suggest the following script categories

Version Control
Software Configuration Management
Software Development


From the README:
----------------
rcsfreeze.pl is a perl script to freeze a configuration of
sources checked in under RCS.

This perl script is a complete rewrite of the rcsfreeze.sh shell
script contained in the RCS package with its RCS ID:
$Id: rcsfreeze.sh,v 4.6 1993/11/03 17:42:27 eggert Exp $.
The major differences between the shell script and the perl
script are the following:
the input argument "symb revision number"
- is optional for the shell script. Internally an unique
revision number is used.
- is mandatory for the perl script. Only this symbolic
revision number is used.
the log message
- is saved by the shell script in its own file
rcsfreeze.log. But there are no tools available to
retrieve the log messages for a given revision number.
- is saved by the perl script amongst the other RCS log
messages. Therefore they can be retrieved with the
appropriate rlog command.


I am looking forward to your comments.

Norbert
--
+------------------------------------------------------------------+
+------------------------------------------------------------------+

I vote for the broader "Software_Development" category.

Rich

Yes, or "Software_Development/Version_Control" ?


.Robin
Radioactive cats have 18 half-lives.

I think that Version_Control is more suitable. People use RCS
and other revision control systems for other things beside software.
If there's strong feeling for putting it under a Software_Development
hierarchy, then I would favor dual-categorization (e.g., Version_Control
_and_ Software_Development/Version_Control).

Peace,
* Kurt Starsinic (Kurt.Starsinic@isinet.com) --------- Technical Specialist *
Institute for Scientific Information http://www.isinet.com/

Isn't "version control" exclusively an activity related to "software
development"? Unless you think that there would be no other categories below
software development? ;)

David

_________________________________________________________________________
David Coppit - Graduate Student david@coppit.org
The University of Virginia http://coppit.org/
"Yes," said Piglet, "Rabbit has Brain." There was a long silence.
"I suppose," said Pooh, "that that's why he never understands anything."

On Sun, 3 Oct 1999, David Coppit wrote:

[..]
No, here we use it for pretty much everything (of course software code,
but also configuration files, database tables, installation scripts, etc
etc). Actually, we even use CVS for some of our software distribution
(among the servers, that is).


- ask

Well, my first choice would be just "Version_Control" :-)

Norbert

Hello Kurt,
I just wanted to ask about the present status of my inquiry. Is there a
final agreement and if so what is it ?

Best Regards,

Norbert
--
Ceterum censeo | PGP encrypted mail preferred.
Redmondem delendam esse. | PGP Public Key at www.MPA-Garching.MPG.DE/~nog/


PS: on Sun, 3 Oct 1999, Kurt D. Starsinic wrote:
Excuse me, if I am penetrative, but what is the status of the "upload
strategies" ?

...
...

I thought that we resolved this, but apparently we never did.
Version_Control had the most support when we discussed this. Let's go
ahead and get that category created for Norbert.

Rich

Done and done.

Peace,
* Kurt Starsinic (Kurt.Starsinic@isinet.com) --------- Technical Specialist *
Institute for Scientific Information http://www.isinet.com/

OK, makes sense to me. I only use VC for software. But, now that you
mention it, there's a strong argument for doing it with config files and
a variety of other things. Let's go with Version_Control rather than the
40-character monstrosity! ;-)

Rich

Um, what about "Configuration_Management", which is a bit broader, and
whose abbreviation is nearly universally understood?