Hi Nicolas,
The complexity comes for the following reason.
There is no use case that could make use of the path that includes the initial folder.
However, if you would call verveinej.sh from outside the current folder, you will have
troubles getting the sources in Moose. So, basically you will always have to do the cd
<some-directory> first. I just tested it on Mac, and that works, but I do not know
if having a ./ would work on Windows.
Anyway, having to cd first is not intuitive, because people would expect to be able to run
a shell script from anywhere. Failing to comply to this would produce errors that would be
too subtle for newcomers to debug.
Cheers,
Doru
On 1 May 2011, at 21:23, Nicolas Anquetil wrote:
I have been busy working on the other bugs.
I am still pondering it.
I must admit I fail to see how
"cd <some-directory> ; verveinej ."
is that much complex or annoying that "verveinej <some-directory>"
In all cases, you need to know where the root of your project is (if I understand
correctly your argument).
I could add an option, but this does not appear yet as a pressing emergency ...
nicolas
----- Mail original -----
De: moose-technology(a)googlecode.com
À: moose-dev(a)iam.unibe.ch
Envoyé: Dimanche 1 Mai 2011 10:28:38
Objet: [Moose-dev] Re: Issue 603 in moose-technology: VerveineJ should export relative
paths
Comment #1 on issue 603 by tudor.gi...(a)gmail.com: VerveineJ should
export
relative paths
http://code.google.com/p/moose-technology/issues/detail?id=603
Do we agree to have the sources without the trailing folder?
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Being happy is a matter of choice."