- asdf-devel - mailman3.common-lisp.net

UIOP documentation?
by Jared C. Davis 06 May '15

06 May '15

Hi, The ASDF web site at https://common-lisp.net/project/asdf/ has a very nice manual. Is there similar documentation for UIOP itself? If so, it would be great to add a link to it from the ASDF web page. Cheers, Jared -- Jared C. Davis <jared(a)cs.utexas.edu> 11410 Windermere Meadows Austin, TX 78759 http://www.cs.utexas.edu/users/jared/

4 8

Re: UIOP documentation?
by Robert P. Goldman 06 May '15

06 May '15

Faré wrote: >> > I looked at the link to the version that's supposed to have good docs: >> > >> > http://bimib.disco.unimib.it/people/Marco.Antoniotti/Projects/CL/HELAMBDAP/… >> > >> > AFAICT it shows only the docs for BACKWARD-INTERFACE, and maybe not even >> > all of those. >> > > Oh! It has more documentation than that, but depending on your screen > resolution, it can be totally unobvious that you can scroll the > package pane. Le sigh. I tried to document that in the uiop/README.md, > but that needs also be told in the index.html. > That is a *horrible* left pane. As you say, there is no visible affordance, indicating an ability to scroll that pane. The pane also has no border, which hides the fact that, instead of filling the frame with package entries, it takes only 25% of the height of the pane. I guess that's because it wants to put the package interface below the package menu. A border around those frames would help the user understand how the layout is to be used. Also, one I have selected one package, clicking on another in the sidebar takes a *very* long time (so long that I thought it was not going to update at all) to update the main frame.

1 0

Fwd: UIOP documentation?
by Faré 06 May '15

06 May '15

[I got notification on the below message being rejected because the quickdocs url is blacklisted by http://lookup.uribl.com/ !? I stripped said url so the message makes it to the list.] On Tue, May 5, 2015 at 8:35 PM, Robert P. Goldman <rpgoldman(a)sift.net> wrote: > Faré wrote: >> UIOP has no manual, but it has a README.md which guides you through >> the code and links to a website with interactive help as extracted >> from docstrings. I included a direct link on the ASDF webpage in >> doc/index.html — but only the maintainer has the rights to update the >> actual webpage. > > I looked at the link to the version that's supposed to have good docs: > > http://bimib.disco.unimib.it/people/Marco.Antoniotti/Projects/CL/HELAMBDAP/… > > AFAICT it shows only the docs for BACKWARD-INTERFACE, and maybe not even > all of those. > Oh! It has more documentation than that, but depending on your screen resolution, it can be totally unobvious that you can scroll the package pane. Le sigh. I tried to document that in the uiop/README.md, but that needs also be told in the index.html. > As you report, the quickdocs page, http://....org/uiop/api, only > provides docs for UIOP/PACKAGE. > > Also, for some reason these aren't clickable links in the README.md: > they come through as preformatted text, instead. > OK, I was assuming ReST-style magic. I pushed a fix to that. Actually, I made a few passes over both README.md and uiop/README.md. I also merged into the minimakefile branch. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org An anarchist is a man who is careful to always use pedestrian crossings, because he utterly detests talking with policemen. — Georges Brassens

1 0

Lisp scripting
by Faré 06 May '15

06 May '15

>> * minimakefile. Can we get this in before we cut 3.2? Actually, >> merging before 3.1.5 would allow to test the release functions before >> we release an actual 3.2. > > The last time I was working with minimakefile it was still at the state > where every time I tried a new command, I would get a new error. I got > tired of this and gave up. I'll try again, but this one is your cause: > I don't care if CL never becomes a scripting language. I'm willing to > run with it if it works, but if it gives me grief, I'll give up again. > Indeed, it's my pet topic; I apologize for the bugs, and I am grateful to you for bearing with me thus far. Obviously, there was a big gap from "(seems to) works for me" to "works robustly for everyone"; but this time, I believe the bugs have been shaken, and the new test system is superior in many ways, including not drowning the screen in so much noise, providing better replay information on error, supporting one more Lisp (clasp), an interactive list of commands, ability to invoke tests from the SLIME REPL, etc. Please try again, and merge into master if satisfactory. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org When one realises one is asleep, at that moment one is already half-awake. ― Pyotr Uspensky

1 0

ASDF configuration and cache
by Faré 29 Apr '15

29 Apr '15

Dear Lispers, The most significant bit for this email is: DO YOU HAVE A source-registry.conf ON WINDOWS? or do you know someone who has? If so, please contact me, either on this list or in private, because I'm considering a backward-incompatible change in its location. (If you use or don't use source-registry.conf on Linux, that can be an interesting data point, too, for comparison of impact.) If not, then there will be no negative impact to the proposed change. I'm having a hard time finding an affected Windows user who cares, which may be a sign that there is none and I can proceed, or that I'm simply disconnected from the user base. Right now, ASDF tries to do things kind-of-the-windows-way, where "common-lisp/" replaces the vendor/app/ path component. Thus, it puts its configuration in %LOCALAPPDATA%/common-lisp/config/ its cache in %LOCALAPPDATA%/common-lisp/cache/ and for source code in %LOCALAPPDATA%/common-lisp/source/ I'm considering dropping the Windows special-casing, and offering the XDG model on all platforms, including Windows. That would mean the configuration would instead go in %LOCALAPPDATA%/Configuration/common-lisp/ and the cache in %LOCALAPPDATA%/Cache/common-lisp/ while source code remains in %LOCALAPPDATA%/common-lisp/source/ with these the conceptual mapping XDG_CONFIG_HOME=%LOCALAPPDATA%/Configuration instead of ~/.config/ and XDG_DATA_HOME=%LOCALAPPDATA%/ instead of ~/.local/share/ and XDG_CACHE_HOME=%LOCALAPPDATA%/Cache/ instead of ~/.cache/ The advantage of the change would be that ASDF would offer to Lisp programs a uniform XDG view on all platforms, which has some costs in terms of being slightly unfamiliar to Windows users and a transition issue for some of them, but going forward allows for: * all files can be redirected on all platforms using the XDG_CONFIG_HOME environment variable and its siblings. * the same directory concepts on all platforms. * slightly simpler code for the ASDF maintainers, and much simpler documentation: no need to explain vast subtle discrepancies from one platform to the next. * the ability to handle backup of configuration and skipping of backup of cache in a simpler way than with the usual Windows semi-convention. * a more uniform API for the Lisp programmer The main disadvantage is that this setup is somewhat different from current conventions on Windows. On the other hand, conventions on Unix were similar to those on Windows some ten years back, and have improved thanks to XDG -- maybe they can evolve for the better on Windows, too, in the next ten years. To me, the big issue is with transition for people who currently use a source-registry.conf on Windows. Since ASDF will start to look for it at a different location, their setup will need to be amended when they upgrade ASDF. What do you think? Does anyone care at all? Does anyone actually have a common-lisp/config/source-registry.conf file and be confused if the location changes? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Corollaries to the Law of Bitur-Camember: The political process destroys the value of all known resources that are up for grabs. The socialist process of systematically denying legitimacy to property rights applies the political process universally and destroys the value of all available resources.

2 6

manual version
by DJ 29 Apr '15

29 Apr '15

How do I know whether the asdf manual I am looking at matches the version of asdf I have installed? - DJ -

4 5

default method for test-system?
by Faré 26 Apr '15

26 Apr '15

Dear ASDF users, what about this default method (or something similar) for test-op? (defmethod perform ((o test-op) (s system)) (loop :with name = (coerce-name s) :for suffix :in '("" "/test" "-test") :for test-system-name = (strcat name suffix) :for test-system = (find-system test-system-name nil) :when test-system :do (load-system test-system) ;; Would be string-upcase, if not to accommodate for "modern" syntax. ;; UIOP probably needs to offer a standard way to abstract over ;; the string-upcase vs string-downcase vs neither default. (flet ((symbol-namify (x) (string (safe-read-from-string x)))) (if-let (test-suite (find-symbol* '#:test-suite (symbol-namify test-system-name) nil)) (return (funcall test-suite)))) :finally (error "No tests found for system ~A" name))) —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If being against something is a phobia, then being for is mania. Peace and understanding through slurs of mental illness. Homomania, islamomania, etc.

2 3

asdf, poiu, etc.
by Faré 08 Apr '15

08 Apr '15

[This is a test of the new asdf-devel mailing-list.] While I'm at it, may I attract your attention to POIU? It now has a deterministic mode, so it's reasonably usable in your buildbots. Several tweaks since release 2.33, but nothing really new since then. If your implementation hasn't upgraded to 2.33 yet, now is a good time. —♯ƒ Fascists divide in two categories: the fascists and the anti-fascists — Ennio Flaiano

2 1

[asdf-devel] Fwd: ASDF testing for LWW
by Dave Cooper 08 Apr '15

08 Apr '15

FYI It looks like some more command line escaping tweaks are needed for LWW. I'm on an outing today and will be able to run tests tonight with the latest commit. ---------- Forwarded message ---------- From: *Fabrice Popineau* Date: Sunday, October 20, 2013 Subject: ASDF testing for LWW To: Dave Cooper <david.cooper(a)genworks.com> The test suite fails by me with LWW : here at ligne 91 of run-tests.sh if DO $bcmd $eval "'(#.(load(string'|script-support.lisp|))#.(asdf-test::load-asdf)#.(asdf-test::frob-packages)#.(asdf-test::with-test()(load(string'|$i|))))" ; then $ ./run1 make[1]: Entering directory `/c/temp/asdf-test/asdf-windows' PWD=/c/temp/asdf-test/asdf-windows/test !C:=C:\Temp\asdf-test ASDF_TEST_LISPS=lispworks OLDPWD=/c/temp/asdf-test/asdf-windows /c/Local/Lispworks/lw-console.exe -siteinit - -init - -eval "(or #.(load(string\ `|test/script-support.lisp|))#.(asdf-test::compile-asdf-script))" LispWorks(R) (for the Windows(R) operating system) Copyright (C) 1987-2012 LispWorks Ltd. All rights reserved. Version 6.1.1 Saved by Fabrice as lw-console, at 20 Oct 2013 11:59 User Fabrice on ALIMANTADO Error: The file "testscript-support.lisp" does not exist. 1 (continue) Try loading testscript-support.lisp again. 2 Give up loading testscript-support.lisp. 3 Try loading another file instead of testscript-support.lisp. 4 (abort) Abort initialization. 5 Continue to top-level loop. I'm not that familiar with path syntax in CL (I'm using it at its minimum and always checking) so why is there this (string`|path|) ? Case-sensitivity ? Or ? Fabrice 2013/10/20 Dave Cooper <david.cooper(a)genworks.com <javascript:_e({}, 'cvml', 'david.cooper(a)genworks.com');>> > > > Have you been waiting for the noise to settle down on asdf-devel? I think > it's safe to go ahead and try the tests on LWW now. > > I've attached a "run" script which should be pretty much ready to go for > LWW, all you have to do is fill in your lwconsole.exe location where it > says: > > "Fill in for location of your LWW console exe:" > > You have to have "make" and "rsync" installed in your MSYS (or cygwin) > (rsync is probably not strictly necessary; for running on a single OS you > can just replace $asdf with the original "asdf/" directory). > > I'll be away from the office tomorrow (Sunday) but if you feel like giving > it a go on Sunday and run into any issues, feel free to give me a call on > skype or +1 248-330-2979. > > > > On Thu, Oct 17, 2013 at 5:50 PM, Fabrice Popineau < > fabrice.popineau(a)supelec.fr <javascript:_e({}, 'cvml', > 'fabrice.popineau(a)supelec.fr');>> wrote: > >> Ok, I'll reply about it on Saturday. >> >> Best regards, >> >> Fabrice >> >> >> 2013/10/17 Dave Cooper <david.cooper(a)genworks.com <javascript:_e({}, >> 'cvml', 'david.cooper(a)genworks.com');>> >> >>> >>> Basic instructions to run the tests: >>>> >>>> 1. Establish a directory to be the root of your testing area. >>>> 2. cd to this directory. >>>> 3. git clone git://common-lisp.net/projects/asdf/asdf.git >>>> 4. put the attached script into this directory >>>> >>> >>> >>> To be clear, by "this directory" I mean the _current_ directory, not the >>> asdf/ subdirectory which was newly created by the git clone. So the "run" >>> script and your pwd should both be in the parent of the asdf/ subdirectory >>> created by the git clone. >>> >>> >>> >>>> 5. edit the script to point to your LWW console image >>>> 6. ./run >>>> 7. observe the output in ./asdf/build/results/lispworks.text >>>> 8. If interesting, report the output to asdf-devel(a)common-lisp.net<javascript:_e({}, 'cvml', 'asdf-devel(a)common-lisp.net');> >>>> >>> > > > > -- > My Best, > > Dave Cooper, Genworks Support > david.cooper(a)genworks.com <javascript:_e({}, 'cvml', > 'david.cooper(a)genworks.com');>, dave.genworks.com(skype) > > -- Fabrice Popineau ----------------------------- SUPELEC Département Informatique 3, rue Joliot Curie 91192 Gif/Yvette Cedex Tel direct : +33 (0) 169851950 Standard : +33 (0) 169851212 ------------------------------ -- My Best, Dave Cooper, Genworks Support david.cooper(a)genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

3 4

[asdf-devel] Re: Preview of my ASDF3 article.
by Faré 08 Apr '15

08 Apr '15

I refactored that paper by making separate "short" (8 pages) and "extended" versions (24 pages), thereby fitting the limit while being able to say everything I had on my heart. I submitted the short PDF to ELS 2014. I also moved the papers to a more permanent location. [Source] https://github.com/fare/asdf3-2013/blob/master/asdf3-2014.scrbl [Extended HTML] http://fare.tunes.org/files/asdf3/asdf3-2014.html [Extended PDF] http://fare.tunes.org/files/asdf3/asdf3-2014.pdf [Short HTML] http://fare.tunes.org/files/asdf3/asdf3-els2014.html [Short PDF] http://fare.tunes.org/files/asdf3/asdf3-els2014.pdf I still need to extend the section on pathnames some more, but the short version should be stable, and even the extended version. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The worst thing that can happen to a good cause is, not to be skillfully attacked, but to be ineptly defended. — F. Bastiat

2 1