On Mon, 8 Apr 2024 at 06:51, Enrico Scholz <enrico.sch...@sigma-chemnitz.de> wrote: > > "Dan McGregor" <danismostlik...@gmail.com> writes: > > > Add support for the nfsv4 user ID mapping daemon, configured with > > a sensible default, and add a packageconfig for Kerberos support. > > > > This is reasonably tested in production in our environment, but only > > systemd support. There'll be some more work to do to get GSSAPI and > > NFS idmapd support integreated into that. > > Just for interest: how do you solve GSSAPI? I made it work for me, put > it requires ugly changes (e.g. see [1]) > > There is an early dependency loop in libtirpc -> python -> kerberos -> > openssl -> python. I solved it by
That's interesting; my setup didn't enable openssl for krb5, so I avoided the dependency loop. But you're right, looks like a bit more work'll be needed to make that loop go away. > > - creating a throw-away krb5-initial package [2]; installs libraries in > /opt/krb5 and is used only at a few places. > > - splitting libtirpc; this required to touch only a few other packages > some weeks/months ago. But now, [file-rdeps] error is triggered and > every > > Both is ugly.... > Yep they are. I think one potential way to deal with this is have a local build of tirpc for nfs-utils. Or splitting tirpc up into two related recipes that somehow don't stomp on each other, like a tirpc-initial and tirpc like we do with libgcc. > > > Enrico > > Footnotes: > [1] > https://gitlab.com/ensc-groups/bpi-router/de.ensc.bpi-router/-/tree/nanbield-next/meta-core/recipes-extended/libtirpc?ref_type=heads > > (there exists a newer version but I do have not pushed it yet...) > > [2] > https://gitlab.com/ensc-groups/bpi-router/de.ensc.bpi-router/-/tree/nanbield-next/meta-core/recipes-connectivity/krb5?ref_type=heads >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#198016): https://lists.openembedded.org/g/openembedded-core/message/198016 Mute This Topic: https://lists.openembedded.org/mt/105279025/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
