On Wed, Jun 11, 2014 at 11:25:31AM -0400, Rahul Sundaram wrote:
Hi
On Wed, Jun 11, 2014 at 11:20 AM, Jan ZelenA 1/2 wrote:
The transition period is one reason why we want to keep the name dnf.
We'd
basically like to keep current yum around for users that have various
scripts
and stuff depending on it so they have some time to migrate to dnf.
I would suggest doing it the other way around.A A Rename old yum to
yum-legacy.A Rename dnf to yum and at the end of the transition period
drop yum-legacy and retain yum as the command line name.A A For any
deprecation options, warn on them and suggest the supported alternative.A
With your current plan, after the transition period, everyone has to
retrain themselves to type dnf instead of yum which I don't think is
necessary.A
If the idea is interesting it does imply that each person having scripts
depending on yum has to:
* s/yum/yum-legacy/
- Deploy to prod and run as before
* s/yum-legacy/dnf/
- Test and ensure it has a consistent behavior w/ yum (that the script is not
using any of the deprecated options, that there is no some surprises in some
weird corners)
So the scripts need to be updated twice against once if we just let dnf be dnf
and eventually let it provide a /usr/bin/yum optionally.
Pierre