Displaying 3 results from an estimated 3 matches for "origfilepath".
2004 Apr 27
1
'R CMD build' fails when there are spaces in the path (PR#6830)
Full_Name: Byron Ellis
Version: R 1.9.0 (and 2.0.0)
OS: Linux (Redhat Fedora Core)
Submission from: (NULL) (140.247.241.197)
It appears that `R CMD build` cannot handle spaces in the path when building
packages for distribution. For instance:
[ellis@net-78815 ~/Bayesian Networks]$ R CMD build bnsl
* checking for file 'bnsl/DESCRIPTION' ... OK
* preparing 'bnsl':
* cleaning src
*
2007 Jun 29
1
R CMD build with mingw and msys (PR#9766)
...q "windows");
-my $MSYS = ( $ENV{OSTYPE} eq "msys" );
my @exclude_patterns = R::Utils::get_exclude_patterns();
@@ -222,14 +221,10 @@
my $filepath = &file_path($startdir, $filename);
## under Windows, need separate Cygwin and Windows versions of path.
my $origfilepath = $filepath;
- if ($MSYS) {
- ## different workwaround for MSYS
- $filepath =~ s+^([A-Za-z]):+/\1/+;
- } elsif ($WINDOWS) {
- ## workaround for paths in Cygwin tar
- $filepath =~ s+^([A-Za-z]):+/cygdrive/\1+;
+ if($WINDOWS) {
+...
2005 May 09
1
can't build packages anymore...
...t
it never hurts to look). I found the following lines:
my $filename = "${pkgname}_" . $description->{"Version"} . ".tar";
my $filepath = &file_path($startdir, $filename);
## under Windows, need separate Cygwin and Windows versions of path.
my $origfilepath = $filepath;
if($WINDOWS) {
## workaround for paths in Cygwin tar
$filepath =~ s+^([A-Za-x]):+/cygdrive/\1+;
}
And I'm not sure why that's in there. Aren't packages that are built under
Windows using the Mingw and MSYS tools exclusively? Should they? Could they?
I'm not...