<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Thanks everyone, I'll try and submit a pull request when I have a
    minute. <br>
    <br>
    Best<br>
    <br>
    Simon<br>
    <br>
    <div class="moz-cite-prefix">On 18/01/2018 12:03, Dmitriy Selivanov
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAJdZCv0GQaoAwA+1WyHHRVyHpHOrt2bS6RArUh=2FJ_nuNEj=g@mail.gmail.com"
      type="cite">
      <div dir="auto">
        <div>I was going to suggest the same - Martin is very responsive
          and open for improvements.<br>
          <div class="gmail_extra"><br>
            <div class="gmail_quote">18 янв. 2018 г. 15:00 пользователь
              <<a moz-do-not-send="true"
                href="mailto:rcpp-devel-request@lists.r-forge.r-project.org">rcpp-devel-request@lists.r-forge.r-project.org</a>>
              написал:<br type="attribution">
              <blockquote class="quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">Send
                Rcpp-devel mailing list submissions to<br>
                        <a moz-do-not-send="true"
                  href="mailto:rcpp-devel@lists.r-forge.r-project.org">rcpp-devel@lists.r-forge.r-<wbr>project.org</a><br>
                <br>
                To subscribe or unsubscribe via the World Wide Web,
                visit<br>
                        <a moz-do-not-send="true"
href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel"
                  rel="noreferrer" target="_blank">https://lists.r-forge.r-<wbr>project.org/cgi-bin/mailman/<wbr>listinfo/rcpp-devel</a><br>
                <br>
                or, via email, send a message with subject or body
                'help' to<br>
                        <a moz-do-not-send="true"
                  href="mailto:rcpp-devel-request@lists.r-forge.r-project.org">rcpp-devel-request@lists.r-<wbr>forge.r-project.org</a><br>
                <br>
                You can reach the person managing the list at<br>
                        <a moz-do-not-send="true"
                  href="mailto:rcpp-devel-owner@lists.r-forge.r-project.org">rcpp-devel-owner@lists.r-<wbr>forge.r-project.org</a><br>
                <br>
                When replying, please edit your Subject line so it is
                more specific<br>
                than "Re: Contents of Rcpp-devel digest..."<br>
                <br>
                <br>
                Today's Topics:<br>
                <br>
                   1. Re: using SparseSuite and RcppEigen in package
                (Martyn Plummer)<br>
                <br>
                <br>
                ------------------------------<wbr>------------------------------<wbr>----------<br>
                <br>
                Message: 1<br>
                Date: Wed, 17 Jan 2018 17:23:18 +0000<br>
                From: Martyn Plummer <<a moz-do-not-send="true"
                  href="mailto:plummerm@iarc.fr">plummerm@iarc.fr</a>><br>
                To: "<a moz-do-not-send="true"
                  href="mailto:simon.barthelme@gipsa-lab.fr">simon.barthelme@gipsa-lab.fr</a>"
                <<a moz-do-not-send="true"
                  href="mailto:simon.barthelme@gipsa-lab.fr">simon.barthelme@gipsa-lab.fr</a>><wbr>,<br>
                        "<a moz-do-not-send="true"
                  href="mailto:edd@debian.org">edd@debian.org</a>" <<a
                  moz-do-not-send="true" href="mailto:edd@debian.org"><a class="moz-txt-link-abbreviated" href="mailto:edd@debian.org">edd@debian.org</a></a>>,<br>
                        "<a moz-do-not-send="true"
                  href="mailto:rcpp-devel@lists.r-forge.r-project.org">rcpp-devel@lists.r-forge.r-<wbr>project.org</a>"<br>
                        <<a moz-do-not-send="true"
                  href="mailto:rcpp-devel@lists.r-forge.r-project.org">rcpp-devel@lists.r-forge.r-<wbr>project.org</a>><br>
                Subject: Re: [Rcpp-devel] using SparseSuite and
                RcppEigen in package<br>
                Message-ID: <<a moz-do-not-send="true"
                  href="mailto:1516209796.843.99.camel@iarc.fr">1516209796.843.99.camel@iarc.<wbr>fr</a>><br>
                Content-Type: text/plain; charset="utf-8"<br>
                <br>
                I think it is worth asking Martin Maechler if he could
                expose more<br>
                SuiteSparse functionality through the Matrix package.<br>
                <br>
                Martyn<br>
                <br>
                On Wed, 2018-01-17 at 15:06 +0100, Simon Barthelm?
                wrote:<br>
                > Hi Dirk,<br>
                ><br>
                > Thanks for your suggestion - I had thought of doing
                that but it requires<br>
                > tracking the versions of SuiteSparse used by
                Matrix, which means extra<br>
                > maintenance work. OTOH maybe updates are rare
                enough that it's not worth<br>
                > worrying about. It'd be nice if Matrix could expose
                more of SuiteSparse,<br>
                > though, I'm sure I'm not the only one who needs
                that stuff.<br>
                ><br>
                > Best<br>
                ><br>
                > Simon<br>
                ><br>
                ><br>
                > Le 17/01/2018 ? 13:35, Dirk Eddelbuettel a ?crit :<br>
                > > On 17 January 2018 at 13:10, Simon Barthelm?
                wrote:<br>
                > > > I'm trying to use some CHOLMOD
                functionality inside an R package<br>
                > > > (specifically, sparse Cholesky
                updates/downdates). There's an<br>
                > > > CHOLMOD/Eigen interface for that, but
                unfortunately the header I need is<br>
                > > > not shipped as part of either the Matrix
                package or the Rcpp package.<br>
                > > > The file is cholmod_modify.h, and it does
                appear in the src/ directory<br>
                > > > of the Matrix package, but not in the
                include/ directory.<br>
                > > ><br>
                > > > If I include it by hand I risk version
                conflicts, because the rest of<br>
                > > > CHOLMOD is provided by the Matrix package
                via RcppEigen. What's the<br>
                > > > clean way of handling that? Thanks for
                your input!<br>
                > ><br>
                > > I know "some" (eg rstan) have completemented
                the BH package with local<br>
                > > headers when BH was missing what they needed
                (as BH grew, I think we by now<br>
                > > added all they need).  So you could just do
                that, being careful to stick with<br>
                > > the same version.<br>
                > ><br>
                > > Or would Yixuan's RSpectra help?  <a
                  moz-do-not-send="true"
                  href="https://cran.r-project.org/package=RSpectra"
                  rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="https://cran.r-project.org/">https://cran.r-project.org/</a><wbr>package=RSpectra</a><br>
                > ><br>
                > > Dirk<br>
                > ><br>
                ><br>
                > ______________________________<wbr>_________________<br>
                > Rcpp-devel mailing list<br>
                > <a moz-do-not-send="true"
                  href="mailto:Rcpp-devel@lists.r-forge.r-project.org">Rcpp-devel@lists.r-forge.r-<wbr>project.org</a><br>
                > <a moz-do-not-send="true"
href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel"
                  rel="noreferrer" target="_blank">https://lists.r-forge.r-<wbr>project.org/cgi-bin/mailman/<wbr>listinfo/rcpp-devel</a><br>
                <br>
                ------------------------------<br>
                <br>
                ______________________________<wbr>_________________<br>
                Rcpp-devel mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:Rcpp-devel@lists.r-forge.r-project.org">Rcpp-devel@lists.r-forge.r-<wbr>project.org</a><br>
                <a moz-do-not-send="true"
href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel"
                  rel="noreferrer" target="_blank">https://lists.r-forge.r-<wbr>project.org/cgi-bin/mailman/<wbr>listinfo/rcpp-devel</a><br>
                <br>
                End of Rcpp-devel Digest, Vol 99, Issue 6<br>
                ******************************<wbr>***********<br>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Rcpp-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Rcpp-devel@lists.r-forge.r-project.org">Rcpp-devel@lists.r-forge.r-project.org</a>
<a class="moz-txt-link-freetext" href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel</a></pre>
    </blockquote>
    <br>
  </body>
</html>