On 4/30/2008 5:02 PM, Simon Urbanek wrote:
On Apr 30, 2008, at 4:29 PM, Duncan Murdoch wrote:
On 4/30/2008 4:01 PM, Simon Urbanek wrote:
On Apr 30, 2008, at 2:31 PM, Duncan Murdoch wrote:
On 4/30/2008 11:56 AM, Michael wrote:
On 29 Apr 2008, Duncan Murdoch wrote:
Right, you don't need to set
On Apr 30, 2008, at 4:29 PM, Duncan Murdoch wrote:
On 4/30/2008 4:01 PM, Simon Urbanek wrote:
On Apr 30, 2008, at 2:31 PM, Duncan Murdoch wrote:
On 4/30/2008 11:56 AM, Michael wrote:
On 29 Apr 2008, Duncan Murdoch wrote:
Right, you don't need to set the system path for everything,
but you
On 4/30/2008 4:01 PM, Simon Urbanek wrote:
On Apr 30, 2008, at 2:31 PM, Duncan Murdoch wrote:
On 4/30/2008 11:56 AM, Michael wrote:
On 29 Apr 2008, Duncan Murdoch wrote:
Right, you don't need to set the system path for everything, but
you do
need to set it in CMD (or other shell) before ru
On Apr 30, 2008, at 2:31 PM, Duncan Murdoch wrote:
On 4/30/2008 11:56 AM, Michael wrote:
On 29 Apr 2008, Duncan Murdoch wrote:
Right, you don't need to set the system path for everything, but
you do
need to set it in CMD (or other shell) before running Rcmd.
For Win 2K/XP/Vista, the system
On 4/30/2008 11:56 AM, Michael wrote:
On 29 Apr 2008, Duncan Murdoch wrote:
Right, you don't need to set the system path for everything, but you do
need to set it in CMD (or other shell) before running Rcmd.
For Win 2K/XP/Vista, the system path can be set (through the GUI interface,
not sure
You can use the Windows batch PATH command.
On Wed, Apr 30, 2008 at 11:56 AM, Michael <[EMAIL PROTECTED]> wrote:
> On 29 Apr 2008, Duncan Murdoch wrote:
>
> > Right, you don't need to set the system path for everything, but you do
> > need to set it in CMD (or other shell) before running Rcmd.
>
>
On 29 Apr 2008, Duncan Murdoch wrote:
> Right, you don't need to set the system path for everything, but you do
> need to set it in CMD (or other shell) before running Rcmd.
For Win 2K/XP/Vista, the system path can be set (through the GUI interface,
not sure how to do it with scripts) without re
On Tue, Apr 29, 2008 at 4:00 PM, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> On 29/04/2008 2:51 PM, Gabor Grothendieck wrote:
> > The use of the UNIX find command on Windows makes installation
> > very troublesome and fragile. I wonder if you could include a
> > find2 or somesuch with the tools a
On 29/04/2008 4:26 PM, Michael wrote:
On 29 Apr 2008, Duncan Murdoch wrote:
On 29/04/2008 12:54 PM, Michael wrote:
I've been trying to build a Windows binary of a package of mine without
success. It seems that the files under inst/doc throw the script off.
I am using the command 'Rcmd INS
On 29 Apr 2008, Duncan Murdoch wrote:
> On 29/04/2008 12:54 PM, Michael wrote:
> > I've been trying to build a Windows binary of a package of mine without
> > success. It seems that the files under inst/doc throw the script off.
> >
> > I am using the command 'Rcmd INSTALL --build'.
> >
> >
On 29/04/2008 2:51 PM, Gabor Grothendieck wrote:
The use of the UNIX find command on Windows makes installation
very troublesome and fragile. I wonder if you could include a
find2 or somesuch with the tools and change the scripts to use that
getting rid of find or use just use the Windows find
The use of the UNIX find command on Windows makes installation
very troublesome and fragile. I wonder if you could include a
find2 or somesuch with the tools and change the scripts to use that
getting rid of find or use just use the Windows find command in the
scripts. Or some other solution so
On Tue, 29 Apr 2008, Michael wrote:
I've been trying to build a Windows binary of a package of mine without
success. It seems that the files under inst/doc throw the script off.
I am using the command 'Rcmd INSTALL --build'.
-- Making package genepi
adding build stamp t
On 29/04/2008 12:54 PM, Michael wrote:
I've been trying to build a Windows binary of a package of mine without
success. It seems that the files under inst/doc throw the script off.
I am using the command 'Rcmd INSTALL --build'.
-- Making package genepi
adding build stamp
14 matches
Mail list logo
