On Sat, Jun 14, 2014 at 8:40 AM, Reindl Harald <h.reindl(a)thelounge.net> wrote:
> Depends obscure options that are hardly used by the majority of
users
> are different from common options that everyone uses.
"dnf remove yum dnf kernel" ruins your system
yum don't allow that for good reasons
that's unacepptable behavior and was refused to change
Amen. It's too easy to trip over subtle automated dependencies,
especially the "python" dependencies, in environments where older and
newer pythons are being tested out.
> FWIW using a CLI interface to automate things is imo the wrong
> approach if there is an api that can be used instead (cleaner, less
> hacky, more efficient, etc) (and yes this changes here too, because
> the old API was really horrible but that's not the point)
no idea what is your daily job, sysadmin obviously not
shell scripts are the Unix way and overall more efficient
just because you write tiny scripts for different tasks
and plug them together - efficient is not only a matter
of runtime measure
This is a common approach for people being taught object oriented
approaches: they're taught that the sophisticated top down approach
will resolve a lot of problems. But the layers of abstraction,
themselves, introduce profound fragilities. It's *amazing* the
absurdities that are committed by sophisticated GUI's and API's on top
of what is actually a small set of binary commands and can be a small
set of well defined shell wrappers. (And yes, NetworkManager and
/etc/sysconfig/network, I'm staring straight at *YOU* when I say
this.)