public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	<docs@lists.yoctoproject.org>
Subject: Re: [docs] [yocto-docs][PATCH v3] ref-manual: classes: fix bin_package description
Date: Wed, 27 Nov 2024 16:24:06 +0100	[thread overview]
Message-ID: <D5X2CJUWAUXK.1WD6S6Z12GTS6@bootlin.com> (raw)
In-Reply-To: <0cf6ce20-4e81-4f80-8065-01558fffa52f@cherry.de>

Hi Quentin,

On Wed Nov 27, 2024 at 3:15 PM CET, Quentin Schulz wrote:
[...]
>>>> +``${S}/usr/lib/<library>.so`` to be installed in :term:`D` correctly.
>>>> +
>>>
>>> It'd be nice to encourage people to use versioned shared libraries even
>>> for binary packages but not sure how to word this here.
>> 
>> Replace by ``${S}/usr/lib/<library>.<version>.so``? and implicitly encourage it.
>> Not sure this is the place to give written advice on that.
>> 
>
> It's actually ``${S}/usr/lib/<library>.so.<version>`` :) But would work 

Oops, right thanks :)

> for me. Though considering FILES:${PN} = "/" once inheriting this class, 
> whether versioned or not doesn't matter to the packaging step (unlike 
> the default values, where .so goes to -dev package).
>
>>>> +.. note::
>>>>    
>>>> -      SRC_URI = "git://example.com/downloads/somepackage.rpm;branch=main;subpath=${BP}"
>>>> +   The extraction of the package passed in :term:`SRC_URI` is not handled by the
>>>> +   :ref:`ref-classes-bin-package` class, and is done by the appropriate
>
> s/, and is done/but rather/ ?

+1

>>>> +   :ref:`fetcher <bitbake-user-manual/bitbake-user-manual-fetching:fetchers>`
>>>> +   depending on the nature of the package.
>>>
>>> What do you mean by "depending on the nature of the package"?
>> 
>> I meant the type, like RPM, tarball, deb… I can replace by "type", and add a
>> "(RPM, Deb, tarball, …)" in parenthesis afterwards.
>> 
>
> I would simply remove "depending on the nature of the package", that's 
> already implied? Ah, or we can say depending on the file extension which 
> I believe is how the fetcher is actually figuring out how to extract them?

Sure! File extension's fine to me.

Thanks,
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2024-11-27 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 11:36 [yocto-docs][PATCH v3] ref-manual: classes: fix bin_package description Antonin Godard
2024-11-27 12:36 ` Quentin Schulz
2024-11-27 13:37   ` [docs] " Antonin Godard
2024-11-27 14:15     ` Quentin Schulz
2024-11-27 15:24       ` Antonin Godard [this message]

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=D5X2CJUWAUXK.1WD6S6Z12GTS6@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.petazzoni@bootlin.com \
    /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