added trust-anchors repo #9
Conversation
There was a problem hiding this comment.
The PR is still a draft.
It's possible to use a remote sources instead of the manually defined one:
https://repository.egi.eu/sw/production/cas/1/current/repo-files/egi-trustanchors.repo
But in fact I'm not a big fan of the repo creation like this, I like when it's possible to install a repo via a package. Usually, with UMD the CA repo was installed via the umd-release package, like by https://repository.egi.eu/sw/production/umd/5/centos7/x86_64/base/umd-release-5.0.0-1.el7.centos.noarch.rpm
❯ rpm2cpio umd-release-5.0.0-1.el7.centos.noarch.rpm | cpio -idmv
./etc/umd-release
./etc/yum.repos.d/EGI-trustanchors.repo
./etc/yum.repos.d/UMD-5-base.repo
./etc/yum.repos.d/UMD-5-testing.repo
./etc/yum.repos.d/UMD-5-untested.repo
./etc/yum.repos.d/UMD-5-updates.repo
./usr/share/doc/umd-release-5.0.0
./usr/share/doc/umd-release-5.0.0/LICENSE-2.0
28 blocksWe should take into account that all this is hopefully just a very temporary solution.
I would prefer having only the dependencies on the packages ca-policy-egi-core, ca-policy-egi-lg and fetch-crl, if/as needed.
And let the users know they need to configure the repositories themselves, either via the future umd-release, or by CURL-ing what they need. (as they have to have a repo providing the dependencies, be them htcondor or the CA).
This can be added to the doc/README as needed
Summary
Related issue :