unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Troy Figiel <troy@troyfigiel.com>
To: 68159@debbugs.gnu.org
Cc: Sharlatan Hellseher <sharlatanus@gmail.com>
Subject: [bug#68159] [PATCH] gnu: Add python-camb.
Date: Wed, 17 Jan 2024 12:14:17 +0100	[thread overview]
Message-ID: <faeac24f-8a83-4751-9666-788bc8d370c8@troyfigiel.com> (raw)
In-Reply-To: <CAO+9K5pq2vFd41jSuQrbWuWit3zqPLv1SVZKAEy5BC8dwWyiwQ@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1404 bytes --]

Hi Oleg,

Perfect! I wasn't aware there was a license team that could look into this.

I think it would make sense a lot of sense to have the git checkout of
HMCode_test_outputs as a separate package. It seems more HMCode-type
packages exist, which might need access to that repo. I would be more
than happy making these changes.

It does bring up a point I hadn't thought about before: What is the
license of the data? It is only used in the build process, but that data
will be saved by the Software Heritage if I understand correctly. What
do you think?

Secondly, there is a dependency on a git submodule called forutils. I
originally assumed this was code specifically used for python-camb, but
it is included on the Fortran wiki as a separate library (and has an
expat license only, no LGLP3 components).

I have no experience using/packaging Fortran, but it has a Makefile, so
could give it a shot. Should we turn this into a separate package as well?


Best wishes,

Troy


On 2024-01-16 19:56, Sharlatan Hellseher wrote:
> Hi Troy,
> 
> Thank you for the patch.
> 
> I could build it locally and all tests passed just fine. The license
> question might need to be checked with our license team.
> 
> How about to pack the tests git checkout as internal package with
> copy-build-system, thinking if it would be usefully in some others?
> 
> Thanks,
> Oleg

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 6367 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-01-17 13:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 23:23 [bug#68159] [PATCH] gnu: Add python-camb Troy Figiel
2023-12-30 23:49 ` [bug#68159] (no subject) Troy Figiel
2024-01-16 18:56 ` [bug#68159] [PATCH] gnu: Add python-camb Sharlatan Hellseher
2024-01-16 19:09   ` Sharlatan Hellseher
2024-01-17 15:19     ` Simon Tournier
2024-01-18 11:04       ` Sharlatan Hellseher
2024-01-17 11:14   ` Troy Figiel [this message]
2024-01-18 11:42 ` Troy Figiel
2024-01-24 15:07   ` bug#68159: " Maxim Cournoyer
2024-01-21 10:42 ` [bug#68159] " Sharlatan Hellseher
2024-01-21 12:11   ` Troy Figiel
     [not found] <mailman.71232.1705523462.1170.guix-patches@gnu.org>
2024-01-17 23:04 ` Troy Figiel
2024-01-18 10:45   ` Simon Tournier

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=faeac24f-8a83-4751-9666-788bc8d370c8@troyfigiel.com \
    --to=troy@troyfigiel.com \
    --cc=68159@debbugs.gnu.org \
    --cc=sharlatanus@gmail.com \
    /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).