Who maintains RPM?
Posted Aug 23, 2006 3:02 UTC (Wed) by skvidal
In reply to: Who maintains RPM?
Parent article: Who maintains RPM?
the problem with the soft dependencies is that we've got no defined semantic for handling them automatically. Additionally, we have no policy to keep someone from doing:
and having their package pulled in EVERY time.
This, among other reasons, is why we wanted to stage in things like Suggests/Enhances - the soft deps.
We wanted to be able to know when those things would go in. And since they would have fairly far-reaching impact gracefully add them - probably as a major point release or at the very least not a minor.minor release.
I think it would be radical and exciting if rpm had:
1. a roadmap
2. a development cycle based on time or at least based on feature
3. some concept that some features break things or cause other havoc so they need to cycle them through in something other than point release.
to post comments)