From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 2/2] package/refpolicy/Config.in: depend on merged usr when selecting upstream
Date: Mon, 9 Oct 2023 17:14:08 +0200 [thread overview]
Message-ID: <20231009151408.GE14234@scaer> (raw)
In-Reply-To: <20231009151200.GD14234@scaer>
Adam, All,
Sorry, O was too fast at sending my reply...
On 2023-10-09 17:12 +0200, Yann E. MORIN spake thusly:
> On 2023-10-09 10:06 +0200, Adam Duskett spake thusly:
> > Refpolicy contexts expect a merged /usr file system. In fact, there
> > are no references to /bin, /sbin, /lib, or /lib64 at all
Is this due to the version bump?
If yes, then it should be part of the same patch. If not (i.e. that was
already the case before the new version), then it should come before the
version bump (so tht it can be more easily backported to maintenance
branches)
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
prev parent reply other threads:[~2023-10-09 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 8:06 [Buildroot] [PATCH v3 1/2] package/refpolicy: bump version to 2.20231002 Adam Duskett
2023-10-09 8:06 ` [Buildroot] [PATCH v3 2/2] package/refpolicy/Config.in: depend on merged usr when selecting upstream Adam Duskett
2023-10-09 15:12 ` Yann E. MORIN
2023-10-09 15:14 ` Yann E. MORIN [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=20231009151408.GE14234@scaer \
--to=yann.morin.1998@free.fr \
--cc=adam.duskett@amarulasolutions.com \
--cc=buildroot@buildroot.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