From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: sans-dbus was: gnome intrusion?
Date: Sat, 19 Nov 2016 16:34:55 -0600 [thread overview]
Message-ID: <CADPrc80J5JevgXW=V+jr6BH+9HPs+toP00GV1_ox_cNeiVqRLA@mail.gmail.com> (raw)
In-Reply-To: <20161119211734.12746.24E6124D@matica.foolinux.mooo.com>
[-- Attachment #1: Type: text/plain, Size: 2551 bytes --]
On Sat, Nov 19, 2016 at 3:23 PM, Ian Zimmerman <itz@primate.net> wrote:
[ ... ]
> Why
> should I have to learn all that huge amount of information, crowding out
> things I actually _like_ to know from my declining memory, to keep control
> of my computing?
Because you didn't wrote the code. Someone else did, and you are using it
free (as in beer and as in freedom). Therefore, you don't get a say on what
dependencies the code should or shouldn't rely on.
You don't like a dependency? Use other software that doesn't use it; be
warned that it will almost for sure be less capable that the one that uses
dbus.
You don't want to stop using the software, but you don't want the
dependency? Then write patches for the software that allow the dependency
to be dropped; be warned that said patches will most probably be rejected,
since the maintainers have to think in the *generality* of its users, not
in your particular case, and therefore the dependency (dbus in this case)
makes perfect sense and make their lifes *sooooo* much easier.
You still insist on not using the dependency? Then fork the code and
maintain it yourself. You will quickly see why the maintainers decided to
use dbus.
The real solution is, as Alan said, understanding the reason of the
dependency and reaching the completely logical conclusion that the
maintainers were 100% right on deciding to depend on dbus, because it's the
bee's knees.
You are right: it's your computer and you have the right to decide what
does it runs and what it doesn't (that's why you run a Free Software BIOS
and no proprietary firmware at all, right?) But you don't get to complain
about the choices that other software's authors take about dependencies and
requirements for said software: if you don't like it, stop using it or
contribute to changing it (with the very real possibility that your
contributions will be rejected).
You don't *have to* learn a huge amount of information about dbus; but it
will help you to understand why so many in this thread see the dbus
dependency as perfectly reasonable.
Or don't learn nothing about dbus, but then stop complaining about why some
software uses it, and be happy to enjoy its many many advantages. And the
fact that is Free Software, and you can study and learn from the code if
you so desire at some point in the future.
Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México
[-- Attachment #2: Type: text/html, Size: 2811 bytes --]
next prev parent reply other threads:[~2016-11-19 22:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 9:32 [gentoo-user] gnome intrusion? Jorge Almeida
2016-11-14 17:37 ` [gentoo-user] " Ian Zimmerman
2016-11-14 19:03 ` Jorge Almeida
2016-11-14 20:37 ` Kai Krakow
2016-11-14 21:49 ` Jorge Almeida
2016-11-14 23:51 ` Kai Krakow
2016-11-16 12:47 ` [gentoo-user] sans-dbus was: " Miroslav Rovis
2016-11-16 18:42 ` Jorge Almeida
2016-11-17 1:48 ` Rich Freeman
2016-11-17 7:56 ` [gentoo-user] " Ian Zimmerman
2016-11-17 9:08 ` Rich Freeman
2016-11-19 9:21 ` Kai Krakow
2016-11-19 19:06 ` Ian Zimmerman
2016-11-19 19:16 ` Rich Freeman
2016-11-19 20:47 ` Ian Zimmerman
2016-11-19 21:07 ` Alan McKinnon
2016-11-19 21:23 ` Ian Zimmerman
2016-11-19 22:34 ` Canek Peláez Valdés [this message]
2016-11-19 22:36 ` Alan McKinnon
2016-11-20 0:36 ` Walter Dnes
2016-11-19 21:59 ` [gentoo-user] " Tom H
2016-11-19 22:15 ` Rich Freeman
2016-11-20 18:40 ` [gentoo-user] " Kai Krakow
2016-11-14 23:38 ` [gentoo-user] " Andrew Tselischev
2016-11-14 23:52 ` Jorge Almeida
2016-11-15 17:39 ` [gentoo-user] " Ian Zimmerman
2016-11-15 19:23 ` Jorge Almeida
2016-11-15 19:32 ` Alan McKinnon
2016-11-15 19:45 ` Jorge Almeida
2016-11-16 2:10 ` [gentoo-user] " Walter Dnes
2016-11-16 7:23 ` Jorge Almeida
2016-11-16 9:08 ` Neil Bothwick
2016-11-16 11:25 ` Jorge Almeida
2016-11-16 20:51 ` [gentoo-user] " Kai Krakow
2016-11-16 21:20 ` Jorge Almeida
2016-11-17 20:42 ` [gentoo-user] " Frank Steinmetzger
2016-11-17 20:49 ` Jorge Almeida
2016-11-17 23:32 ` Frank Steinmetzger
2016-11-14 23:55 ` [gentoo-user] " Kai Krakow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADPrc80J5JevgXW=V+jr6BH+9HPs+toP00GV1_ox_cNeiVqRLA@mail.gmail.com' \
--to=caneko@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox