Christian Seberino wrote:
am unwilling
to put up with SVN's massive dependency chain to actually get it to
compile on all of my machines, I have yet to use SVN in earnest.
Man I'd be afraid to try to sell you something. Just do
'apt-get install subversion' or some such and get on with life.
Man, I'd be afraid to let you run a software development group.
If you are developing software, you have to *know* your dependency
chain. Choosing a dependency of "RedHat Enterprise Linux 4" gets you in
massive trouble when something breaks.
What caused subversion to break? Was it an upgrade to libc? libssh?
subversion? The filesystem? Permissions? etc.
In software development, you try to isolate the dependency chain, and
you compile everything *yourself*. Tools that you use get compiled
internally and checked into your source control system (interesting
bootstrap problem, that ...). That way if you need a newer version
(because, say, there is a 256 character limit in a buffer somewhere) or
need an older version (new bug, completely destroys old repositories)
you can do it.
In VLSI, we were far more strict about that than even software. All
scripts were required to compute and store the MD5 hash of all binary
executable files, configuration files, and data files which were going
to be used. That way we could pull a version and literally re-create
the run. The reason for this is exactly the problem above. Cadence
would "upgrade", and a gazillion things would break and then we'd have
to hunt them all down. With the hashes, we could identify changed tools
and files immediately.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
