Thansk for the latest changes, they work like a charm now.
I have done something which I do not know whether it is a desired protocol. Namely I have submitted patches for asdf-ecl.lisp using launchpad.
I did this because I always found it more convenient to have a look at the ECL bug/patch tracker thank keeping track of the emails with patches and remember whether they were committed.
Is it ok? Should I continue doing so with the following patches, such as test cases, etc?
Juanjo
On 19 March 2010 13:34, Juan Jose Garcia-Ripoll juanjose.garciaripoll@googlemail.com wrote:
Thansk for the latest changes, they work like a charm now.
Glad to know it was "just" a package problem, and thanks to Robert for the diagnostic and to you for the explanation! I'm glad it didn't require any deep algorithmic fix.
I have done something which I do not know whether it is a desired protocol. Namely I have submitted patches for asdf-ecl.lisp using launchpad. I did this because I always found it more convenient to have a look at the ECL bug/patch tracker thank keeping track of the emails with patches and remember whether they were committed. Is it ok? Should I continue doing so with the following patches, such as test cases, etc?
You did the right thing. It's better to file issues that way indeed.
Committed as 1.656.
We're drawing close to a ASDF 2 release. Is there anything missing in the documentation?
The only piece of code which I think is missing, is support for configuration paths under Windows.
Can you help with the configuration on Windows? What is the ECL equivalent of LispWorks' get-folder-path? Or if there isn't one builtin, how do I read a string entry from the registry? Can you test ASDF with ECL on Windows? Do these environment variables USERPROFILE and ALLUSERSPROFILE actually exist?
[If users or vendors of other implementations are around, I'm soliciting the same services.]
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] You cannot teach a man anything; you can only help him find it for himself. — attributed to Galileo Galilei
On Fri, Mar 19, 2010 at 7:51 PM, Faré fahree@gmail.com wrote:
Can you help with the configuration on Windows? What is the ECL equivalent of LispWorks' get-folder-path? Or if there isn't one builtin, how do I read a string entry from the registry?
We do not export in ECL any way to read the registry, nor any function to get local paths for concepts like Desktop, Documents, etc.
Can you test ASDF with ECL on Windows?
Sure. I am building it right now. But is there a way to run the tests here?
Do these environment variables USERPROFILE and ALLUSERSPROFILE actually exist?
They do exist.However, I have a problem with ASDF's use of ALLUSERSPROFILE, because it is mixed with a pathname "Application Data ..." which may have a different name on a different language -- Windows has the bad habit of naming system folders differently depending on the localization of the operating system. Unfortunately all my copies of Windows are installed with US locale and language so I can not check this.
Juanjo
On 19 March 2010 15:24, Juan Jose Garcia-Ripoll juanjose.garciaripoll@googlemail.com wrote:
On Fri, Mar 19, 2010 at 7:51 PM, Faré fahree@gmail.com wrote:
Can you help with the configuration on Windows? What is the ECL equivalent of LispWorks' get-folder-path? Or if there isn't one builtin, how do I read a string entry from the registry?
We do not export in ECL any way to read the registry, nor any function to get local paths for concepts like Desktop, Documents, etc.
Hum. Could such a way be made available in ECL, possibly through (require :windows-registry) or some such? I'm sure that would help all Windows developers.
Can you test ASDF with ECL on Windows?
Sure. I am building it right now. But is there a way to run the tests here?
If you install a unix shell (via cygwin or mingw?), the tests should "just" work. If not, I accept patch. I don't have a windows machine to help make it work, though.
Do these environment variables USERPROFILE and ALLUSERSPROFILE actually exist?
They do exist.However, I have a problem with ASDF's use of ALLUSERSPROFILE, because it is mixed with a pathname "Application Data ..." which may have a different name on a different language -- Windows has the bad habit of naming system folders differently depending on the localization of the operating system. Unfortunately all my copies of Windows are installed with US locale and language so I can not check this.
Well, IIUC, the Windows Registry is precisely where these localizations are stored. But I don't know what authoritative document to consult to be sure.
For the record, what are the values of USERPROFILE and ALLUSERSPROFILE on that machine / account?
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Luck occurs when preparedness meets opportunity.
On Fri, Mar 19, 2010 at 7:51 PM, Faré fahree@gmail.com wrote:
Can you help with the configuration on Windows? What is the ECL equivalent of LispWorks' get-folder-path? Or if there isn't one builtin, how do I read a string entry from the registry? Can you test ASDF with ECL on Windows? Do these environment variables USERPROFILE and ALLUSERSPROFILE actually exist?
I only could make a small set of tests, and only from the ECL sources because this Windows machine is sitting behind a firewall, but I can say ASDF, as it is now integrated in ECL, is working fine on Windows. The paths that are being used are in %TEMP%, which is fine for me but does not look like what was originally intended -- something in Application Data or so.
Juanjo
-
Faré -
Juan Jose Garcia-Ripoll