From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Christian Stewart <christian@aperture.us>
Cc: Raphael Pavlidis <raphael.pavlidis@gmail.com>,
Buildroot Mailing List <buildroot@buildroot.org>,
Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH 9/9 v3] package/podman: new package
Date: Sat, 8 Mar 2025 12:02:57 +0100 [thread overview]
Message-ID: <Z8wj4ZEJGRdf38Ll@landeda> (raw)
In-Reply-To: <CA+h8R2o4L0tMA1SWdp5PMxt3VjWzBj1hhQakK2805RKZ8JUMwQ@mail.gmail.com>
Christian, All,
On 2025-03-07 11:38 -0800, Christian Stewart spake thusly:
> On Fri, Mar 7, 2025, 5:40 AM Raphael Pavlidis <[1]raphael.pavlidis@gmail.com>
> wrote:
> On 3/1/25 16:05, Yann E. MORIN wrote:
> > + $(PODMAN_PKGDIR)/containers.conf \
> > + $(TARGET_DIR)/etc/containers/containers.conf
> > + $(Q)$(INSTALL) -D -m 0644 \
> > + $(PODMAN_PKGDIR)/policy.json \
> > + $(TARGET_DIR)/etc/containers/policy.json
> > + $(Q)$(INSTALL) -D -m 0644 \
> > + $(PODMAN_PKGDIR)/registries.conf \
> > + $(TARGET_DIR)/etc/containers/registries.conf
> Just for curiosity, why not installing those files under
> /usr/share/containers?
> I agree that as far as the defaults we install with the package, they should go
> to /usr/share/containers
> [2]https://github.com/containers/common/blob/main/docs/containers.conf.5.md
>
> Container engines read the /usr/share/containers/containers.conf, /etc/
> containers/containers.conf, and /etc/containers/containers.conf.d/*.conf for
> global configuration that effects all users.
See my reply to Raphael, that explains why I choose those locations for
those files.
I'll move the contrainers.conf file to its primary location, in
/usr/share/, in the next respin.
Thanks!
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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-03-08 11:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 15:05 [Buildroot] [PATCH 0/9 v3] package/podman: new package (branch yem/podman) Yann E. MORIN
2025-03-01 15:05 ` [Buildroot] [PATCH 1/9 v3] support/testing: set date in emulated machine Yann E. MORIN
2025-03-07 18:49 ` Julien Olivain
2025-03-08 11:07 ` Yann E. MORIN
2025-03-08 21:51 ` Julien Olivain
2025-03-01 15:05 ` [Buildroot] [PATCH 2/9 v3] package/shadow: install to staging for subids Yann E. MORIN
2025-03-07 13:15 ` Raphael Pavlidis
2025-03-01 15:05 ` [Buildroot] [PATCH 3/9 v3] package/conmon: depends on systemd when enabled Yann E. MORIN
2025-03-01 15:05 ` [Buildroot] [PATCH 4/9 v3] package/slirp4netns: needs TUN support in the kernel Yann E. MORIN
2025-03-07 13:20 ` Raphael Pavlidis
2025-03-01 15:05 ` [Buildroot] [PATCH 5/9 v3] package/skopeo: add target variant Yann E. MORIN
2025-03-01 15:05 ` [Buildroot] [PATCH 6/9 v3] package/cgroupfs-mount: tweak the kernel config Yann E. MORIN
2025-03-01 15:05 ` [Buildroot] [PATCH 7/9 v3] package/cgroupfs-v2-mount: new package Yann E. MORIN
2025-03-01 15:05 ` [Buildroot] [PATCH 8/9 v3] package/netavark: " Yann E. MORIN
2025-03-01 15:05 ` [Buildroot] [PATCH 9/9 v3] package/podman: " Yann E. MORIN
2025-03-07 13:40 ` Raphael Pavlidis
2025-03-07 19:38 ` Christian Stewart via buildroot
2025-03-08 11:02 ` Yann E. MORIN [this message]
2025-03-08 11:00 ` Yann E. MORIN
2025-03-09 8:30 ` Yann E. MORIN
2025-03-09 22:14 ` Yann E. MORIN
2025-03-07 18:55 ` Julien Olivain
2025-03-08 11:34 ` Yann E. MORIN
2025-03-08 22:03 ` Julien Olivain
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=Z8wj4ZEJGRdf38Ll@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=ju.o@free.fr \
--cc=raphael.pavlidis@gmail.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