The operant development paradigm in RPM has always been to implement,
wait two years and then honk loudly.
On that note, it's time to announce the fork between the "RedHat
Package Manager"
and the "RPM Package Manager" that was taken two years ago publically.
This list is now devoted to the vendor neutral, OSS branch of the
fork, henceforth known
as the "RPM Package Manager". The other branch of the fork is
controlled by Red Hat.
Bound to confuse everyone, can't be helped.
So if you want the "RedHat Package Manager", you are on the wrong
mailing list here.
My rpm sources will be distributed through ftp://jbj.org, and I will
be setting up a CVS repository,
bugzilla, distribution packages, a release roadmap, and web site as I
no longer have
any say in the running of <rpm-list@xxxxxxxxxx> or rpm.org itself.
I fully intend to continue developing RPM as maintainer and primary
architect. If that's
not to your likinbg, I will hand you a tar ball and show you the
door. I wrote this code,
and I'd rather fix existing problems than worry about known issues in
other already released
versions of rpm that I cannot change.
Life's too short to rehash, say, +/- NPTL issues with Berkeley DB, or
diagnose build systems ad nauseum.
rpm-4.4.2 will be the last version that I release that promises
interoperability with
the Red Hat version of rpm.
I hope this starts to clarify a rather muddled situation.
73 de Jeff
|
