From: "Andreas Oberritter" <obi@opendreambox.org>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Martin Jansa <martin.jansa@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Khem Raj <raj.khem@gmail.com>
Subject: Re: [PATCH] glibc: move ld.so.conf back to main package
Date: Mon, 18 May 2020 16:36:28 +0200 [thread overview]
Message-ID: <20200518163628.7984eb9d@opendreambox.org> (raw)
In-Reply-To: <3c2fa255-4f8b-1f4f-df79-32fd1ac72d62@prevas.dk>
On Mon, 18 May 2020 15:25:19 +0200
Rasmus Villemoes <rasmus.villemoes@prevas.dk> wrote:
> On 18/05/2020 14.29, Andreas Oberritter wrote:
> > Hello Rasmus,
> >
> > On Mon, 18 May 2020 14:12:43 +0200
> > Rasmus Villemoes <rasmus.villemoes@prevas.dk> wrote:
> >
> >> I'm certainly open to other ways of solving this. But can we agree that
> >> it is a bug that the ldconfig done at build-time does not take
> >> /etc/ld.so.conf.d/* into account, and that that should not depend on
> >> whether one has ldconfig-the-binary on target?
> >
> > have you tried installing ldconfig and adding it to ROOTFS_RO_UNNEEDED? It might be an improvement to include it in ROOTFS_RO_UNNEEDED by default.
>
> Thanks, but I don't think that will work:
>
> self._uninstall_unneeded()
>
> if self.progress_reporter:
> self.progress_reporter.next_stage()
>
> self._insert_feed_uris()
>
> self._run_ldconfig()
>
> so if the ldconfig package (including the ld.so.conf file) is just added
> to ROOTFS_RO_UNNEEDED, it will be gone by the time we get to doing the
> build-time ld.so.cache generation. And I think it has to be done in this
> order - if some of the packages removed by _uninstall_unneeded remove
> shared libraries, one doesn't want stale entries in ld.so.cache
> referring to those.
That's not ideal, but we could special-case ldconfig and uninstall it after this step.
> > Please consider use-cases where writable filesystems ship without ldconfig, but a user installs it from a package feed when needed.
>
> Do you mean I should leave /etc/ld.so.conf.d/ alone? I can do that. But
> I'd say that also in that case the current behaviour is buggy - if any
> package in the rootfs ships with an /etc/ld.so.conf.d/ entry, that entry
> should be taken into account at image build time, regardless of whether
> ldconfig is there at image build time or can usefully be added later via
> a package installer.
What I meant to say is that, in general, we can't remove files from rootfs manually if they are managed by a package manager (without causing difficulties like having to reinstall glibc in this case to restore these files when needed by someone installing ldconfig from a feed). So you'd have to leave both ld.so.conf and ld.so.conf.d alone.
Best regards,
Andreas
next prev parent reply other threads:[~2020-05-18 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 11:36 [PATCH] glibc: move ld.so.conf back to main package Rasmus Villemoes
2020-05-18 11:55 ` Martin Jansa
2020-05-18 12:12 ` Rasmus Villemoes
2020-05-18 12:23 ` [OE-core] " Phil Blundell
2020-05-18 12:29 ` Andreas Oberritter
2020-05-18 13:25 ` Rasmus Villemoes
2020-05-18 14:36 ` Andreas Oberritter [this message]
2020-06-02 9:44 ` [PATCH v2] " Rasmus Villemoes
2020-06-02 10:02 ` ✗ patchtest: failure for glibc: move ld.so.conf back to main package (rev2) Patchwork
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=20200518163628.7984eb9d@opendreambox.org \
--to=obi@opendreambox.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.