all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 34613@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: [bug#34613] Acknowledgement ([PATCH] gnu: Add prometheus.)
Date: Mon, 11 Mar 2019 23:19:59 +0100	[thread overview]
Message-ID: <87k1h5rr3k.fsf@gnu.org> (raw)
In-Reply-To: <CAE4v=phFeyXQOY59QbPkZKCRLsNFc5EhDJ_UCOzjsoSD3yT36A@mail.gmail.com> ("Gábor Boskovits"'s message of "Fri, 22 Feb 2019 13:21:35 +0100")

Hi Gábor!

Gábor Boskovits <boskovits@gmail.com> skribis:

> 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 think we generally do that yes.  Pierre, Leo?

> 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.

Glyphicons appears to be non-free, indeed.  Could you check what Debian
does, for instance?  It may be that we can just remove or replace it
with something else.

> 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.

OK.

> 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.

I’m ignorant about Go, but hopefully Pierre, Leo, or someone else with
experience with Go packaging can provide some guidance!

It’d be great to have Prometheus!

Thank you
Ludo’.

  reply	other threads:[~2019-03-11 22:21 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   ` [bug#34613] Acknowledgement ([PATCH] gnu: Add prometheus.) Gábor Boskovits
2019-03-11 22:19     ` Ludovic Courtès [this message]
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

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

  git send-email \
    --in-reply-to=87k1h5rr3k.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=34613@debbugs.gnu.org \
    --cc=boskovits@gmail.com \
    --cc=mail@ambrevar.xyz \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.