search for: packagenam

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 n...

...(no repository) . Therefore I wrote following Script: class install_package { case "$operatingsystem" { SLES: { notify {"${operatingsystem} ${operatingsystemrelease} detected":} notify {"Installing $packagename now:":} exec { ''installing $packagename'': command => "rpm -iv ${repopath}${packagename}", path => ["/usr/bin", "/usr/sbin", "/bin"]...

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: Martin.Schlather@uni-bayre...

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 packagename is giving me the same message, suggesting that I am misusing the -lib switch when I enter R CMD IN...

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 'packagename/DESCRIPTION' ... OK *...

...andrake 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 /usr/lib/R/library A cheat fix, but it worked. Sam >-----Original Message----- >From: Gabor Grothendieck [mailto:ggrothendieck at gmail.com] >Sent: Tuesday, 13 September 2005 3:41 PM >To: McClatchie, Sam (PIRSA-SARDI) >Cc: r-help a...

...t; > While not a simple answer, this bash function will provide what you're looking for: > > whatrequires () { (rpm -q --qf '%{NAME}\n' "$1" ; rpm -q --provides "$1" ) | tr \\n \\0 | xargs -0 rpm -q --whatrequires ; } > or this one :-) rpm -ev --test PACKAGENAME will list all packages that require PACKAGENAME -- LF

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 certai...

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 genera...

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

...hts. 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 "personal" version of this library that I now want to load instead of the standart one. Running: R CMD INSTALL 'path*/*packagename* --library=*path*/Software/R-packages i managed to compile my modified version on the remote machine and save the library in a folder on that machine. When I now start R and run library(packagename) R still seem to load the version installed on the remote computer, even though i added my f...

...hts. 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 "personal" version of this library that I now want to load instead of the standart one. Running: R CMD INSTALL 'path*/*packagename* --library=*path*/Software/R-packages i managed to compile my modified version on the remote machine and save the library in a folder on that machine. When I now start R and run library(packagename) R still seem to load the version installed on the remote computer, even though i added my f...

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 unable to do so. So, how would you specify version number for a package with two candidates but the same name? I'm at a loss... :-( Tim Nelson Systems/Network Supp...

..., but not necessarily as an \name{<topic>}. The link will be display as the string <topic>. B. \link[=<topic>]{<name>} - where <topic> must occur as an \alias{<topic>} with a \name{<name>}. The link will be display as the string <name>. C. \link{<packageName>]{<name>} - where <name> must be a \name{<name>} in a package named <packageName>. The link will be display as the string <name>. D. \link{<packageName>:<name>]{<label>} - where <name> must be a \name{<name>} in a package named <pa...

...ither the packages were installed around 3am or they were installed when I manually chose to do so by specifying "-DManualRun" on the command line when calling the cfengine client. Is there a way to do something similar in puppet? I have found that I can use either: package { "packagename": ensure => latest, schedule => "daily" } (where "daily" is defined as between 2-4am) OR package { "packagename": ensure => latest, tag => "manualrun" } These each do what I want them to do, but if I try to combine them: package { "...

...ery 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 growing segment that believes one should put packagename:: in front of every single instance.?? For instance ????? fit <- survival::survdiff( survival::Surv(time, status) ~ ph.karno + survival::strata(inst),? data= survival::lung) This fails to give the correct answer because it fools terms(formula, specials= "strata").??? I've stoo...

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

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/

> 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 in an alias, I suppose t...

...he R CMD CHECK command with the error Error in get(as.character(FUN), mode = "function", envir = envir) : object '.fooInternal' of mode 'function' was not found I'm wondering if this is some environment misspecification issue? I also tried replacing .fooInternal by packageName:::.fooInternal (replacing packageName with actual package name, of course), to no avail. Thanks in advance for all replies. Peter