From: Andrew Udvare <audvare@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Help with dev-util/cargo blocking dev-lang/rust.
Date: Sun, 18 Nov 2018 00:33:41 -0500 [thread overview]
Message-ID: <b238e795-6af3-b1e4-49db-b64677c338e0@gmail.com> (raw)
In-Reply-To: <9c01349e-3ddd-7774-5732-2a637682e96c@spamtrap.tnetconsulting.net>
[-- Attachment #1.1: Type: text/plain, Size: 880 bytes --]
On 18/11/2018 00:23, Grant Taylor wrote:
>
> I'm not completely sure what that means. I'm guessing you're asking
> about accept_keywords. I'm mostly (?) running stock amd64. I have
> added ~amd64 to some packages for various reasons over the 2+ years that
> this install has been around.
I switched fully to ACCEPT_KEYWORDS="~amd64" (make.conf) after running
mixed for a while. These kinds of issues come up too often and I don't
have a lot of time to solve them, plus for my dev machine I just don't
notice stable vs unstable most of the time. If something is truly
unstable from my own experience I will mask that version and downgrade.
My recommendation would be to switch over to ~amd64 for a workstation
generally. On my home server I run stable with a few unmasks, but most
of the time these are packages that have no dependencies.
--
Andrew
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-18 5:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 0:24 [gentoo-user] Help with dev-util/cargo blocking dev-lang/rust Grant Taylor
2018-11-18 1:11 ` Andrew Udvare
2018-11-18 1:16 ` Adam Carter
2018-11-18 1:29 ` Andrew Udvare
2018-11-18 2:52 ` Adam Carter
2018-11-18 2:53 ` Grant Taylor
2018-11-18 2:55 ` Adam Carter
2018-11-18 2:58 ` Adam Carter
2018-11-18 4:53 ` Grant Taylor
2018-11-18 5:13 ` Andrew Udvare
2018-11-18 5:23 ` Grant Taylor
2018-11-18 5:33 ` Andrew Udvare [this message]
2018-11-18 5:46 ` Grant Taylor
2018-11-18 13:13 ` Neil Bothwick
2018-11-18 13:37 ` Ralph Seichter
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=b238e795-6af3-b1e4-49db-b64677c338e0@gmail.com \
--to=audvare@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