It seems that a renaming of the ebuild is enough. Btw. I wondered why the line: use acl || myconf="${myconf} --disable-ea-support" is in the ebuild. Why are people not using acl not allowed to backup extended attributes?!? Another odd thing I noticed while upgrading from 2.2.2 to 2.2.2 is the following: ... >>> /usr/lib64/libdar.so.3.0.0 >>> /usr/lib64/libdar.so.3 -> libdar.so.3.0.0 >>> /usr/lib64/libdar.la >>> /usr/lib64/libdar.so -> libdar.so.3.0.0 ... <<< obj /usr/lib64/libdar.so.3.0.2 ... <<< sym /usr/lib64/libdar.so.3 ... It seems that the newer lib has a version number lower than the old (3.0.0 vs. 3.0.2). But that might just be a choice of the dar-people. But it doesn't seem right that it first creates a symlink libdar.so.3 -> libdar.so.3.0.0 and then later removes it again. Is this a problem with portage or...?!? Reproducible: Always Steps to Reproduce:
libdar.so.3 is not actually removed. 2.2.3 in cvs.
