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>,
	<docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2] overview-manual: concepts: add details on package splitting
Date: Tue, 22 Oct 2024 16:02:48 +0200	[thread overview]
Message-ID: <D52E2OT8FW95.1HWYMAWG3NWBQ@bootlin.com> (raw)
In-Reply-To: <b924ebb2-61f2-4d6a-8d57-b3807672ab61@cherry.de>

On Tue Oct 22, 2024 at 3:47 PM CEST, Quentin Schulz wrote:
>> -The :term:`FILES` variable defines the
>> -files that go into each package in
>> -:term:`PACKAGES`. If you want
>> -details on how this is accomplished, you can look at
>> -:yocto_git:`package.bbclass </poky/tree/meta/classes-global/package.bbclass>`.
>> +Packages for a recipe are listed in the :term:`PACKAGES` variable. The
>> +:oe_git:`bitbake.conf </openembedded-core/tree/meta/conf/bitbake.conf>`
>> +configuration file defines the following default list of packages::
>> +
>> +  PACKAGES = "${PN}-src ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale ${PACKAGE_BEFORE_PN} ${PN}"
>> +
>> +Each of these packages contain a default list of files defined with the
>
> s/contain/contains/ since it's "each" so singular.

Thanks... I know it's the correct way to write it but my brain can't stop from
finding it weird that way :)

>> +:term:`FILES` variable. For example, the package ``${PN}-dev`` represents files
>> +useful to the development of applications depending on ``${PN}``. The default
>> +list of files for ``${PN}-dev``, also defined in :oe_git:`bitbake.conf
>> +</openembedded-core/tree/meta/conf/bitbake.conf>`, is defined as follows::
>> +
>> +  FILES:${PN}-dev = "${includedir} ${FILES_SOLIBSDEV} ${libdir}/*.la \
>> +                  ${libdir}/*.o ${libdir}/pkgconfig ${datadir}/pkgconfig \
>> +                  ${datadir}/aclocal ${base_libdir}/*.o \
>> +                  ${libdir}/${BPN}/*.la ${base_libdir}/*.la \
>> +                  ${libdir}/cmake ${datadir}/cmake"
>> +
>> +The paths in this list must be *absolute* paths from the point of view of the
>> +root filesystem on the target, and must *not* make references to the variable
>
> I would use the singular here for reference as a path can only make a
> reference to another path and not multiple ones.

+1

>> +:term:`D` or any :term:`WORKDIR` related variable. A correct example would be::
>> +
>> +  ${sysconfdir}/foo.conf
>> +
>> +.. note::
>> +
>> +   The list of files for a package is defined using the override syntax by
>> +   separating :term:`FILES` and the package name by a semi-colon (``:``).
>> +
>> +.. note::
>> +
>> +  To find out which package installs a file, the ``oe-pkgdata-util``
>> +  command-line utility can be used::
>> +
>> +    $ oe-pkgdata-util find-path '/etc/fstab'
>> +    base-files: /etc/fstab
>> +> +  For more information on the ``oe-pkgdata-util`` utility, see the
> section
>> +  :ref:`dev-manual/debugging:Viewing Package Information with
>> +  \`\`oe-pkgdata-util\`\`` of the Yocto Project Development Tasks Manual.
>> +
>
> I would move the second note to after the paragraph in which the "a file
> is only in one package" statement below, but that's personal taste at
> that point :)

Right, I agree.

> Looks good to me.
>
> With the contain/contains typo fixed:
>
> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
>
> Cheers,
> Quentin

Thanks Quentin.

Cheers,
Antonin

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


      reply	other threads:[~2024-10-22 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 13:38 [PATCH v2] overview-manual: concepts: add details on package splitting Antonin Godard
2024-10-22 13:47 ` Quentin Schulz
2024-10-22 14:02   ` 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=D52E2OT8FW95.1HWYMAWG3NWBQ@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