From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 47972@debbugs.gnu.org
Subject: [bug#47972] Add irods.
Date: Thu, 10 Jun 2021 10:28:21 +0200 [thread overview]
Message-ID: <874ke6aztm.fsf_-_@gnu.org> (raw)
In-Reply-To: <20210423143201.12831-1-rekado@elephly.net> (Ricardo Wurmus's message of "Fri, 23 Apr 2021 16:31:56 +0200")
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> skribis:
> * gnu/packages/boost.scm (boost-for-irods): New variable.
[...]
> +;; Sadly, this is needed for irods. It won't link with 1.69 or later.
> +(define-public boost-for-irods
> + (package
> + (name "boost-for-irods")
> + (version "1.68.0")
For this and the other “for-irods” packages, how about:
1. Inheriting from the original package (‘boost’ in this case), to at
least avoid duplicating the synopsis, description, and license?
2. Adding the ‘hidden?’ property, because they are not meant to be
installed on their own?
Apart from that, it LGTM.
Thanks!
Ludo’.
next prev parent reply other threads:[~2021-06-10 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 14:20 [bug#47972] Add irods Ricardo Wurmus
2021-04-23 14:31 ` [bug#47972] [PATCH 1/6] gnu: Add boost-for-irods Ricardo Wurmus
2021-04-23 14:31 ` [bug#47972] [PATCH 2/6] gnu: Add snappy-with-clang6 Ricardo Wurmus
2021-04-23 14:31 ` [bug#47972] [PATCH 3/6] gnu: Add nanodbc-for-irods Ricardo Wurmus
2021-04-23 14:31 ` [bug#47972] [PATCH 4/6] gnu: Add fmt-for-irods Ricardo Wurmus
2021-04-23 14:32 ` [bug#47972] [PATCH 5/6] gnu: Add irods Ricardo Wurmus
2021-04-23 14:32 ` [bug#47972] [PATCH 6/6] gnu: Add irods-client-icommands Ricardo Wurmus
2021-04-24 11:02 ` [bug#47972] [PATCH 1/6] gnu: Add boost-for-irods Maxime Devos
2021-06-10 8:28 ` Ludovic Courtès [this message]
2021-06-14 14:48 ` bug#47972: Add irods Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874ke6aztm.fsf_-_@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=47972@debbugs.gnu.org \
--cc=rekado@elephly.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.