From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] dev-manual: some minor cleanups to "Pre-Built Libraries"
Date: Tue, 24 Jun 2025 10:35:45 +0200 [thread overview]
Message-ID: <DAUMJR1JIO0X.I9IFP24VIJ4Y@bootlin.com> (raw)
In-Reply-To: <e35decf1-32df-59f8-9456-335ecdec531b@crashcourse.ca>
On Tue Jun 24, 2025 at 10:31 AM CEST, Robert P. J. Day wrote:
> On Tue, 24 Jun 2025, Antonin Godard via lists.yoctoproject.org wrote:
>
>> On Sun Jun 22, 2025 at 12:59 PM CEST, Robert P. J. Day wrote:
>> >
>> > * Add note about new URL for FHS 3.0.
>> > * Add wildcard for "INHIBIT_" variable.
>> > * Fix font for ${PN}.
>> >
>> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>> >
>> > ---
>> >
>> > diff --git a/documentation/dev-manual/prebuilt-libraries.rst b/documentation/dev-manual/prebuilt-libraries.rst
>> > index a05f39ca1..077184657 100644
>> > --- a/documentation/dev-manual/prebuilt-libraries.rst
>> > +++ b/documentation/dev-manual/prebuilt-libraries.rst
>> > @@ -22,6 +22,13 @@ To summarize, a versioned library must meet two conditions:
>> > This section shows how to deal with both versioned and unversioned
>> > pre-built libraries.
>> >
>> > +.. note::
>> > +
>> > + In the shared library article referenced above, the link to the current
>> > + version of the Filesystem Hierarchy Standard (FHS) is out of date;
>> > + the current FHS 3.0 release can be found
>> > + `here <https://refspecs.linuxfoundation.org/FHS_3.0/index.html>`__.
>>
>> Not sure adding a note to say a link is outdated is the good approach.
>> Instead update the link above?
>
> i'm not sure that's the right way to do it. that old article is
> quite a decent explanation of library versioning; if we now link
> directly to the FHS spec from the yocto docs and bypass that article,
> we lose a lot of good intro-level explanation.
>
> thoughts?
I see. Then as Quentin suggested I think it's reasonable to link to
https://refspecs.linuxfoundation.org/fhs.shtml instead of the 3.0 version, and
say:
"""
the latest release can be found `here
<https://refspecs.linuxfoundation.org/fhs.shtml>`__.
"""
Thanks,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-06-24 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 10:59 [PATCH] dev-manual: some minor cleanups to "Pre-Built Libraries" Robert P. J. Day
2025-06-23 14:16 ` [docs] " Quentin Schulz
2025-06-23 15:19 ` Robert P. J. Day
2025-06-24 7:50 ` Antonin Godard
2025-06-24 8:19 ` Robert P. J. Day
2025-06-24 8:28 ` Antonin Godard
2025-06-24 8:31 ` Robert P. J. Day
2025-06-24 8:35 ` Antonin Godard [this message]
2025-06-24 8:43 ` Robert P. J. Day
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=DAUMJR1JIO0X.I9IFP24VIJ4Y@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.