From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Changing dependencies without upping version ??
Date: Tue, 26 Sep 2017 11:45:45 -0700 [thread overview]
Message-ID: <20170926184544.ng6dzg4njfye4v3u@matica.foolinux.mooo.com> (raw)
In-Reply-To: <0fbc546c-bd8f-a6d9-b3dc-1cdd50fcf336@gentoo.org>
On 2017-09-26 22:01, Michael Palimaka wrote:
> If the only argument is you don't want to upgrade, I'm afraid there's
> not much we can do to help you.
You're right that I don't want to upgrade, and I have already explained
my workaround for that. But that is _not_ what I'm complaining about in
this thread. Rather, my complaint is that such a major change is hidden
in an ebuild edit with no version/revision bump, which means I cannot
use the normal means (ie. package.mask) to prevent it. Before I decided
to drop Qt completely, I had to make a local package of qtcustomplot in
my own repo.
Surely there are other reasons against this kind of thing? What if
someone reports a bug in the package? Now you don't know from the
version/rev number if it's linked with Qt4 or Qt5. Is that not
important?
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
Do obvious transformation on domain to reply privately _only_ on Usenet.
next prev parent reply other threads:[~2017-09-26 18:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 17:37 [gentoo-user] Changing dependencies without upping version ?? Ian Zimmerman
2017-09-24 18:51 ` John Blinka
2017-09-25 0:33 ` Rich Freeman
2017-09-25 8:20 ` Andreas K. Huettel
2017-09-25 7:32 ` Paul Colquhoun
2017-09-24 20:05 ` Neil Bothwick
2017-09-24 22:17 ` [gentoo-user] " Ian Zimmerman
2017-09-25 12:24 ` Michael Palimaka
2017-09-25 17:03 ` Ian Zimmerman
2017-09-26 12:01 ` Michael Palimaka
2017-09-26 18:45 ` Ian Zimmerman [this message]
2017-09-27 0:38 ` Kai Krakow
2017-09-27 1:30 ` Ian Zimmerman
2017-09-27 1:35 ` Kai Krakow
2017-09-27 8:42 ` Neil Bothwick
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=20170926184544.ng6dzg4njfye4v3u@matica.foolinux.mooo.com \
--to=itz@very.loosely.org \
--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