unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Simon South <simon@simonsouth.net>
Cc: "44557@debbugs.gnu.org" <44557@debbugs.gnu.org>
Subject: [bug#44557] [PATCH] gnu: Add gputils.
Date: Wed, 11 Nov 2020 11:28:32 +0000	[thread overview]
Message-ID: <BtS5wuTVQC9CpLn0jOvaYdDKhyLTz9qZyaAJd9hc9L7B0sjmE6xJyJOxJZ0-shbG5XVtteU-PHeuUuswXJ4Jz_fAuaiFMLk_OHY5d__kwGY=@elenq.tech> (raw)
In-Reply-To: <87eel0hl09.fsf@simonsouth.net>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, November 11, 2020 12:04 AM, Simon South <simon@simonsouth.net> wrote:

> Ekaitz Zarraga ekaitz@elenq.tech writes:
>
> > I packaged GPUtils...
>
> I hate to jump in here with bad news, but I didn't expect anyone would
> package gputils before I got around to sharing this:
>
> While gputils itself is free software, I suspect some of the header
> files contained in its distribution may not be, which makes the
> licensing status of the project as a whole somewhat dubious. (This is
> similar to the problem that affects SDCC[0].) I think gputils should be
> reviewed carefully before the decision is made to include it in Guix.


Hi,

Thanks for the email.
I'll forward this discussion to the GPUtils team and ask them about
the header files. There might be a way to separate them from the project.

Thanks for the detailed answer.

Best,
Ekaitz




  reply	other threads:[~2020-11-11 11:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 20:23 [bug#44557] [PATCH] gnu: Add gputils Ekaitz Zarraga
2020-11-10 23:04 ` Simon South
2020-11-11 11:28   ` Ekaitz Zarraga [this message]
2020-11-29 22:36     ` Ludovic Courtès
2021-06-14  2:44       ` Maxim Cournoyer
2021-06-14  8:08         ` Ekaitz Zarraga
2021-06-25  4:04           ` Maxim Cournoyer

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='BtS5wuTVQC9CpLn0jOvaYdDKhyLTz9qZyaAJd9hc9L7B0sjmE6xJyJOxJZ0-shbG5XVtteU-PHeuUuswXJ4Jz_fAuaiFMLk_OHY5d__kwGY=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=44557@debbugs.gnu.org \
    --cc=simon@simonsouth.net \
    /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).