genterminl Guru
Joined: 12 Feb 2005 Posts: 527 Location: Connecticut, USA
|
Posted: Thu May 30, 2019 8:17 pm Post subject: Questions on unsymlink-lib in prep for 17.1 profile migratio |
|
|
I've got several questions/issues with unsymlink-lib, but am not sure any of them are quite worth filing a bug.
(I've upgraded to version 14)
1) the output has a lot of "b'name'" where I wonder if the b' ' is supposed to be some sort of markup, such as bold. If so, it's not really clear. (That notation is also in the output of unsymlink-lib --migrate --pretend.)
2) the sections are all about "files" and "directories" but many of the items in some of the "files" list are really directories. Certainly not a show-stopper, but still confusing.
3) The section (orphan files (not owned by any package) that will be moved to b'/usr/lib/' includes avahi (a directory, not a file) but these files are NOT orphan. I just emerged avahi-0.7-r2, which explicitly puts stuff in both /usr/lib32 and /usr/lib64 (per equery f) including .so files and pkgconfig files, and I have trouble believing they belong in /usr/lib.
Am I missing something in understanding all of this?
EDIT: scratch #3. That was just sloppy reading on my part. /usr/lib/avahi is an empty dir. The actual avahi .so files are directly in /usr/lib32 and /usr/lib64. It is also not so bad to label an empty dir as a file.
EDIT2: on #1, I now see it's a Python notation for a byte literal. Am I correct to assume that notation should not escape to the output of the script? |
|