From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Vicente Vera <vicentemvp@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 04/19] gnu: Add r-bh.
Date: Thu, 17 Sep 2015 14:02:29 +0200 [thread overview]
Message-ID: <idjlhc56yp6.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <CAMfbzvByP8TsM6U6Sr5wC6N6dYmuaVpstVN860sZYvzx+YcRiQ@mail.gmail.com>
Vicente Vera <vicentemvp@gmail.com> writes:
> I don't know if the boost package in the distribution could be used to
> comply with the requirements. IMO it is safer to incorporate r-bh as
> it is needed by dplyr.
I took a look at the README file and have come to the conclusion that it
is best to add the package as is rather than trying to wrap the existing
Boost headers. The section “Updating” states the following:
We aim to maintain this package in a somewhat conservative fashion and
do not immediately jump the newest Boost releases. Rather, we start
from the Debian sources for Boost to ensure that we work with a
version that is at the same time current yet mature. But on occassion,
and as needed, we will go directly to Boost releases.
This means that we should treat this like an independent fork as they
don’t necessarily move as fast as our Boost package would. Also, they
only keep a subset of the Boost headers. The biggest value in having an
actual R package here is that other R packages that declare a dependency
on Boost headers will be satisfied.
I’m planning to amend the patch today and push it if there are no
objections against this.
~~ Ricardo
prev parent reply other threads:[~2015-09-17 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 16:46 [PATCH 04/19] gnu: Add r-bh Vicente Vera
2015-09-14 10:50 ` Ricardo Wurmus
2015-09-14 19:43 ` Vicente Vera
2015-09-15 17:34 ` Vicente Vera
2015-09-17 12:02 ` Ricardo Wurmus [this message]
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=idjlhc56yp6.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=vicentemvp@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 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.