On Wed, Aug 29, 2018 at 03:25:09PM +0200, Nicolas Mailhot wrote:
I already spent a few months of work working on the Go layer, writing Golang-to-rpm plumbing, packaging guidelines, packaging and testing hundreds of spec files. It is finally looking like something that could end up in the distribution, even though there is still a ton of work to do plumbing-side to make Go packaging in Fedora simple and convenient. And I'd like to spend more time making this plumbing a reality.
Hello,
thanks for sharing, this is awesome.
While I believe, EPEL is unsuitable for this kind of applications, we should have them in Fedora. For example prometheus is also packaged in a recent version in Debian, while Grafana is still at version 2.6, which is fairly old.
That being said, the way upstreams are adding/changing dependencies to the projects and at the same time releasing multiple major and minor releases per year makes it hard to stay on top of these projects. Having multiple releases per year and no backports makes these kind of applications trickier to handle, if not unsuitable for EPEL.
Back at the time, when I looked at packaging Grafana, it already required what felt like 100 js dependecies, where some of them were only used at build time (for copying, concatenating files etc).
Prometheus is already included in Fedora, in an old version. The package maintainer will probably accept patches and help.
I suppose this is also a test if a distribution like Fedora/Epel can still be used to deploy the kind of apps written in 2018, or if it's condemned to fade and be replaced by other approaches like containers.
I tend to disagree here. For building containers, and I'd do that from packages.
Matthias