From: Kai Krakow <hurikhan77@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Changing dependencies without upping version ??
Date: Wed, 27 Sep 2017 03:35:04 +0200 [thread overview]
Message-ID: <20170927033504.4f7cb5b0@jupiter.sol.kaishome.de> (raw)
In-Reply-To: 20170927013033.swgykevoswge5oer@matica.foolinux.mooo.com
Am Tue, 26 Sep 2017 18:30:33 -0700
schrieb Ian Zimmerman <itz@very.loosely.org>:
> On 2017-09-27 02:38, Kai Krakow wrote:
>
> > If you don't want (or cannot) upgrade, you have two options:
> >
> > 1. Prepare to maintain your own overlay and deal with it
> >
> > 2. Don't use a rolling release distribution
> >
> > Personally, and since you seem to know enough to manage your own
> > overlay, I'd stick to #1.
>
> I do so already, and in fact my initial workaround was to fork the
> ebuild in my repo, pretty much like you recommend.
>
> But I didn't know that this was the official way of stopping upgrades.
> I thought package.mask was that, and I think that's what the Handbook
> (or maybe some other part of the wiki) recommends.
Yes, masking of course. But at some point in time, the ebuild would be
dropped. And you may want to keep it around for rebuilds.
--
Regards,
Kai
Replies to list-only preferred.
next prev parent reply other threads:[~2017-09-27 1:35 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
2017-09-27 0:38 ` Kai Krakow
2017-09-27 1:30 ` Ian Zimmerman
2017-09-27 1:35 ` Kai Krakow [this message]
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=20170927033504.4f7cb5b0@jupiter.sol.kaishome.de \
--to=hurikhan77@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