On 12/7/07, Barry Rowlingson <[EMAIL PROTECTED]> wrote:
> Gabor Grothendieck wrote:
> > An svn checkout directory can contain a mix of files that
> > are mirrored in the svn and not mirrored. In particular, if you
> > add a new file into your checkout directory it will not automatically
> > go int
Oleg Sklyar wrote:
> If I am not mistaken R CMD build builds the package temporarily and uses
> that build to build the vignette, so where is the problem? All my
> vignettes build fine on both Linux and Windows and on Windows you
> actually see that running R CMD build --binary builds the source c
These files in the SVN tree does not harm the things that are checked
in. However it is indeed reasonable to keep the rubbish out, so:
> I've started a new package and I'm trying to work out the best way to do
> it. I'm managing my package source directory with SVN, but "R CMD build"
> likes to
Gabor Grothendieck wrote:
> An svn checkout directory can contain a mix of files that
> are mirrored in the svn and not mirrored. In particular, if you
> add a new file into your checkout directory it will not automatically
> go into the repository on your next commit unless you specifically
> pla
An svn checkout directory can contain a mix of files that
are mirrored in the svn and not mirrored. In particular, if you
add a new file into your checkout directory it will not automatically
go into the repository on your next commit unless you specifically
place that file under svn control so ju
I've started a new package and I'm trying to work out the best way to do
it. I'm managing my package source directory with SVN, but "R CMD build"
likes to dump things in the inst/doc directory when making vignette PDF
files. I don't want to keep these in SVN (they aren't strictly
'source'), so
Peter Kleiweg wrote:
> Prof Brian Ripley schreef op de 7e dag van de wijnmaand van het jaar 2005:
>
>
>>On Fri, 7 Oct 2005, Peter Kleiweg wrote:
>>
>>
>>>Duncan Murdoch schreef op de 6e dag van de wijnmaand van het jaar 2005:
>>>
>>>
On Fri, 7 Oct 2005, Peter Kleiweg wrote:
>Wha
On Fri, 7 Oct 2005, Peter Kleiweg wrote:
> Prof Brian Ripley schreef op de 7e dag van de wijnmaand van het jaar 2005:
>
>> On Fri, 7 Oct 2005, Peter Kleiweg wrote:
>>
>>> Duncan Murdoch schreef op de 6e dag van de wijnmaand van het jaar 2005:
>>>
On Fri, 7 Oct 2005, Peter Kleiweg wrote:
Prof Brian Ripley schreef op de 7e dag van de wijnmaand van het jaar 2005:
> On Fri, 7 Oct 2005, Peter Kleiweg wrote:
>
> > Duncan Murdoch schreef op de 6e dag van de wijnmaand van het jaar 2005:
> >
> > > On Fri, 7 Oct 2005, Peter Kleiweg wrote:
> > >
> > > > What has changed in R for Windows
On Fri, 7 Oct 2005, Peter Kleiweg wrote:
> Duncan Murdoch schreef op de 6e dag van de wijnmaand van het jaar 2005:
>
>> On Fri, 7 Oct 2005, Peter Kleiweg wrote:
>>
>>>
>>> What has changed in R for Windows from version 1.7.1 to
>>> 2.2.0 that won't allow me to build binary packages?
>>
>> Many thi
Duncan Murdoch schreef op de 6e dag van de wijnmaand van het jaar 2005:
> On Fri, 7 Oct 2005, Peter Kleiweg wrote:
>
> >
> > What has changed in R for Windows from version 1.7.1 to
> > 2.2.0 that won't allow me to build binary packages?
>
> Many things have changed; I don't know which is causin
On Fri, 7 Oct 2005, Peter Kleiweg wrote:
>
> What has changed in R for Windows from version 1.7.1 to
> 2.2.0 that won't allow me to build binary packages?
Many things have changed; I don't know which is causing the failure you
see. One change is that instructions are now collected in the
Ins
What has changed in R for Windows from version 1.7.1 to
2.2.0 that won't allow me to build binary packages?
On 1.7.1 I built a packge with this command:
Rcmd build --force --binary iL04
On 2.2.0 this fails. First I had to copy sh.exe from d:\bin to
c:\bin. This got me over the first hurdle
13 matches
Mail list logo
