From: "Haelwenn (lanodan) Monnier" <contact@hacktivis.me>
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 05:54:54 +0100 [thread overview]
Message-ID: <ZgZJnoK6HYvNPLl1@cloudsdale.the-delta.net.eu.org> (raw)
In-Reply-To: <20240329035439.11381-1-eschwartz93@gmail.com>
[2024-03-28 23:54:35-0400] Eli Schwartz:
> * QA Notice: The ebuild is installing to one or more unexpected paths:
> *
> * /var/tmp/portage/sys-cluster/legion-9999/image/usr/bin/legion_prof_files
> * /var/tmp/portage/sys-cluster/legion-9999/image/usr/bin/serializer_examples
> *
> * Please fix the ebuild to use correct FHS/Gentoo policy paths.
>
>This message is hard to understand. Is it saying that the resulting
>package contains files prefixed with ${D} which would be immensely
>broken? Is it saying that these paths are *directories* and the FHS does
>not approve of directories in /usr/bin/*/?
>
>In fact, it's the latter. Fix this in two ways:
>
>- clarify that it's an unexpected directory, not just some kind of path
I guess it would also make sense to have a trailing slash as extra
indication of it being a directory like `ls -F` does.
>- 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).
next prev parent reply other threads:[~2024-03-29 4:55 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 [this message]
2024-03-29 18:49 ` Eli Schwartz
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=ZgZJnoK6HYvNPLl1@cloudsdale.the-delta.net.eu.org \
--to=contact@hacktivis.me \
--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