On 02/08/2016 6:34 PM, Dirk Eddelbuettel wrote:
On 2 August 2016 at 18:13, Duncan Murdoch wrote:
| Okay, now I think I understand, but I agree with CRAN. It is not
| feasible to tell if the test happened somewhere in the code unless we
| enforce a particular way of writing the test.
Debian
On 02/08/2016 4:20 PM, Dirk Eddelbuettel wrote:
On 2 August 2016 at 16:07, Duncan Murdoch wrote:
| On 02/08/2016 1:41 PM, Dirk Eddelbuettel wrote:
| >
| > On 2 August 2016 at 13:12, Duncan Murdoch wrote:
| > | On 02/08/2016 1:01 PM, Dirk Eddelbuettel wrote:
| > | >
| > | > On 2 August 2016 at
Not strictly what you're asking, but at some point it may be important to note
that the "QR" method used by lm() and friends (notably anova() and aov())
actually relies on successive orthogonalization. This does yield a QR
decomposition but the reverse is not true. A generic X=QR decomposition
On 2 August 2016 at 16:07, Duncan Murdoch wrote:
| On 02/08/2016 1:41 PM, Dirk Eddelbuettel wrote:
| >
| > On 2 August 2016 at 13:12, Duncan Murdoch wrote:
| > | On 02/08/2016 1:01 PM, Dirk Eddelbuettel wrote:
| > | >
| > | > On 2 August 2016 at 11:36, Joshua Ulrich wrote:
| > | > | Maybe I'm
On 02/08/2016 1:41 PM, Dirk Eddelbuettel wrote:
On 2 August 2016 at 13:12, Duncan Murdoch wrote:
| On 02/08/2016 1:01 PM, Dirk Eddelbuettel wrote:
| >
| > On 2 August 2016 at 11:36, Joshua Ulrich wrote:
| > | Maybe I'm missing something, but isn't that the point of calling
| > |
On 2 August 2016 at 13:12, Duncan Murdoch wrote:
| On 02/08/2016 1:01 PM, Dirk Eddelbuettel wrote:
| >
| > On 2 August 2016 at 11:36, Joshua Ulrich wrote:
| > | Maybe I'm missing something, but isn't that the point of calling
| > | requireNamespace()? For example:
| > | if
On 02/08/2016 1:01 PM, Dirk Eddelbuettel wrote:
On 2 August 2016 at 11:36, Joshua Ulrich wrote:
| Maybe I'm missing something, but isn't that the point of calling
| requireNamespace()? For example:
| if (requireNamespace("suggestedPackage"))
| stop("suggestedPackage required but not
On 2 August 2016 at 11:36, Joshua Ulrich wrote:
| Maybe I'm missing something, but isn't that the point of calling
| requireNamespace()? For example:
| if (requireNamespace("suggestedPackage"))
| stop("suggestedPackage required but not installed")
|
| That doesn't seem like a heavy burden for
Dirk,
That is useful. I think the "Recommends" category from that link is
pretty much what I am suggesting - something that should be installed
if it's available in the package repository but is not loaded/imported
by default.
Some of those other relationships sound like they would also be
On Tue, Aug 2, 2016 at 11:26 AM, Thomas J. Leeper wrote:
> I have a fairly open-ended question about the handling of package
> dependencies that is inspired by the precise distinction between
> "Depends", "Imports", and "Suggests" listed in DESCRIPTION.
>
> Some background,
See eg https://www.debian.org/doc/debian-policy/ch-relationships.html
We have other big fish to fry. Eg many packages have LinkingTo: BH (as Boost
headers are indeed awesome) but this 120 mb (!!) payload is needed _once_
during package compilation / installation and never again afterwards. So
I have a fairly open-ended question about the handling of package
dependencies that is inspired by the precise distinction between
"Depends", "Imports", and "Suggests" listed in DESCRIPTION.
Some background, as I understand it: Prior to requiring package
namespaces, we listed package dependencies
12 matches
Mail list logo