public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Date: Sat, 19 Dec 2020 10:13:44 -0600	[thread overview]
Message-ID: <79b6f10f-556c-d21a-356e-870071ef7e6a@gmail.com> (raw)
In-Reply-To: <20201219155450.00df95ff@digimed.co.uk>

Neil Bothwick wrote:
> On Sat, 19 Dec 2020 15:11:34 +0100, n952162 wrote:
>
>
>> I update the /etc/portage/package.use files by hand, so I get a feeling
>> for how it works.  Can it be that etc-update is a "smart system" that
>> does more than just that?
> Yes, read the docs, it merges the old and new configs. I prefer to use
> conf-update but all the config managers do much the same thing.
>
>

There's also dispatch-conf as well.  I can't recall how many config
managers there is but each seems to work a little different.  I'd
suggest OP try them all and then pick the one they like the best.  I
like dispatch-conf but others like something else.  Either of them gets
the job done. Oh, some can also be configured to have fancy colors and
such as well.  Let's complicate things a little more.  :/ 

Just another option, as if there wasn't already some mentioned.  lol 

My opinion on the upgrade problem; I'd look at the world file, maybe
even post it here, to see what has crept into it that shouldn't be there
or is no longer in the tree.  I had to unmerge several packages recently
to get a update done.  Some died ages ago.  They were related to old
python versions if I recall correctly. 

Dale

:-)  :-) 


  reply	other threads:[~2020-12-19 16:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 10:24 [gentoo-user] override PYTHON_TARGETS to avoid a slot collision n952162
2020-12-16 10:34 ` Miles Malone
2020-12-16 10:59   ` Arve Barsnes
2020-12-19 10:20     ` n952162
2020-12-19 10:45       ` William Kenworthy
2020-12-19 11:15         ` n952162
2020-12-19 10:56       ` Arve Barsnes
2020-12-19 11:12         ` n952162
2020-12-19 11:35           ` Neil Bothwick
2020-12-19 14:19             ` n952162
2020-12-19 15:49               ` Neil Bothwick
2020-12-19 12:34           ` Arve Barsnes
2020-12-19 11:12       ` bobwxc
2020-12-19 11:33         ` n952162
2020-12-19 11:37           ` Neil Bothwick
2020-12-19 11:51             ` Michael
2020-12-19 12:02               ` Jude DaShiell
2020-12-19 11:35       ` Michael
2020-12-19 14:11         ` n952162
2020-12-19 15:54           ` Neil Bothwick
2020-12-19 16:13             ` Dale [this message]
2020-12-20 13:58       ` Róbert Čerňanský
2020-12-16 11:07   ` n952162
2020-12-16 11:20     ` Miles Malone
2020-12-16 11:22     ` Miles Malone
2020-12-16 12:25       ` Dale
2020-12-19  9:39   ` n952162
2020-12-16 10:56 ` bobwxc

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=79b6f10f-556c-d21a-356e-870071ef7e6a@gmail.com \
    --to=rdalek1967@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