Re: About upgrading to glibc-2.40

"Pierre Labastie" ([email protected] via lfs-support Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.support
Message-ID <[email protected]>
Le dimanche 05 janvier 2025 à 10:18 +0100, tjoen a écrit :
> www.linuxfromscratch.org/lfs/view/stable-systemd/chapter08/glibc.html
> Running LFS for about 15 years. With RPM.
> Failed twice upgrading glibc with RPM
> I came with a new idea:
> 
> 1. add in %pre
>     rpm -e --justdb --nodeps glibc
> 2. add in %install
>     cd $RPM_BUILD_ROOT/
>     mkdir usr/lib64/glibc
>     mv lib64/*.so.* usr/lib64/glibc/
> 3. add in %post
>     install /usr/lib64/glibc/*.so.* /lib64/
> 
> (/lib64 is a symlink to /usr/lib64)
> 
> Would that work?

I don't know much of rpm, especially when in the build/install process
%pre, %install, and %post are run.

So I assume %pre is the configure step, %install is a DESTDIR install,
and %post is run after the package has been installed onto the system.

If so, it should work, although I am not sure why you need to rpm -e
the db (maybe to prevent erasing existing files when installing the
package onto the system?).

But the problem is this: old files wouldn't be removed when installing
the new glibc. This is not a problem if there is a one to one
correspondance between old and new files. But often some filenames are
changed or some files are moved from version to version... Well, the
procedure proposed in the book does not care about changed files
either!

Pierre

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.