From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 5/6] gnu: Add ceph.
Date: Wed, 18 Jan 2017 00:11:18 +0100 [thread overview]
Message-ID: <87r3419t9l.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87a8apb8x1.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
>> + (substitute* "src/Makefile.in"
>> + ;; By default, the PYTHONPATH is set to "src/pybind".
>> + ;; Make sure our libraries are found too.
>> + (("export PYTHONPATH=") (string-append "export PYTHONPATH="
>> + (getenv "PYTHONPATH")
>> + ":"))
>
> I’d move (string-append …) on the next line (for the following
> substitutions as well.)
I tried that, but actually found this easier to read. :-)
Will double-check.
>> + ;; Ceph is licensed under LGPL2.1, but includes a number of components
>> + ;; covered by other licenses. Consult COPYING for full information.
>> + (license (list license:lgpl2.1
>> + license:cc-by-sa3.0 ; documentation
>> + license:bsd-2 ; xxHash
>> + license:bsd-3
>> + license:gpl3
>> + license:gpl2
>> + license:public-domain
>> + license:boost1.0
>> + license:expat))))
>
> No “or any later version” clause for the GNU licenses here?
Oops, yes, there are some gpl2+ files at least. But Ceph itself is
LGPL2.1 only AFAICT; the COPYING file has a debian-style copyright
format and adds "or later" on some components but not on '*'. No
copyright headers in the source files I've checked.
Unfortunately COPYING does not cover the bundled components, so I still
have some digging to do.
> Then apart from the wrapping that you mentioned in the cover letter and
> other issues, that looks good. Great work!
Thanks! I'm sure there is a lot of work remaining to make *everything*
work (e.g. 'ceph-deploy'), but will make sure it's possible to provision
a cluster the "old school" way at least :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-01-17 23:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 20:33 [PATCH 0/6] gnu: Add ceph Marius Bakke
2017-01-15 20:33 ` [PATCH 1/6] gnu: Add leveldb Marius Bakke
2017-01-17 22:34 ` Ludovic Courtès
2017-01-15 20:33 ` [PATCH 2/6] gnu: Add crypto++ Marius Bakke
2017-01-17 22:38 ` Ludovic Courtès
2017-01-17 22:46 ` Leo Famulari
2017-01-17 22:57 ` Marius Bakke
2017-01-15 20:33 ` [PATCH 3/6] gnu: Add python-cram Marius Bakke
2017-01-17 22:36 ` Ludovic Courtès
2017-01-15 20:33 ` [PATCH 4/6] gnu: Add rocksdb Marius Bakke
2017-01-17 22:42 ` Ludovic Courtès
2017-01-18 0:10 ` Marius Bakke
2017-01-18 21:29 ` Ludovic Courtès
2017-01-15 20:33 ` [PATCH 5/6] gnu: Add ceph Marius Bakke
2017-01-17 22:47 ` Ludovic Courtès
2017-01-17 23:11 ` Marius Bakke [this message]
2017-01-18 21:27 ` Ludovic Courtès
2017-01-15 20:33 ` [PATCH 6/6] gnu: fio: Enable rbd support Marius Bakke
2017-01-17 22:48 ` 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=87r3419t9l.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.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).