Re: [Evolution-hackers] building evolution-data-server against the already installed libdb
В Пнд, 27/02/2006 в 17:49 -0500, Mikhail Teterin пишет: I'm trying to convince the maintainers of the evolution-data-server FreeBSD port (http://freshports.org/databases/evolution-data-server) to build the software against the db4-version installed by the separate port of SleepyCat's db4 (http://freshports.org/databases/db43). I'm using the thus built evolution (against db-4.3.29) to type this message, but they remain hesitant, because of the past problems they encountered trying to build evolution using the already installed db3 instead of the version then-bundled with evolution. I'm guessing, you used to have modified version of db3, which allowed it to work, where the standard version did not. Is there anything like that in the db4.1 version bundled with e-d-s 1.4.2.1, or can we safely use any reasonably recent version of db4? Moreover, perhaps, you can be convinced to stop the bundling of db4 completely and turn it into just another pre-requisite? I used to compile e-d-s 1.4 along an external db4.3, by applying a simple patch. It didn't seem to cause any problems. So, what's the purpose of bundling an obsolete version of Berkeley DB inside the project? ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] building evolution-data-server against the already installed libdb
On 3/6/06, Mikhail Zabaluev [EMAIL PROTECTED] wrote: I used to compile e-d-s 1.4 along an external db4.3, by applying a simple patch. It didn't seem to cause any problems. You are of course free to apply your own patches; however, in the long term, using a distribution's version of bdb will probably be an intolerable maintenance burden for either distributors or evolution: So, what's the purpose of bundling an obsolete version of Berkeley DB inside the project? I think the idea was that since the berkeley db API is not very stable, and since distributions ship a wide variety of versions of berkeley db, it would be simpler to ship a version of bdb along with evolution to avoid either (1) requiring distributions wishing to ship evolution to either ship a special bdb just for it, or patch evolution on their own (a big maintenance burden for distributors) or (2) requiring evolution to be compatible against multiple versions of bdb (a big maintenance burden for evolution) Maybe the bdb API is more stable these days so this no longer makes sense; I was under the impression it was still changing quite often. Have fun, Peter ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] building evolution-data-server against the already installed libdb
As far as I can recall, when I asked the same thing, the response was that this is how Berkeley DB is supposed to be used, embedded into another product. That some (all?) Linux distributions choose to also ship a separately installed instance was irrelevant ;) --tml ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
