[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: CVS corrupts binary files ...

From: Paul Sander
Subject: RE: CVS corrupts binary files ...
Date: Fri, 2 Jul 2004 12:49:58 -0700

>--- Forwarded mail from address@hidden

>[ On Wednesday, June 30, 2004 at 22:59:27 (-0700), Paul Sander wrote: ]
>> Subject: RE: CVS corrupts binary files ...
>> >(A) they're not "sources" -- they're intermediate product files.
>> They're not "intermediate product files" unless they can be reproduced
>> from some other source using an established process.

>Yes, they are intermediate product files.  Just because their ultimate
>source code is managed by someone else doesn't change the fact that they
>are not sources for the local project -- indeed it only confirms it.

In other words, you're trying to integrate your vendor's CM process into
some global, all-encompassing process that also happens to include yours?

Well, in my world, there are boxes around my process and my vendors.
The boxes have well-defined inputs and outputs, and anything in my box
is subject to my process.  And artifacts that can't be derived from other
artifacts automatically are treated like sources.  And rightly so.

>The "established process" is to repeat whatever process you did to get a
>copy of those intermediate product files in the first place!

>What's so bloody hard to understand about this?  It's extremely basic!!!

So, what you're proposing is to use the vendor's distribution media and
an offline archival system for version control, and a written installation
procedure to put it somewhere (hoping that whatever local configuration
options get used once are repeated next time), and assuming that the
installation procedure provides a hook so that you can manage your
installations as baselines?  And you re-install by hand and patch for
every bug fix?

Yeah.  Right.  Get real.

>--- End of forwarded message from address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]