Tricky update

[s***@o2.pl]

I'm looking for a way to make an update on a project with a single
command(it would be nice if it was just a "cvs update") which makes a
regular update(-Pd) for almost all of the files in project and
overwrite update(-C) for a small subset of all files. The goal is that
the end user of repository does not have to do these updates manually

[Spiro Trikaliotis]

Hello,

Post by s***@o2.pl
I'm looking for a way to make an update on a project with a single
command(it would be nice if it was just a "cvs update") which makes a
regular update(-Pd) for almost all of the files in project and
overwrite update(-C) for a small subset of all files. The goal is that
the end user of repository does not have to do these updates manually

Isn't a script a viable solution?

Best regards,
Spiro.

[Arthur Barrett]

Post by s***@o2.pl
I'm looking for a way to make an update on a project with a single
command(it would be nice if it was just a "cvs update") which makes a
regular update(-Pd) for almost all of the files in project and
overwrite update(-C) for a small subset of all files. The goal is that
the end user of repository does not have to do these updates manually

In CVSNT (GPL like CVS, runs in linux like CVS) you'd set the 'small
number of files' to be 'static' with cvs update -ks filename.ext; cvs ci
-f -m "change to static" filename.ext. This is a special CVSNT
keyword-mode that means that whenever the file changes all users should
get the change - however when a user makes a change to a static file it
is not committed to the repository in the 'normal' way (you need to do a
'force commit').
http://www.cvsnt.org/manual/html/Substitution-modes.html

In CVS I don't know how you'd do this.

Regards,


Arthur

[Socki]

Thank you for answering. Keeping original cvs is required so I will
consider using some kind of a script.

Thank you again,
Kamil Wysocki