Dason Kurkiewicz
Dason Kurkiewicz
It might make sense to use the same approach we use in p_load and have it check the pac_update option and if it is null set it to FALSE.
The whole point is to bootstrap the process of getting pacman on the system and loaded so I'm not sure why we would want to only load the namespace if...
Interesting. I didn't think we had backspaces hardcoded but it appears we do https://github.com/trinker/pacman/blob/ace0936406ca0186a67ee0f5cd52698f663780db/R/p_unload.R#L87 I'll try to look at this over the weekend and see what - if anything -...
I believe it was our intention as we find them noisy. At one point I thought we were going to add in a parameter to give the user more control...
I think we talked about a `silent` parameter at some point. But thinking back I'm not sure if we even included package startup messages in our consideration and that was...
Add functionality to ensure a package is installed without actually loading (and thus attaching) it.
Does `p_isinstalled` not meet your needs? https://github.com/trinker/pacman/blob/master/R/p_isinstalled.R
Add functionality to ensure a package is installed without actually loading (and thus attaching) it.
Ah - I see now. Ok. That isn't something I've found the need for but can see how it could be useful in some situations. It would be easy enough...
Probably too late. We already put out a release and don't want to have any breaking changes.
My guess is that we are expecting warnings in our tests but instead of using expect_warning we just try to suppress them but aren't doing it properly. and travis is...
I'll be honest - I've never really investigated the travis stuff as much as you have. Is this still an issue or should we close this?