RE: checkout hook; user defined keyword

[Arthur Barrett]

Joachim,

> We are fixed to SuSE/Novell distributions at the server as 
> well as at the 
> clients. I.e. we have CVS (not CVSNT) and cannot install a 
> patched server. 
> Maybe I can escalate the problem and get it thru.

Just to clear up any possible misconception - yes CVSNT does run on SuSE
SLES.

On the commercial support side I know of at least one customer with
hundreds of users who runs SLES9 x64.  However 'crossgrading' from CVS
to CVSNT with an installation base of 100's of users does require some
forethought, planning and risk management.

> Is there a way to get a script running in update/checkout? 
> The program options 
> in the moudles file work only, if a module is checked out, 
> but not for an 
> update, when single (modified) files are fetched from the repository.

Not to the best of my knowledge, the server doesn't (shouldn't) affect
the client that way.

If the CVS distribution that comes with your SuSE install is not
providing the business functions you require then I think you need to
consider what is more important - getting the business done or keeping
your SuSE toolchain intact.

Completely off topic? I often wonder about the bloat in linux (and even
some unix) distributions - should databases, team collaboration suites
and customer/employee portals be shipped as part of the OS?  I may
want/need to upgrade my Solaris install from 01/09 to 04/09 to ensure
the latest security patches are in place, but the suggestion that I
couldn't upgrade my Oracle from 10g/r1 to 10g/r2 until I upgrade to
Solaris 11 would be incomprehensible - so why is that the case with
MySQL or CVS?

If you are using the 'bundled' database or version control software for
a couple of inconsequential 'developer initiated' projects then using
the vendors support and release recommendations probably makes sense.
But once you get to a point where CVS/CVSNT/SVN or MySQL or Apache is
running your enterprise then I believe that you need to treat that
software separately to the OS, both in terms of support requirements and
upgrade schedule since the business drivers for that software are
different to the business drivers for the underlying OS.

Regards,


Arthur Barrett