To follow up to this, I am planning on package.masking sys-libs/db 4.0 and 4.1
sometime in the near future, to be followed up by their removal in ~30 days.
If this poses a problem to you, a package you maintain, one of your family
members,
or some exotic animal you may or may not own, please let
There is one use-case that I am aware of against removing old versions of 4.*,
but I haven't seen it in the tree for a while - other folk might be more aware
of it: Ability to take DB files from other systems and read them sanely /
migrate them to new versions.
Yep, subversion comes to mind
I'm hoping to advocate some more cleanups in sys-libs/db by proposing the
removal of
4.0.* and 4.1.* from portage. 4.2 has been stable for a long time, with 4.3
unstable and 4.4 and 4.5 available in package.mask.
If anyone has a package that won't work with =sys-libs/db-4.2* please reply.
On Tue, Feb 27, 2007 at 03:45:52PM -0500, Caleb Tennis wrote:
I'm hoping to advocate some more cleanups in sys-libs/db by proposing the
removal of
4.0.* and 4.1.* from portage. 4.2 has been stable for a long time, with 4.3
unstable and 4.4 and 4.5 available in package.mask.
There is one
