unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Jack Hill <jackhill@jackhill.us>, guix-devel@gnu.org
Subject: Re: Jam: which licence is this?
Date: Sun, 25 Apr 2021 13:42:16 -0400	[thread overview]
Message-ID: <87pmyijm5o.fsf@netris.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2104250213150.8414@marsh.hcoop.net>

Hi Jack,

Jack Hill <jackhill@jackhill.us> writes:

> I'm working on packaging the Argyll Color Management System for Guix. To 
> build, it uses the Jam tool, which has the following license:
>
> ```
> This is Release 2.5 of Jam, a make-like program.
>
> License is hereby granted to use this software and distribute it
> freely, as long as this copyright notice is retained and modifications
> are clearly marked.
>
> ALL WARRANTIES ARE HEREBY DISCLAIMED.
> ```
>
> Which license is this?

Thanks very much for your diligence here.

I looked into it, and Debian calls this the "Perforce" license.  The
"copyright" file for Debian's 'boost' package includes the following
lines:

--8<---------------cut here---------------start------------->8---
License: Perforce
 License is hereby granted to use this software and distribute it
 freely, as long as this copyright notice is retained and modifications
 are clearly marked.
 .
 ALL WARRANTIES ARE HEREBY DISCLAIMED.
--8<---------------cut here---------------end--------------->8---

<https://metadata.ftp-master.debian.org/changelogs//main/b/boost1.67/boost1.67_1.67.0-13+deb10u1_copyright>

Maybe this should be added to (guix licenses) as 'perforce', or perhaps
'perforce-jam'?

Thoughts?

      Mark

-- 
Support Richard Stallman against the vicious disinformation campaign
against him and the FSF.  See <https://stallmansupport.org> for more.


  parent reply	other threads:[~2021-04-25 17:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25  6:15 Jam: which licence is this? Jack Hill
2021-04-25  7:16 ` Ricardo Wurmus
2021-04-25 17:25   ` Mark H Weaver
2021-04-25 17:35     ` Leo Famulari
2021-04-25 20:37       ` Mark H Weaver
2021-04-26 16:24         ` Leo Famulari
2021-05-02  4:53           ` Mark H Weaver
2021-05-02 15:20             ` Leo Famulari
2021-05-07 18:31               ` The purpose of the "license" list of a Guix package (Was: Re: Jam: which licence is this?) Chris Marusich
2021-05-07 19:23                 ` The purpose of the "license" list of a Guix package Chris Marusich
2021-05-08 10:16                 ` The purpose of the "license" list of a Guix package (Was: Re: Jam: which licence is this?) Leo Prikler
2021-05-08 11:17                   ` Ricardo Wurmus
2021-05-08 11:22                     ` Leo Prikler
2021-05-08 20:52                   ` Maxime Devos
2021-05-08 23:04                     ` Leo Prikler
2021-05-09  8:33                       ` Maxime Devos
2021-05-02 21:12             ` Jam: which licence is this? Ludovic Courtès
2021-04-25 17:42 ` Mark H Weaver [this message]
2021-04-28 13:20   ` Maxim Cournoyer
2021-04-25 20:23 ` Vagrant Cascadian
2021-04-25 20:49   ` Ricardo Wurmus
2021-04-25 20:53   ` Jack Hill
2021-04-25 21:04     ` Jack Hill
2021-04-26 14:36       ` Jack Hill
2021-05-02  5:02         ` Mark H Weaver
2021-04-25 21:41     ` Vagrant Cascadian

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=87pmyijm5o.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=jackhill@jackhill.us \
    /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).