I am updating db3 and db4 at the moment, just checking that it'll build and install properly, please be patient, I have to go to work soon, but they'll be fixed later today.
db3 and db4 shlibs can live happily together. db4 is a new major version, so is presumably incompatible with db3. Max actually told me about the db31 package, but I forgot to look at it and check for conflicts, sorry. Peter On Wednesday, April 10, 2002, at 08:39 AM, Chris Devers wrote: > On Wed, 10 Apr 2002, Martin Costabel wrote: > >> Alexander Hansen wrote: >>> >>> The problem is that db3 and db31 both provide db, and fink >>> doesn't want >>> to remove db31 in preference to db3, because you have a package that >>> requires db31 explicitly, (Evolution?) >> >> You are right, I hadn't seen this. Other packages depend on db3 >> explicitly, so there is no easy way out right now. You have to choose >> one or the other. > > Is there any particular reason that db3 and db4 can't coexist? > Is db4 not > backwards compatible, or buggy, or something? Or for that > matter, is there > any benefit that db4 provides over db3 that would make it > worthwhile, even > if porting some software might introduce bugs? I would hope that this > can't be a problem, if the interface remains the same -- but does it? > > I'll admit that I'm [obviously] not aware of the version details or how > they might differ, I'm just used to using & working with higher level > wrappers like DBM, and not with DB* directly. It just seems > annoying that > the two versions have difficulty co-existing (or the newer one > can't just > supercede the older). > > _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
