From: Georgy Yakovlev <ya@sysdump.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New SYMLINK_LIB=no migration tool for review
Date: Sat, 19 Aug 2017 15:25:04 -0700 [thread overview]
Message-ID: <60c9f4d9-3398-1705-3dc4-9ea4539070f6@sysdump.net> (raw)
In-Reply-To: <1502573615.12010.4.camel@gentoo.org>
I've found couple of issues, or maybe not.
systemd installs to /usr/lib/systemd (or /lib/systemd since 234)
unconditionally.
I'm not sure if it's special and should be allowed to do that, but it's
the only package on the system (except gcc/$CHOST dir) that has 64-bit
libraries and binaries in lib.
Here is the list of the bugs I've found and opened, maybe you can add
them as blockers for #506276
https://bugs.gentoo.org/show_bug.cgi?id=627744
https://bugs.gentoo.org/show_bug.cgi?id=627746
https://bugs.gentoo.org/show_bug.cgi?id=628338
On 08/12/2017 02:33 PM, Michał Górny wrote:
> On śro, 2017-08-02 at 17:58 +0200, Michał Górny wrote:
>> Hi, everyone.
>>
>> I've finally gotten around to writing a new tool for migrating amd64
>> systems to SYMLINK_LIB=no layout [1]. I've put it in symlink-lib-
>> migration [2] repository along with a README. Please review it and give
>> it more testing.
>
> I've pushed two important fixes now:
>
> a. The tool now processes unowned files as well -- *.{a,la,so} are left
> in lib64 (i.e. the symlinks created by db.eclass and alikes) while
> everything else goes into lib.
>
> b. I've fixed cleanup phase to also remove top-level files
> and directories that were moved out of lib64. Also, I've fixed it not to
> complain about trying to remove non-empty directories.
>
>
>> [1]:https://bugs.gentoo.org/show_bug.cgi?id=506276
>> [2]:https://github.com/mgorny/symlink-lib-migration
>
next prev parent reply other threads:[~2017-08-19 22:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 15:58 [gentoo-dev] New SYMLINK_LIB=no migration tool for review Michał Górny
2017-08-02 17:51 ` [gentoo-dev] " Martin Vaeth
2017-08-02 18:10 ` Mike Gilbert
2017-08-02 19:07 ` Martin Vaeth
2017-08-02 19:25 ` Mike Gilbert
2017-08-03 1:02 ` Walter Dnes
2017-08-03 2:09 ` Benda Xu
2017-08-03 6:55 ` Michał Górny
2017-08-03 7:23 ` Martin Vaeth
2017-08-03 7:50 ` Martin Vaeth
2017-08-03 7:57 ` Michał Górny
2017-08-03 14:30 ` Martin Vaeth
2017-08-02 19:44 ` Michał Górny
2017-08-02 18:10 ` Holger Hoffstätte
2017-08-11 23:56 ` [gentoo-dev] " Gerogy Yakovlev
2017-08-12 7:12 ` Michał Górny
2017-08-12 21:33 ` Michał Górny
2017-08-19 22:25 ` Georgy Yakovlev [this message]
2017-08-19 22:50 ` Michał Górny
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=60c9f4d9-3398-1705-3dc4-9ea4539070f6@sysdump.net \
--to=ya@sysdump.net \
--cc=gentoo-dev@lists.gentoo.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