search for: rarely_

Displaying 4 results from an estimated 4 matches for "rarely_".

Did you mean: rarely
2016 Dec 16
3
Upgrading a package to which other packages are LinkingTo
...(but try to be very prudent with public-facing API). Many times | > you do not. It is hard to pin down. | > | > At work we have a bunch of servers with Rcpp and many packages against them | > (installed system-wide for all users). We _very really_ needs rebuild. Edit: "We _very rarely_ need rebuilds" is what was meant there. | So that comes back to my suggestion: you should provide a way for a | dependent package to ask if your API has changed. If you say it hasn't, | the package is fine. If you say it has, the package should abort, | telling the user they need t...
2016 Dec 16
0
Upgrading a package to which other packages are LinkingTo
...with public-facing API). Many times > | > you do not. It is hard to pin down. > | > > | > At work we have a bunch of servers with Rcpp and many packages against them > | > (installed system-wide for all users). We _very really_ needs rebuild. > > Edit: "We _very rarely_ need rebuilds" is what was meant there. > > | So that comes back to my suggestion: you should provide a way for a > | dependent package to ask if your API has changed. If you say it hasn't, > | the package is fine. If you say it has, the package should abort, > | telling...
2016 Dec 16
2
Upgrading a package to which other packages are LinkingTo
On 16 December 2016 at 10:14, Duncan Murdoch wrote: | On 16/12/2016 8:37 AM, Dirk Eddelbuettel wrote: | > | > On 16 December 2016 at 08:20, Duncan Murdoch wrote: | > | Perhaps the solution is to recommend that packages which export their | > | C-level entry points either guarantee them not to change or offer | > | (require?) version checks by user code. So dplyr should start out by
2016 Dec 16
2
Upgrading a package to which other packages are LinkingTo
...Many times >> | > you do not. It is hard to pin down. >> | > >> | > At work we have a bunch of servers with Rcpp and many packages against them >> | > (installed system-wide for all users). We _very really_ needs rebuild. >> >> Edit: "We _very rarely_ need rebuilds" is what was meant there. >> >> | So that comes back to my suggestion: you should provide a way for a >> | dependent package to ask if your API has changed. If you say it hasn't, >> | the package is fine. If you say it has, the package should abort,...