Could you clarify a bit?
Quote:
Originally Posted by sahko
(Post 3525063)
AFAIK db is used by python, ruby, perl and web related stuff like apache etc, so its a pretty important package.
|
Are you sure it is "used by"? I always thought that python/ruby/perl have db bindings that allow them to access db data, but I never heard of any dependency on db. Apache can run applications that use db but I never heard that Apache is dependent on it. More so, I always thought that Apache requires a special module to run apps that use db safe. Thus, it looks like "can be used with", not "used by". If the above is not the fact, please explain since this is important in any db talk.
Quote:
Originally Posted by rworkman
(Post 3525315)
Understood, but the main point was this: is there something that won't build/work properly due to our old(er) version of bdb? That's a serious question - I'm not being an asshole :-)
|
The db packages describe themselves as "This package should be installed if compatibility is needed with databases created with the Berkeley DB version 4.2.x." If this is correct, everything should build/work properly with what we have until a data file created with version 4.3, 4.5, 4.6, or 4.7 is hit. So, the answer to the question may be "nothing", but this is meaningless in the context of package selection. Apps that actually use db may compile fine but reduce functionality if an older version of db is offered, like "no 4.7 - no heterogeneous replication".
Why not drop both 42 and 44 and add 4.6 and 4.7?
|