Restructure repository classes and drop manual management of debian erlang source #38
Conversation
zilchms
changed the title
zilchms
changed the title
| 'RedHat': { | ||
| contain erlang::repo::yum | ||
| } | ||
| 'Debian': {} |
There was a problem hiding this comment.
How does it now work on Debian? Only use the packages from Debian.org? Is the erlang_solutions repo dead?
There was a problem hiding this comment.
Yea, it now uses the packages from debian. I am not sure what exactly is going on with the erlang_solutions repo. I know we lose a bit of configurability for debian this way, but at the very least we get the posibility to do work here again. Right now the metadata shows that we are falling behind on what OSes can be maintained. My thought process was: if the configurability is needed/wanted it can be added again later in a functional state.
There was a problem hiding this comment.
There should probably be another PR fully fixing the repo indirection problem at some point in the future. But i would have to look at the best practices for repo handling again before tackling that
| class erlang::repo::yum ( | ||
| String $ensure = $erlang::repo_ensure, | ||
| Erlang::RepoSource $source = $erlang::repo_source, | ||
| String $erlang_solutions_baseurl = "https://packages.erlang-solutions.com/rpm/centos/\$releasever/\$basearch", |
There was a problem hiding this comment.
Please update to the httpsurl datatype from stdlib
3 participants
Reduce indirection by reducing repository classes redirect levels.