# Copyright 1999-2022 Gentoo Authors # Distributed under the terms of the GNU General Public License v2 EAPI=7 inherit readme.gentoo-r1 systemd toolchain-funcs COMMIT="591a7834dc9f1dff3d336d769a6561138a5befe7" DESCRIPTION="An OpenPGP keyserver which is decentralized with highly reliable synchronization" HOMEPAGE="https://github.com/SKS-Keyserver/sks-keyserver" SRC_URI="https://github.com/SKS-Keyserver/sks-keyserver/archive/${COMMIT}.tar.gz -> ${P}.tar.gz" S="${WORKDIR}/${PN}-keyserver-${COMMIT}" LICENSE="GPL-2" SLOT="0" KEYWORDS="amd64 ~x86" IUSE="optimize test" RESTRICT="!test? ( test )" DOC_CONTENTS="To get sks running, first build the database, start the database, import atleast one key, then run a cleandb. See the sks man page for more information Typical DB_CONFIG file and sksconf has been installed in /var/lib/sks and can be used as templates by renaming to remove the .typical extension. The DB_CONFIG file has to be in place before doing the database build, or the BDB environment has to be manually cleared from both KDB and PTree. The same applies if you are upgrading to this version with an existing KDB/Ptree, using another version of BDB than 4.8; you need to clear the environment using e.g. db4.6_recover -h . and db4.6_checkpoint -1h . in both KDB and PTree Additionally a sample web interface has been installed as web.typical in /var/lib/sks that can be used by renaming it to web Important: It is strongly recommended to set up SKS behind a reverse proxy. Instructions on properly configuring SKS can be found at https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering" RDEPEND=" acct-user/sks acct-group/sks