I trying to figure out how command-line arguments are passed to image...
and this is complete mess.
I cannot determine why on Windoze, a script argument passed in command
line is ignored.
--
Best regards,
Igor Stasenko AKA sig.
Looks like you run into the same problem as Tudor:
If you want to give an absolute path you have to use the file protocol
since otherwise it is interpreted as a relative path due to some
changes to support relative paths (I think that was done for coral).
A detailed example is explained in my
I trying to figure out how command-line arguments are passed to image...
and this is complete mess.
what if this is broken don't fix it
;D
Yes we will fix that tooo
I cannot determine why on Windoze, a script argument passed in command
line is ignored.
--
Best regards,
Apparently, it is not broken at all. Like Torsten said, you have to explicitly
mention that you want the file: if you want to specify an absolute path.
Cheers,
Doru
On 16 Mar 2011, at 16:14, Stéphane Ducasse wrote:
I trying to figure out how command-line arguments are passed to image...
What igor means is that it would be good to have a consistent and unified way
to pass information to the vm.
Right now the mac vm does not handle well -headless and each vm has its
different ways to handle arguments.
Stef
On Mar 16, 2011, at 4:23 PM, Tudor Girba wrote:
Apparently, it is not
Yes we will fix that tooo
It's not a bug - more an undocumented features
that URI's are now used and that means to use
file: protocol for absolute paths.
If I remember correctly I saw a sd on the method
somewhere ;)
Bye
T.
P.S.: I hope with hudson accessing different OS machines
yes... we need a common command line options (and maybe very specific platform
command line options too, but there should be a common way to do common things
:)
best,
Esteban
El 16/03/2011, a las 12:38p.m., Stéphane Ducasse escribió:
What igor means is that it would be good to have a
On Mar 16, 2011, at 4:41 PM, Torsten Bergmann wrote:
Yes we will fix that tooo
It's not a bug - more an undocumented features
that URI's are now used and that means to use
file: protocol for absolute paths.
If I remember correctly I saw a sd on the method
somewhere ;)
yes
+ 1
yes... we need a common command line options (and maybe very specific
platform command line options too, but there should be a common way to do
common things :)
best,
Esteban
On 16 March 2011 16:23, Tudor Girba tudor.gi...@gmail.com wrote:
Apparently, it is not broken at all. Like Torsten said, you have to
explicitly mention that you want the file: if you want to specify an
absolute path.
Its not broken.. But as to me it contains too many hops between the
as i said.. it is too clever :)
Yes and as I already noted on issue #3595 relative paths are now
supported but relative means currently relative to the image location
since FileDirectory default is used.
I think there is not yet a primitive to tell you where the VM is located
and that was the
On 16 March 2011 17:07, Torsten Bergmann asta...@gmx.de wrote:
as i said.. it is too clever :)
Yes and as I already noted on issue #3595 relative paths are now
supported but relative means currently relative to the image location
since FileDirectory default is used.
I think there is not yet a
On Wed, Mar 16, 2011 at 9:14 AM, Igor Stasenko siguc...@gmail.com wrote:
On 16 March 2011 17:07, Torsten Bergmann asta...@gmx.de wrote:
as i said.. it is too clever :)
Yes and as I already noted on issue #3595 relative paths are now
supported but relative means currently relative to the
+1
Em 16-03-2011 12:42, Esteban Lorenzano escreveu:
yes... we need a common command line options (and maybe very specific
platform command line options too, but there should be a common way to do
common things :)
best,
Esteban
mm. no. Typically a relative paths are relative to the directory where
you issued the command line,
not relative to the directory where command located.
Right.
Aren't we going to replace all the old FileDirectory crap with Colin's code?
Please??
We are working on it but it takes
15 matches
Mail list logo
