On Thu, Nov 16, 2023 at 10:37 AM John Reiser <jreiser@xxxxxxxxxxxx> wrote: > > > Is it safe to assume that this symbolic link [/lib64 -> usr/lib64] > > exists in all chroots? > > This includes the initial ramdisk, recovery environments, and chroots > > for confining services. > > It is unsafe unless prominently documented in the places that are likely > to be seen by affected developers, now and especially *in the future*: > man glibc, info glibc, man chroot, info chroot, man docker, man virtmgr, etc. > Such a change has aspects of being a System-Wide Change for Fedora. > For instance, I have a recipe for an "embedded" Docker > that will have to add the symlink. Unless you are somehow excluding the "filesystem" package when building a Fedora rootfs (which is a required package, so it's quite hard to avoid), you are not going to be missing that symlink. -- 真実はいつも一つ！/ Always, there's only one truth! -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
