unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: 34613@debbugs.gnu.org
Subject: [bug#34613] Acknowledgement ([PATCH] gnu: Add prometheus.)
Date: Fri, 22 Feb 2019 13:21:35 +0100	[thread overview]
Message-ID: <CAE4v=phFeyXQOY59QbPkZKCRLsNFc5EhDJ_UCOzjsoSD3yT36A@mail.gmail.com> (raw)
In-Reply-To: <handler.34613.B.155083599830524.ack@debbugs.gnu.org>

Hello,

I have packaged prometheus.

There are some problems with it however:

The tarball has a vendor directory, containing sources of third party
go stuff. How do we deal with that?
(Should we package the stuff there, and link the sources into the tree?)

I have noticed a few possible problems:
https://github.com/prometheus/prometheus/blob/master/vendor/github.com/influxdata/influxdb/LICENSE_OF_DEPENDENCIES.md
indicates that glyphicons is possibly non-free, needs further
investigation.
https://github.com/prometheus/prometheus/tree/master/vendor/github.com/shurcooL/httpfs
does not copy the original LICENSE file from upstream, it is MIT
licensed. Should report a bug against prometheus.

Other preliminary license checks does not show further issues.

I would like to know if anyone could help me get this package into
shape, and point me towards a way to use inputs instead of linking the
source into the build tree. It would be nice, if we didn't have to
build these stuffs twice.
I am willing to do the work, but I need some pointer, as I am not into go.

Unbundling would also help to get a more exact license line.

Any help welcome.

Additionally:
1. this package misses a service,
2. only prometheus is built, the repository contains some other tools,
like promtool, those are not provided.

Best regards,
g_bor

  parent reply	other threads:[~2019-02-22 12:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 11:45 [bug#34613] [PATCH] gnu: Add prometheus Gábor Boskovits
     [not found] ` <handler.34613.B.155083599830524.ack@debbugs.gnu.org>
2019-02-22 12:21   ` Gábor Boskovits [this message]
2019-03-11 22:19     ` [bug#34613] Acknowledgement ([PATCH] gnu: Add prometheus.) Ludovic Courtès
2019-03-12  7:03       ` Pierre Neidhardt
2019-03-12 19:31         ` Leo Famulari
2019-03-12 21:24         ` Gábor Boskovits
2019-03-12 21:29       ` Gábor Boskovits
2019-03-13 10:06         ` Ludovic Courtès
2019-03-13 12:33           ` Gábor Boskovits
2019-03-18  8:31             ` Ludovic Courtès
2022-04-07 12:29 ` [bug#34613] [PATCH] gnu: Add prometheus zimoun
2022-10-08 14:42   ` zimoun
2022-10-18 16:18     ` bug#34613: " zimoun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE4v=phFeyXQOY59QbPkZKCRLsNFc5EhDJ_UCOzjsoSD3yT36A@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=34613@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).