public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ashley Dixon <ash@suugaku.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] docutils needing py2.7, but not wanting py2.7?
Date: Thu, 4 Jun 2020 23:42:50 +0100	[thread overview]
Message-ID: <20200604224250.y7xq66qok54svn4t@ad-gentoo-main> (raw)
In-Reply-To: <f3996c17-eef8-ee5e-28ee-d493e04c532d@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

On Thu, Jun 04, 2020 at 05:31:29PM -0500, Dale wrote:
> Neil Bothwick wrote:
> > Allow portage to add the changes to your config, then run etc-update or
> > equivalent. When portage adds package.use changes, it also adds comments
> > showing what requires those changes. With that information, you should be
> > able to see which package is causing this.
> 
> One of us is reading that wrong.  Given my eyes, maybe it is me.  My new
> glasses should be in within the next week or so.  In the first instance,
> it wants py2.7 disabled.  So he adds it to the config file to disable
> it.  When he runs the command again, it wants to enable py2.7 for the
> same package and version.  If I'm reading that right, even if he lets
> emerge add the change, it will lead to two problems.  One, there will be
> one line enabling py2.7 and another line disabling it.  If I recall
> correctly, emerge will take the last one.  Two, he will be back to the
> first problem, it wanting py2.7 disabled.  In other words, back where he
> started. 
> 
> Am I reading that wrong or something?? 

Providing he's just adding the line to a package.use file with  a  text  editor,
that's just manually doing the work of etc-update.  We need the  `emerge  --info
docutils` output to see full information about his Python environment.

-- 

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-04 22:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 21:24 [gentoo-user] docutils needing py2.7, but not wanting py2.7? Caveman Al Toraboran
2020-06-04 21:43 ` Ashley Dixon
2020-06-04 23:38   ` Caveman Al Toraboran
2020-06-05  0:20     ` Ashley Dixon
2020-06-05  0:54       ` Caveman Al Toraboran
2020-06-05  1:08         ` Ashley Dixon
2020-06-05  1:17           ` Caveman Al Toraboran
2020-06-04 21:47 ` Dale
2020-06-04 22:14 ` Neil Bothwick
2020-06-04 22:31   ` Dale
2020-06-04 22:42     ` Ashley Dixon [this message]
2020-06-04 22:56       ` Dale
2020-06-04 23:06         ` Ashley Dixon
2020-06-04 23:39           ` Sean O'Myers
2020-06-04 23:49             ` [OT] " Ashley Dixon
2020-06-05  8:09       ` Neil Bothwick
2020-06-05  8:43         ` Dale

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=20200604224250.y7xq66qok54svn4t@ad-gentoo-main \
    --to=ash@suugaku.co.uk \
    --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