From: Ming Liu <liu.ming50@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] [PATCH 2/2] podman: add alternative link for docker
Date: Mon, 11 Dec 2023 15:40:32 +0100 [thread overview]
Message-ID: <CALatG=5N+_2JoG_RWtx=TGCf8ym37iVbZiLjGbAv7V6Vk5DM5A@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4Mr8Y=h+vT2849n9d+RWGjCscDh4EL62gk53FgqCYzG=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
OK, understood, thanks for the explanation.
the best,
thank you
On Mon, Dec 11, 2023 at 9:20 AM Ming Liu <liu.ming50@gmail.com> wrote:
> >
> > Hi, Bruce:
> >
> > They are both being added in packagegroup-container? If I install that
> packagegroup from the current code base, I will get a conflict error?
>
> That packagegroup is used as a build test, versus something that is
> installed (and that distinction isn't clear, I've been meaning to
> improve it for quite some time).
>
> We can split the packagegroup to make it more useful, that's
> definitely a patch that I would accept.
>
> Bruce
>
> >
> > the best,
> > thank you
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
[-- Attachment #2: Type: text/html, Size: 1333 bytes --]
prev parent reply other threads:[~2023-12-11 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 12:09 [meta-virtualization] [PATCH 0/2] docker/podman: add alternative link for docker liu.ming50
2023-12-11 12:09 ` [meta-virtualization] [PATCH 1/2] docker: " liu.ming50
2023-12-11 12:09 ` [meta-virtualization] [PATCH 2/2] podman: " liu.ming50
2023-12-11 13:35 ` Bruce Ashfield
2023-12-11 14:20 ` Ming Liu
2023-12-11 14:30 ` Bruce Ashfield
2023-12-11 14:40 ` Ming Liu [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='CALatG=5N+_2JoG_RWtx=TGCf8ym37iVbZiLjGbAv7V6Vk5DM5A@mail.gmail.com' \
--to=liu.ming50@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).