From imosqueira at suk.azti.es  Wed Dec  1 09:27:25 2004
From: imosqueira at suk.azti.es (Iago Mosqueira)
Date: Wed Dec  1 08:24:36 2004
Subject: [Rd] \link{} to help pages in Debian
In-Reply-To: <Pine.LNX.4.61.0411301751100.11452@gannet.stats>
References: <1101641542.9033.10.camel@xurelo.azti.local>
	<16810.59850.727242.266509@gargle.gargle.HOWL>
	<1101730130.9033.41.camel@xurelo.azti.local>
	<Pine.LNX.4.61.0411301751100.11452@gannet.stats>
Message-ID: <1101889645.19689.89.camel@xurelo.azti.local>

On Tue, 2004-11-30 at 17:56, Prof Brian Ripley wrote:

> Yes, and it is true as they are all linked to the same tree when 
> help.start is run.  You do need the alternative trees to be in your 
> .libPath() at that time.

My question is then what to do about it from the package maintainer
point of view. I want to ensure that links in help pages work regardless
of library location.

For example, my Debian system shows

> .libPaths()
[1] "/usr/local/lib/R/site-library" "/usr/lib/R/site-library"      
[3] "/usr/lib/R/library"  

So when running R CMD INSTALL I am placing packages by default in
.libPaths()[1], but debian packages get installed in .libPaths()[3]. I
assume this is a Debian package maintainer decision.

Should I use this information in any way for packae installation? Or
should R install routine take care of it? The information in R
administration manual was not clear enough for me, I am afraid.

> Only by default, just as by default they are under Linux, so
`obviously' 
> you don't know what happens under either.  Is Windows relevant here
(the 
> picture is a lot more complicated there)?

The point of windows was the same package works fine in Windows, in a
default installation with one library.

Many thanks,


iago Mosqueira


[Rd] \link{} to help pages in Debian
Iago Mosqueira