search for: packagenames

Displaying 20 results from an estimated 197 matches for "packagenames".

Did you mean: packagename
2016 Jul 12
1
Is .packageName part of the official API?
Hi, I've seen that some packages use .packageName internally to infer their own name. Is that officially supported? I could not find it documented anywhere. There's utils::packageName(), which internally looks for .packageName. However, if the latter is not found, it may return NULL whereas an error would be more appropriate if a package name is expected. Using .packageName would give
2013 Nov 12
1
Own Package Installscript
Hi, i want to use Puppet to install all packages from a webserver (no repository) . Therefore I wrote following Script: class install_package { case "$operatingsystem" { SLES: { notify {"${operatingsystem} ${operatingsystemrelease} detected":} notify {"Installing $packagename now:":}
2001 Jun 12
1
help(PackageName)
Dear R Core Team, I'm wondering whether it is useful that every package should allow for help(PackageName), giving some general information about the package (more/nicer than library(help=PackageName)). This man page may include some mathematical or statistical background, or contain a guideline for the package. Cheers, Martin -- Martin Schlather email:
2005 Sep 13
1
R CMD INSTALL -l /path/to/library packagename
Background: OS: Linux Mandrake 10.1 release: R 2.1.1 editor: GNU Emacs 21.3.2 front-end: ESS 5.2.3 Colleagues Since I upgraded to R 2.1.1, I am getting a an error message from R CMD INSTALL packagename that says R_HOME ('/usr/local/lib/R') not found. That's not too surprising, since R is now in /usr/lib/R, but what is confusing me is that R CMD INSTALL -l /path/to/library
2013 Jun 04
2
Error during R CMD check
Hi All, I am encountering the following error while performing check on the R package we built: R CMD check packagename_0.99.0.tar.gz During startup - Warning message: Setting LC_CTYPE failed, using "C" * using R Under development (unstable) (2013-05-14 r62742) * using platform: x86_64-unknown-linux-gnu (64-bit) * using session charset: ASCII * checking for file
2005 Sep 14
0
R CMD INSTALL -l /path/to/library packagename/ fixed
Background: OS: Linux Mandrake 10.1 release: R 2.1.1 editor: GNU Emacs 21.3.2 front-end: ESS 5.2.3 --------------------------------- Colleagues The environment variables checked with Sys.getenv() all appeared to be in the right place. The easy fix was to copy /usr/lib/R into /usr/local/lib/R then run the R CMD INSTALL packagename then just copy the package subdirectory back to
2018 Dec 17
2
determining what depends on a rpm
> Am 16.12.2018 um 00:07 schrieb Gordon Messmer <gordon.messmer at gmail.com>: > > On 12/15/18 1:05 PM, Frank Cox wrote: >> Ultimately it would be very useful to have some kind of a tool that would generate a report from the rpms installed on a system and tell you exactly what depends on what else. Among other things you could use that report to remove stuff that's not
2009 Aug 16
1
R CMD check --use-valgrind doesn't run valgrind on tests
R CMD check --use-valgrind <packagename> used to run valgrind on the tests in the tests directory of the package. But it seems to have stopped. R-2.9.1 doesn't -- at least on my box -- and neither does R-2.10.0 (devel). I am not sure when this stopped. I think 2.8.x did this. The only old R I have around is 2.6.0 and it certainly does. R CMD check --help for 2.9.1 says (among other
2008 Oct 23
1
Automating citations in Sweave
Dear all, Is there an elegant way to add citations of packages when using Sweave? Ideally I'd like a function which creates a Bibtex-file with the packagenames as keys. The idea is to use \cite{packagename} or \cite{R} in LaTeX. I know you can get the Bibtex entry with toBibtex(citation("packagename")). But after updating R or a package one needs to update the bib-file too. When trying to automate this I came up with the code below. It generate...
2008 Nov 10
1
problem of unix package installation, following code no response: install.packages("packagename", dependecise=TRUE)
Dear list I am trying installing a package under unix, the command as below works in some case but not some other cases, the primary syndrome is R will stop there with a message: (say I am trying to install the package SASxport) ########################### Warning in install.packages("SASxport", dependencies = TRUE) : argument 'lib' is missing: using
2010 Mar 30
2
library(): load library from a specified location
Dear list memmbers, I would like to load a R library from a specified folder with library() and need help on how to call the command. The reason is that I am loading this library on a remote machine where I have no admin rights. Furthermore a library with the same name is already installed on that machine. I have modified this library slightly by modifying the source code and created a
2010 Mar 30
2
library(): load library from a specified location
Dear list memmbers, I would like to load a R library from a specified folder with library() and need help on how to call the command. The reason is that I am loading this library on a remote machine where I have no admin rights. Furthermore a library with the same name is already installed on that machine. I have modified this library slightly by modifying the source code and created a
2009 Jan 06
4
Yum Issue.. Installing Older Package Version
Hello fellow CentOS'ers- I'm trying to install a package from a not-to-be-named repository (privately operated for some proprietary software). They currently have a package I need but offer multiple versions. However, if I simply 'yum install packagename' it defaults to pulling down the most recent package. I would like to pull down the older version of the package but I'm
2009 Sep 24
1
R v2.10.0: Doc clarification for cross references and where are we heading?
Hi, in 'Writing R Extensions" of R v2.10.0, under Section 'Cross-references' (2009-09-07) it says: 1. "The markup \link{foo} (usually in the combination \code{\link{foo}}) produces a hyperlink to the help for foo. Here foo is a topic, that is the argument of \alias markup in another Rd file (possibly in another package)." 2. "You can specify a link to a different
2007 May 18
5
package installations on schedule or manual run
I would like to have packages installed either in the early morning or whenever I manually choose to do so on a particular machine. I am trying to convert my existing configuration from cfengine so in that tool I had something like: packages: Hr03|ManualRun:: <package installation commands> This basically says to install packages if it''s either 3:00-3:59am or if
2024 Aug 26
9
specials and ::
The survival package makes significant use of the "specials" argument of terms(), before calling model.frame; it is part of nearly every modeling function. The reason is that strata argments simply have to be handled differently than other things on the right hand side. Likewise for tt() and cluster(), though those are much less frequent. I now get "bug reports" from the
2011 Jun 02
1
[R-SIG-Mac] check leads to .o files and to packagename-Ex.R
On 06/02/2011 06:47 AM, Benilton Carvalho wrote: > 'R CMD check' should be applied on the .tar.gz, not on the source directory. Why? The help says: "Check R packages from package sources, which can be directories or package 'tar' archives with extension '.tar.gz', '.tar.bz2' or '.tgz'." I just skimmed through the relevant section (1.3.1) in
2004 Dec 06
4
confession
Gang, I've got to admit, what really sold me on debian was apt-get. And I've been resisting getting up to speed with yum. So, can any of ya point me to a good starter page, maybe one with migrators like me in mind? Many thanks. -- Robert Thomas ("beau") Hayes Link Open your heart, pray for peace, preach healing (c)2004ISR http://www.semanticrestructuring.com/
2018 Dec 17
1
determining what depends on a rpm
> On 12/17/18 3:50 AM, Leon Fauster via CentOS wrote: >> >> or this one :-) >> rpm -ev --test PACKAGENAME >> will list all packages that require PACKAGENAME > > > True.? I considered that, and then decided that I could never recommend > using "rpm -e" as a test, even with the --test flag, due to the risk of > operator error.? Though if you put it
2010 Sep 13
1
Problem (environment?) with R CMD CHECK
Hi all, I have a package that contains a function foo that calls a function .fooInternal via match.fun('.fooInternal'). This step is necessary because I want to give the user an option to override .fooInternal with a custom function. The .fooInternal function name is not exported. The function foo runs perfectly well when used in a normal R session. However, the function fails the R CMD