On 17/02/2022 07:42, Dale wrote:
I also commented out as much as I could in
package.use, the things I'd tried previously. Now it has a clean path
to upgrade.
Is package.use a file or a directory? If it's a file, convert it to a
directory (you can just put the existing package.use file in the
Hi Miles,
This install is likely over 10 years old. I might add, I copied a lot
of things over from my previous system which was a AMD 2500+ single core
puter. In a way, some things could be dating back to around 2003 or
2004. I use eix-test-obsolete to clean up package.* files but there
isn't
threads very rarely makes sense for anything, btw.
On Thu, 17 Feb 2022 at 21:41, Miles Malone
wrote:
>
> Now for your own sanity you might consider stopping adding things
> globally constantly, and using app-portage/flaggie to sanely manage
> them per-package... Cause there's far more use flags
Now for your own sanity you might consider stopping adding things
globally constantly, and using app-portage/flaggie to sanely manage
them per-package... Cause there's far more use flags that make sense
per-package than make sense globally. I used to manage them all
largely globally like ten
Neil Bothwick wrote:
> On Thu, 17 Feb 2022 01:42:39 -0600, Dale wrote:
>
>> P. S. Is there a tool to make the USE line in make.conf in alphabetical
>> order or something? When I add things, I try to put them in order so it
>> is easier to find them. For some reason, they are out of order, a
On Thu, 17 Feb 2022 01:42:39 -0600, Dale wrote:
> P. S. Is there a tool to make the USE line in make.conf in alphabetical
> order or something? When I add things, I try to put them in order so it
> is easier to find them. For some reason, they are out of order, a lot.
> Something at some
6 matches
Mail list logo
