public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH 4/4] Add --disable-major-minor-libraries configure option
Date: Wed, 9 Jun 2021 17:28:52 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2106091724300.360093@digraph.polyomino.org.uk> (raw)
In-Reply-To: <878s3j3qxy.fsf@oldenburg.str.redhat.com>

On Wed, 9 Jun 2021, Florian Weimer via Libc-alpha wrote:

> * Joseph Myers:
> 
> > This needs a NEWS entry.
> 
> What about this?
> 
> * glibc can now be configured with the --disable-major-minor-libraries
>   option.  In this case, the various shared objects that are part of
>   glibc will be installed under their ABI sonames (such as libc.so.6)
>   rather than version-specific file names (such as libc-2.34.so).  As
>   before, by default, glibc installs them as version-specific file
>   names, with the ABI sonames added as symbolic links.  The
>   --disable-major-minor-libraries option enables safer downgrades with
>   package managers which delete removed files very late, after invoking
>   ldconfig.

That seems reasonable (if we have this option at all).

> Indepdently of the implementation of the patch, do you think this is
> something that needs to be configurable, or can we remove versioned file
> names altogether?

I don't know why we have the versioned file names, but my guess would be 
it was intended to help with downgrades after a non-package-manager 
installation directly into the root filesystem went wrong (someone could 
try to use sln to recover by linking back to the older-version files).

I don't think we should expect installation directly into the root 
filesystem by "make install" to work reliably anyway, let alone provide a 
downgrade mechanism, so I don't see the need to support versioned file 
names any more.

-- 
Joseph S. Myers
joseph@codesourcery.com

      reply	other threads:[~2021-06-09 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 11:15 [PATCH 0/4] " Florian Weimer
2021-06-09 11:16 ` [PATCH 1/4] nptl_db: Install libthread_db under a regular implementation name Florian Weimer
2021-06-09 11:16 ` [PATCH 2/4] Makerules: Remove lib-version, $(subdir-version) Florian Weimer
2021-06-09 11:16 ` [PATCH 3/4] elf: Generalize name-based DSO recognition in ldconfig Florian Weimer
2021-06-09 11:16 ` [PATCH 4/4] Add --disable-major-minor-libraries configure option Florian Weimer
2021-06-09 16:03   ` Joseph Myers
2021-06-09 17:09     ` Florian Weimer
2021-06-09 17:28       ` Joseph Myers [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=alpine.DEB.2.22.394.2106091724300.360093@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).