On Wed, 16 Mar 2016, Dennis Gilmore wrote:
On Wednesday, March 16, 2016 9:39:33 PM CDT Kamil Dudka wrote:
> On Wednesday, March 16, 2016 16:19:23 Bill Nottingham wrote:
> > Kamil Dudka (kdudka(a)redhat.com) said:
> > > Are you reading it from the specfile?
> > >
> > > It is just an implementation detail of the packaging (the
> > > RemovePathPostfixes feature of rpm). The string you mentioned neither
> > > appears in the SONAME, nor in any file installed by the RPMs in
> > > question.
> >
> > ... which means if the SONAME is the same, you either are dealing with
>
> > Conflicts:
> Exactly. libcurl conflicts with libcurl-minimal, which means that exactly
> one of them will be installed on any Fedora system at a time. On a regular
> system (server, desktop, etc.) it will always be libcurl.
>
> On the other hand, if you need to create a minimal installation of Fedora
> (e.g. a base image for Docker), you will pick libcurl-minimal instead of
> libcurl, to make the set of installed packages really minimal.
>
> > , or relying on the behavior of ldconfig to figure out which
> > library you happen to get at a particular time.
>
> ldconfig will always pick /usr/lib64/libcurl.so.4 because there can be only
> one file with that name installed at a time.
And how do you transition when you need to add the full featured version?
Just a
note on top of what Dennis asked: if curl minimal would lack
XML-RPC and GSSAPI support, FreeIPA client enrollment will be broken
completely. There are many uses of that within kickstart or cloud-init
files.
--
/ Alexander Bokovoy