summaryrefslogtreecommitdiff
path: root/gnome-base/gnome-keyring/metadata.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2018-07-14 20:58:29 +0100
committerV3n3RiX <venerix@redcorelinux.org>2018-07-14 20:58:29 +0100
commit0cf2f20608308acdf3cb922c3736446bbd8f3388 (patch)
tree07815070629c7c11000a7f51ceb8ccbccb49a809 /gnome-base/gnome-keyring/metadata.xml
parent1798c4aeca70ac8d0a243684d6a798fbc65735f8 (diff)
gentoo resync : 14.07.2018
Diffstat (limited to 'gnome-base/gnome-keyring/metadata.xml')
-rw-r--r--gnome-base/gnome-keyring/metadata.xml21
1 files changed, 0 insertions, 21 deletions
diff --git a/gnome-base/gnome-keyring/metadata.xml b/gnome-base/gnome-keyring/metadata.xml
deleted file mode 100644
index f8058de62b5a..000000000000
--- a/gnome-base/gnome-keyring/metadata.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
-<pkgmetadata>
- <maintainer type="project">
- <email>gnome@gentoo.org</email>
- <name>Gentoo GNOME Desktop</name>
- </maintainer>
- <longdescription lang="en">
- GNOME Keyring is a collection of components in GNOME that store
- secrets, passwords, keys, certificates and make them available to
- applications. It is integrated with the user's login, so that
- their secret storage can be unlocked when the user logins into their
- session. It is based around a standard called PKCS#11, which is a
- standard way for applications to manage certificates and keys on
- smart cards or secure storage.
- </longdescription>
- <use>
- <flag name="ssh-agent">Use GNOME Keyring to unlock SSH keys.
- Recommended unless you are using ECDSA or Ed25519 keys.</flag>
- </use>
-</pkgmetadata>