will investigate a little more to see how I can plan this.
I will try to get the "intelligent" scripts running over on CSSC on Linux, and have the developers test it for a while to see what they find. Maybe we can use CSSC on a regular basis, saving a lot of time instead of going to CVS. Definitively worth checking...
Thanks again! will send some updates when I move forward on this
On 9/6/06, James Youngman <[EMAIL PROTECTED]> wrote:
On 9/6/06, nestor spedalieri <[EMAIL PROTECTED] > wrote:
> sccs2rcs seems to be planned to be executed in each folder you want to
> convert ( at least thats what I understand) but my repository is a big tree
> with s.* files in some of the leaves (not in everyone of them) and the the
> leaves can be as far as 6 or 7 steps from the repository root. Is my
> understanding about sccs2rcs.csh correct?
I'm not sure myself.
> and if so , whats the best way to
> convert such a tree? ( I dont have any SCCS directory along the branches)
You could do
find src -type d -exec /blah/doconversion {} \;
Where /blah/doconversion might be:
#! /bin/sh
for dir
do
echo converting in $dir
sccs2rcs .... || exit $?
done
... but I have never done this ...
> I read in some archived emails from this list some mentions to a perl
> version of this script, is this a more powerful version? where can I get it?
Not sure.
> This is a more philosophical (or down-to-earth practical, from other point
> of view :-) ) question:
>
> as my conversion involves also converting a lot of shell scripts written
> above SCCS, providing the intelligence for a "user-friendly" version
> interface, to somethgin compatible with CVS, I thought maybe I can divide
> the project and as a first stage go to CSSC on Linux and get the system
> running there and then in the future convert it to CVS. So, my question is,
> is CSSC reliable to have a something running on it on a regular basis? or is
> it just a needed step on the conversion but not a soft to be used for a
> "production" instance?. I have read the caveats on CSSC page about this,
> but wanted to know abotu any implementation that is using CSSC as an engine
> for a day to day version control operation.
There are limitations to CSSC. For example, support for excluded
deltas is partly missing. However, I have never heard of it
corrupting someone's source code repository. I know of a team which
has been using CSSC for a substantial period; they started using it in
about 1998 and, as far as I know, are still using it.
I believe it is the case that the Lucent configuration management
system, "Sablime", uses CSSC to support the Linux implementation.
James.
--
Néstor Spedalieri
[EMAIL PROTECTED]
_______________________________________________ cssc-users mailing list cssc-users@gnu.org http://lists.gnu.org/mailman/listinfo/cssc-users
