<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-06-12 9:30 GMT+02:00 Jan Zelený <span dir="ltr"><<a href="mailto:jzeleny@redhat.com" target="_blank">jzeleny@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> It boils down to this: someone is going to be inconvenienced. I argue<br><div class="">
> it's better to inconvenience the minority with special 'yum' needs by<br>
> making them use the 'yum-old' alias, rather than inconveniencing the<br>
> majority by making everyone switch their scripts and fingers to 'dnf'.<br>
<br>
</div>As I said, we will have transition layer so using yum in your shell scripts<br>
will still work for a few more releases. A vast majority of users should not<br>
experience any inconveniences other than different output on the command<br>
line.<br></blockquote></div>… <i>now</i>, but <i>will be inconvenienced later</i> after those “a few more releases” when you are planning for the yum command to go away. The total breakage and total impact on users is the same, you are only arguing for a different timing that makes it seem like a smaller breakage.<br>
<br></div><div class="gmail_extra">(And separately, I don’t buy the argument that this redirection-with-a-message is how users learn about the new tools. This way they only learn about the <i>most useless</i> part of the change, namely “that old thing the system used to do? It can do the same thing, but in addition you have to learn a new command to keep it working“. It doesn’t teach <i>the useful part</i>, “here are the new features and here’s how to use them" at all.)<br>
</div><div class="gmail_extra"> Mirek<br></div></div>