unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add mesa-demos.
Date: Sat, 14 Mar 2015 15:58:02 +0100	[thread overview]
Message-ID: <87a8zf7hj9.fsf@taylan.uni.cx> (raw)
In-Reply-To: <87oanvy8je.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 14 Mar 2015 15:10:13 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
>
>> From 051341d49fae36579ce318ab0b9c245ed084cdae Mon Sep 17 00:00:00 2001
>> From: =?UTF-8?q?Taylan=20Ulrich=20Bay=C4=B1rl=C4=B1/Kammer?=
>>  <taylanbayirli@gmail.com>
>> Date: Fri, 13 Mar 2015 15:57:51 +0100
>> Subject: [PATCH 2/3] gnu: msea: Propagate input libxshmfence.
>>
>> * gnu/packages/gl.scm (mesa): Propagate input libxshmfence.
>
> [...]
>
>> +        ("libxshmfence" ,libxshmfence)
>
> Please add a margin comment explaining the reason.

It's in the "Requires.private" field of the gl.pc pkg-config file.  The
same seems to be the case for other packages in the propagated-inputs
list.  Should it be explained for all of them?..

>> From e1f288dee780b374fc2162eb39d96a50d64964c1 Mon Sep 17 00:00:00 2001
>> From: =?UTF-8?q?Taylan=20Ulrich=20Bay=C4=B1rl=C4=B1/Kammer?=
>>  <taylanbayirli@gmail.com>
>> Date: Fri, 13 Mar 2015 15:58:25 +0100
>> Subject: [PATCH 3/3] gnu: Add mesa-demos.
>>
>> * gnu/packages/gl.scm (mesa-demos): New variable.
>
> [...]
>
>> +    ;; The package contains many source files without a license, some
>> +    ;; instances of the expat license, and some X11 style licenses by SGI, so
>> +    ;; we consider it to be collectively under the X11 license.
>
> Is there a top-level ‘LICENSE’ or ‘COPYING’ or ‘COPYRIGHT’ file?  If
> there is, then the intent is most likely that the files without a
> license headers are covered by whatever this top-level file says.
>
> If there is really no indication, that would make the software non-free.

Sadly, there is no such file.

Debian has it as a "source package", and has a Copyright file assembled
for it:

http://metadata.ftp-master.debian.org/changelogs/main/m/mesa-demos/mesa-demos_8.0.1-2_copyright

It builds the mesa-utils and mesa-utils-extra packages from this source
package.  Do we have to do something similar?

Taylan

  reply	other threads:[~2015-03-14 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 15:23 [PATCH] gnu: Add mesa-demos Taylan Ulrich Bayırlı/Kammer
2015-03-14 14:10 ` Ludovic Courtès
2015-03-14 14:58   ` Taylan Ulrich Bayırlı/Kammer [this message]
2015-03-14 15:04     ` Taylan Ulrich Bayırlı/Kammer
2015-03-15 14:41       ` Ludovic Courtès
2015-03-15 14:46     ` Ludovic Courtès
2015-03-17 11:15       ` Taylan Ulrich Bayırlı/Kammer
2015-03-17 11:49         ` Taylan Ulrich Bayırlı/Kammer
2015-03-18  8:49         ` Ludovic Courtès

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=87a8zf7hj9.fsf@taylan.uni.cx \
    --to=taylanbayirli@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).