From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] metadata/install-qa-check.d: make the FHS paths warning easier to read
Date: Fri, 29 Mar 2024 14:49:29 -0400 [thread overview]
Message-ID: <1aa1f45a-6388-4dba-9a4f-a85fe7f9a051@gmail.com> (raw)
In-Reply-To: <ZgZJnoK6HYvNPLl1@cloudsdale.the-delta.net.eu.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 925 bytes --]
On 3/29/24 12:54 AM, Haelwenn (lanodan) Monnier wrote:
>> - strip ${D} so that people can better visualize what sort of path gets
>> installed. This has the downside of not being able to copy/paste the
>> path in order to inspect the image directory, but I think this is a
>> very small downside. Usually by the time you see this message, portage
>> has cleaned up. And if it hasn't, you can still copy/paste that from:
>>
>> Completed installing sys-cluster/legion-9999 into
>> /var/tmp/portage/sys-cluster/legion-9999/image
>
> Could maybe be confusable with installers not supporting DESTDIR though
> (although the sandbox messages look *very* different).
I'm not worried about confusing it with lack of DESTDIR support, since
lack of DESTDIR support would equal a failed src_install rather than a
FHS warning.
It's really nothing to do with the sandbox specifically.
--
Eli Schwartz
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-29 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 3:54 [gentoo-dev] [PATCH] metadata/install-qa-check.d: make the FHS paths warning easier to read Eli Schwartz
2024-03-29 4:54 ` Haelwenn (lanodan) Monnier
2024-03-29 18:49 ` Eli Schwartz [this message]
2024-03-29 14:17 ` Michał Górny
2024-03-29 18:46 ` Sam James
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=1aa1f45a-6388-4dba-9a4f-a85fe7f9a051@gmail.com \
--to=eschwartz93@gmail.com \
--cc=gentoo-dev@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