The cost of having to build each dependency in Gump drives home that I may be using some weird dependency that no else is using, and is therefore not already in Gump. However, as long as the code remains buildable, it won't be an issue. In the long run, in 5 years when some libarary I am using is no longer maintained, then this will become key information.
Sometimes I just want to build against version XX of a dependency. But this is mostly me being lazy. Eric > -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: Monday, November 01, 2004 12:58 PM > To: Gump code and data > Subject: Re: [proposal] removing non-ASF leaves from the workspace > > > On Monday 01 November 2004 19:29, Eric Pugh wrote: > > > Related to this, I > > am starting to think about dependencies not just in a "is it a good > > dependency to have" but in a "what challenges will having this > dependency > > give me in Gump land", which isn't a great thing... > > Hmmm... I wonder if such thought is a sign of Gump creating > problem for you, > or if Gump amplifies future trouble with external dependencies?? > > > Cheers > Niclas > -- > +------//-------------------+ > / http://www.bali.ac / > / http://niclas.hedhman.org / > +------//-------------------+ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
