Files
gentoo/app-crypt/libsecret/metadata.xml
Pacho Ramos 4630f82113 app-crypt/libsecret: Handle crypto implementations in a more consistent way
This allow to more easily switch among implementations. Use gcrypt as default
(following upstream and most of the other distributions).

Also fix pam dependency (as pam module building also checks for libpam)

Thanks-to: Michał Górny
Closes: https://bugs.gentoo.org/943031
Signed-off-by: Pacho Ramos <pacho@gentoo.org>
2024-11-09 13:52:22 +01:00

19 lines
812 B
XML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
<maintainer type="project">
<email>gnome@gentoo.org</email>
<name>Gentoo GNOME Desktop</name>
</maintainer>
<use>
<flag name="crypt">Enable transport encryption</flag>
<flag name="gcrypt">Enable Backend library to implement transport encryption via <pkg>dev-libs/libgcrypt</pkg></flag>
<flag name="gnutls">Enable Backend library to implement transport encryption via <pkg>net-libs/gnutls</pkg></flag>
<flag name="pam">Build PAM module</flag>
<flag name="tpm">Enable Trusted Platform Module support via <pkg>app-crypt/tpm2-tss</pkg></flag>
</use>
<upstream>
<remote-id type="gnome-gitlab">GNOME/libsecret</remote-id>
</upstream>
</pkgmetadata>