From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Creating Blue-ray video discs
Date: Fri, 29 May 2020 10:12:44 -0500 [thread overview]
Message-ID: <422df50c-480b-568e-1946-8d098a71cdfb@gmail.com> (raw)
In-Reply-To: <20200529131658.kxbxoggmygqom4ll@ad-gentoo-main>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
Ashley Dixon wrote:
> On Fri, May 29, 2020 at 07:56:32AM -0500, Dale wrote:
>> Neil Bothwick wrote:
>>> On Fri, 29 May 2020 07:17:28 -0500, Dale wrote:
>>>
>>>> I'm looking into euses but didn't know it existed before now. Another
>>>> tool to keep track of. <Dale rolls his eyes> Any tips or trcks for
>>>> it??
>>> Yes, don't have make.conf as a directory, euses breaks itself in that
>>> case.
>> I have make.conf as a file still. I plan to keep it that way for the
>> moment tho. I do have package.use and friends as directories tho. Does
>> it work OK with that?
>
> Euses breaks itself in almost every case for new systems; it is in severe need
> of an upgrade. See bug [1]. It relies on $PORTDIR which has been deprecated for
> many years [2] in favour of the per-repo.conf `location` attribute [2].
>
> [1] https://bugs.gentoo.org/663706
> [2] https://wiki.gentoo.org/wiki/PORTDIR
>
Ahhhh, I'll install it but make sure my /etc/ backup is up to date.
;-) I'll likely just read the man page, see what it does etc and maybe
use it for info purposes. Sort of like euse -i does. It doesn't'
change anything, just spits out info, usually it doesn't help much but
anyway. lol
Wonder why it is not being kept up to date. Maintainer no longer
interested in it, other tools took its place???
Dale
:-) :-)
P. S. Back from being a pin cushion.
[-- Attachment #2: Type: text/html, Size: 2268 bytes --]
next prev parent reply other threads:[~2020-05-29 15:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 9:02 [gentoo-user] Creating Blue-ray video discs Dale
2020-05-29 9:33 ` Ashley Dixon
2020-05-29 9:56 ` Dale
2020-05-29 10:18 ` Ashley Dixon
2020-05-29 10:29 ` Neil Bothwick
2020-05-29 12:17 ` Dale
2020-05-29 12:50 ` Neil Bothwick
2020-05-29 12:56 ` Dale
2020-05-29 13:16 ` Ashley Dixon
2020-05-29 15:12 ` Dale [this message]
2020-05-29 16:00 ` Ashley Dixon
2020-05-29 16:48 ` Jack
2020-05-29 17:11 ` Ashley Dixon
2020-05-29 18:23 ` Neil Bothwick
2020-05-29 18:21 ` Neil Bothwick
2020-05-29 9:57 ` Joerg Schilling
2020-05-29 10:10 ` Ashley Dixon
2020-05-29 10:20 ` Joerg Schilling
2020-05-29 10:14 ` Dale
2020-05-29 13:12 ` Gerrit Kühn
2020-05-29 15:21 ` Dale
2020-05-29 20:59 ` Dale
2020-05-29 21:10 ` Ashley Dixon
2020-05-29 21:27 ` Dale
2020-05-29 10:30 ` Andrew Udvare
2020-05-29 12:38 ` Dale
2020-05-29 16:23 ` Laurence Perkins
2020-05-29 19:13 ` Dale
2020-06-02 9:41 ` Joerg Schilling
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=422df50c-480b-568e-1946-8d098a71cdfb@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