Both use flags static and static-libs have been masked since 2020-09-20 followed by this comment in package.use.mask: > # Sam James <sam@gentoo.org> (2020-09-20) > # (for Mikle Kolyada <zlogene@gentoo.org>) > # libgcrypt et al no longer support static-libs > # Need to determine whether dar's static use > # is worthwhile without it. > app-backup/dar static static-libs Recent versions of dar also have support for net-libs/librsync. The ebuild for that library doesn't support static-libs. In my opinion it is better to remove static support for dar as it reduces the amount of work needed to maintain the package and users cannot use all of the program's features with the static version anyway. What are your thoughts on this?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eabc7b7cbc5bedb05f248a3b8c0d5d66ba5cdce3 commit eabc7b7cbc5bedb05f248a3b8c0d5d66ba5cdce3 Author: Viorel Munteanu <ceamac.paragon@gmail.com> AuthorDate: 2021-03-06 14:29:27 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2021-03-12 11:29:06 +0000 app-backup/dar: remove USE static and static-libs Closes: https://bugs.gentoo.org/767454 Package-Manager: Portage-3.0.13, Repoman-3.0.2 Signed-off-by: Viorel Munteanu <ceamac.paragon@gmail.com> Signed-off-by: Joonas Niilola <juippis@gentoo.org> app-backup/dar/dar-2.6.13-r1.ebuild | 57 +++++++++++++------------------------ 1 file changed, 19 insertions(+), 38 deletions(-)
