From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/8] core/show-info: report install types for virtual packages too
Date: Sat, 11 Apr 2020 11:49:16 +0200 [thread overview]
Message-ID: <20200411094916.GL29898@scaer> (raw)
In-Reply-To: <20200411104104.6a01dba7@windsurf.home>
Thomas, All,
On 2020-04-11 10:41 +0200, Thomas Petazzoni spake thusly:
> On Sat, 11 Apr 2020 10:12:28 +0200
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
>
> > Although virtual packages do not usually install anything, they do
> > participate in the dependency chain, and they also transition smoothly
> > from 'not handled yet' all the way down to 'all set'.
> I'm having a hard time to understand what you mean by:
> they also transition smoothly from 'not handled yet' all the way down
> to 'all set'.
> Could you clarify ?
I mean that virtual package, like all other packages, have a sequence of
a few steps that transition the virtual package from "not handled yet"
to "installed and dependencies can start", i.e. virtual packages are:
1. configured
2. built
3. installed in staging (optional)
4. installed in target (optional)
5. isntalled in images (optional)
Virtual packages are just packages in this respect. It's just that their
deoendencies are treated specially.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-04-11 9:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 8:12 [Buildroot] [PATCH 0/8] core/show-info: export extra information about the package build (branch yem/show-info-extras) Yann E. MORIN
2020-04-11 8:12 ` [Buildroot] [PATCH 1/8] core/show-info: do not show install types for host packages Yann E. MORIN
2020-04-25 12:57 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 2/8] infra/pkg-generic: don't set INSTALL_{TARGET, STAGING, IMAGES} for host Yann E. MORIN
2020-04-25 12:57 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 3/8] core/show-info: report install types for virtual packages too Yann E. MORIN
2020-04-11 8:41 ` Thomas Petazzoni
2020-04-11 9:49 ` Yann E. MORIN [this message]
2020-04-25 13:07 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 4/8] core/show-info: report the package build directory Yann E. MORIN
2020-04-25 13:08 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 5/8] core/show-info: report whether a package is overriden Yann E. MORIN
2020-04-11 8:36 ` Thomas Petazzoni
2020-04-11 9:44 ` Yann E. MORIN
2020-04-11 12:42 ` Thomas Petazzoni
2020-04-11 13:22 ` Yann E. MORIN
2020-04-11 14:14 ` Thomas Petazzoni
2020-04-11 17:41 ` Yann E. MORIN
2020-04-11 8:12 ` [Buildroot] [PATCH 6/8] core/show-info: report package stamp files Yann E. MORIN
2020-04-11 8:38 ` Thomas Petazzoni
2020-04-11 8:12 ` [Buildroot] [PATCH 7/8] core/show-info: report the ordered list of build steps Yann E. MORIN
2020-04-11 8:39 ` Thomas Petazzoni
2020-04-11 13:41 ` Philippe Proulx
2020-04-11 14:19 ` Thomas Petazzoni
2020-04-11 15:06 ` Philippe Proulx
2020-04-11 15:27 ` Thomas Petazzoni
2020-04-11 18:20 ` Yann E. MORIN
2020-04-11 18:12 ` Yann E. MORIN
2020-04-11 18:02 ` Yann E. MORIN
2020-04-11 8:12 ` [Buildroot] [PATCH 8/8] core/show-info: report image name of filesystems Yann E. MORIN
2020-04-25 13:12 ` Thomas Petazzoni
2020-04-25 13:32 ` Yann E. MORIN
2021-07-27 20:08 ` Arnout Vandecappelle
2020-04-25 13:13 ` [Buildroot] [PATCH 0/8] core/show-info: export extra information about the package build (branch yem/show-info-extras) Thomas Petazzoni
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=20200411094916.GL29898@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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