begin quoting Christian Seberino as of Wed, Jan 24, 2007 at 01:08:45PM -0800:
>
> On Wed, January 24, 2007 12:14 pm, Andrew Lentvorski wrote:
> > 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.
^^^^^^^
I suspect you missed a key phrase.
> > 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.
>
> I agree that different Linux platforms are a real headache to target all
> at once....
Actually, I have relatively little problem among the various Linux
distros. (Aside from my continual problems with X and sparc32.)
> What about rather than preemptively learning all your dependency chains,
> just testing on various distros and only looking into it when there is a
> problem? The reality is that at least many apps will survive the distro
> upgrade unscathed.
He's probably been there, done that, and got burned. Probably badly.
Not everyone has fun when development screeches to a halt while a few
people spend a few long, hard, stressful days trying to figure out what
broke.
Habits that work for one or two developers do not scale up well.
--
Long dependency chains aren't a feature.
Stewart Stremler
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
