Copying installed bundle can cause existing preserved libs problem
I have gitlabhq-13.7.4 installed. Then upgraded icu, but don't rebuild gitlabhq again (which @preserved-rebuild want to do). Instead I installed gitlabhq-13.8.0. Normally that will use new icu, but since new ebuild copy installed bundle which was build with old icu that cause now @preserved-rebuild to think that it must rebuild gitlabhq again. I emerge gitlabhq again did, but that doesn't fix the problem, because it again copy bunle. Now I have:
!!! existing preserved libs:
>>> package: dev-libs/icu-68.2
* - /usr/lib64/libicudata.so.67
* - /usr/lib64/libicudata.so.67.1
* - /usr/lib64/libicui18n.so.67
* - /usr/lib64/libicui18n.so.67.1
* used by /opt/gitlab/gitlabhq-13.8.0/vendor/bundle/ruby/2.7.0/extensions/x86_64-linux/2.7.0/charlock_holmes-0.7.7/charlock_holmes/charlock_holmes.so (www-apps/gitlabhq-13.8.0)
* used by /opt/gitlab/gitlabhq-13.8.0/vendor/bundle/ruby/2.7.0/gems/charlock_holmes-0.7.7/ext/charlock_holmes/charlock_holmes.so (www-apps/gitlabhq-13.8.0)
* used by /opt/gitlab/gitlabhq-13.8.0/vendor/bundle/ruby/2.7.0/gems/charlock_holmes-0.7.7/lib/charlock_holmes/charlock_holmes.so (www-apps/gitlabhq-13.8.0)
* - /usr/lib64/libicuuc.so.67
* - /usr/lib64/libicuuc.so.67.1
* used by /opt/gitlab/gitlabhq-13.8.0/vendor/bundle/ruby/2.7.0/extensions/x86_64-linux/2.7.0/charlock_holmes-0.7.7/charlock_holmes/charlock_holmes.so (www-apps/gitlabhq-13.8.0)
* used by /opt/gitlab/gitlabhq-13.8.0/vendor/bundle/ruby/2.7.0/gems/charlock_holmes-0.7.7/ext/charlock_holmes/charlock_holmes.so (www-apps/gitlabhq-13.8.0)
* used by /opt/gitlab/gitlabhq-13.8.0/vendor/bundle/ruby/2.7.0/gems/charlock_holmes-0.7.7/lib/charlock_holmes/charlock_holmes.so (www-apps/gitlabhq-13.8.0)
Use emerge @preserved-rebuild to rebuild packages using these libraries
May be there must be some warning or message if something like that happened so user know how to rebuild these bundle mundle things. Or flag in ebuild to use or not "fast" install.