For a few years now I had mused about how nice it would be to have other
scripts triggered like `cleanup`. For Rcpp, it would be nice to run
compileAttributes(). For roxygen2, it would be nice to run roxygenize()
(especially if that continued to work the way it did, but I digress).
That was mos
On Fri, 4 Jan 2019 at 16:43, Dirk Eddelbuettel wrote:
>
>
> For a few years now I had mused about how nice it would be to have other
> scripts triggered like `cleanup`. For Rcpp, it would be nice to run
> compileAttributes(). For roxygen2, it would be nice to run roxygenize()
> (especially if tha
On 4 January 2019 at 19:24, Iñaki Ucar wrote:
| On Fri, 4 Jan 2019 at 16:43, Dirk Eddelbuettel wrote:
| >
| >
| > For a few years now I had mused about how nice it would be to have other
| > scripts triggered like `cleanup`. For Rcpp, it would be nice to run
| > compileAttributes(). For roxygen
On Fri, 4 Jan 2019 at 19:42, Dirk Eddelbuettel wrote:
>
>
> On 4 January 2019 at 19:24, Iñaki Ucar wrote:
> | On Fri, 4 Jan 2019 at 16:43, Dirk Eddelbuettel wrote:
> | >
> | >
> | > For a few years now I had mused about how nice it would be to have other
> | > scripts triggered like `cleanup`. F
On 04/01/2019 1:42 p.m., Dirk Eddelbuettel wrote:
On 4 January 2019 at 19:24, Iñaki Ucar wrote:
| On Fri, 4 Jan 2019 at 16:43, Dirk Eddelbuettel wrote:
| >
| >
| > For a few years now I had mused about how nice it would be to have other
| > scripts triggered like `cleanup`. For Rcpp, it would
Iñaki, Duncan,
Fabulous -- that is just the type of 'hack' I was hoping for in the short
term.
Longer term, it would indeed be nice to do something about this and create
something better. I had looked once or twice at packages utils and tools but
didn't quite find the right spot to connect it
Add a tag to the DESCRIPTION file or configure.ac-like indicating the git
(presumably) revision, perhaps like https://stackoverflow.com/a/11535358/547331
?
On 1/4/19, 1:42 PM, "R-package-devel on behalf of Dirk Eddelbuettel"
wrote:
On 4 January 2019 at 19:24, Iñaki Ucar wrote:
|
On 4 January 2019 at 19:37, Martin Morgan wrote:
| Add a tag to the DESCRIPTION file or configure.ac-like indicating the git
(presumably) revision, perhaps like https://stackoverflow.com/a/11535358/547331
?
I need the path. I need to find the particular build / checkout of headers
and libaries
On Fri, 4 Jan 2019 at 20:10, Iñaki Ucar wrote:
>
> I see. Then I suggest the following hack (not tested). If the package
> has a vignette, put there a hidden chunk that generates a file with
> info about the branch and the path. This file will be available for
> your configure script, which runs a
On 5 January 2019 at 00:00, Iñaki Ucar wrote:
| On Fri, 4 Jan 2019 at 20:10, Iñaki Ucar wrote:
| >
| > I see. Then I suggest the following hack (not tested). If the package
| > has a vignette, put there a hidden chunk that generates a file with
| > info about the branch and the path. This file w
10 matches
Mail list logo
