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