Hi, everyone. I've pushed a commented out set of 17.1 profiles for amd64 that feature the long-overdue SYMLINK_LIB=no setup. I'd really appreciate some real testing.
Warning: there is a slight risk of breaking your system, in particular multilib libraries and/or programs. To switch to the new profiles (from 13.0 or 17.0): emerge -1v app-portage/unsymlink-lib unsymlink-lib --analyze Check the output for any suspicious entries, then follow the instructions it prints. Once all is done, you can either uncomment the masked profile entries or set profile manually, e.g.: eselect profile set --force default/linux/amd64/17.1/desktop (--force is needed since the profile is commented out) If migrating from 13.0, the notes from 17.0 migration apply as well. Detailed migration guide ======================== 1. Sync and upgrade your system to avoid rebuild issues. 2. Install app-portage/unsymlink-lib. 3. Run 'unsymlink-lib --analyze' and verify the results. [at this point: do not call emerge or modify /usr manually] 4. Make a backup unless you're brave and/or the other thing. 5. Run 'unsymlink-lib --migrate'. 6. Reboot your system and see if it still boots, possibly test if important programs work. Also check if emerge starts but don't install anything. If your system is now broken, you can do 'unsymlink-lib --rollback' to return to step 3. 7. Run 'unsymlink-lib --finish'. [at this point you can start using emerge again] 8. Rebuild gcc. If you're switching from 13.0, also binutils & glibc according to that news item. 9. If you're using a multilib profile, rebuild 32-bit packages. Alternatively, if you're switching from 13.0 you can try the full-tree rebuild. 10. Once all 32-bit libraries are rebuilt, the PM should just remove /lib32 and /usr/lib32 symlinks. If it doesn't, remove them manually. -- Best regards, Michał Górny
