asdf-devel April 2015

asdf-devel@common-lisp.net

54 participants
184 discussions

[Asdf-devel] Registering preloaded systems for Quicklisp/ASDF
by Dave Cooper 05 Jun '15

05 Jun '15

Hi, I know this has been discussed, but what is currently the best practice for registering a preloaded system after loading Quicklisp? That is, I have a pre-built image with some Quicklisp/ASDF systems in it, which were loaded through so-called monolithic-fasls (now known as compile-bundles). So the pre-built image doesn’t itself have ASDF or Quicklisp. A downstream user then loads Quicklisp and ASDF (I take steps to ensure that they are loading the matching version of ASDF and Quicklisp as was used to build the image). Now I need to do something to tell Quicklisp and ASDF that certain systems are already loaded in this image, so it won’t try to re-load them as depended-upon systems. In this specific case, I don't want it to try to fetch and reload Gendl when the user does (ql:quickload ...) on an application which :depends-on :gendl (because gendl is already built into this image). asdf/find-system:register-preloaded-system seems like it should be the answer if we’re talking about plain ASDF, because it will prevent ASDF from raising a “missing-component” error for the system in question, if some other system :depends-on it and yet no source code is found. But in my case I can’t guarantee that “no source code is found.” The source might be there in the quicklisp dist directory. So apparently I need something stronger than register-preloaded-system? Or something else? -- My Best, Dave Cooper

3 21

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é 25 Apr '15

25 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

[asdf-devel] errors in ASDF 3.1.0.66
by Anton Vodonosov 08 Apr '15

08 Apr '15

Hello. I've been testing ASDF 3.1.0.66 and unfortunately detected errors: 1. Required method PERFORM not implemented for operation #<STANDARD-CLASS CFFI-GROVEL::PROCESS-OP {599AF195}>, component #<STANDARD-CLASS ASDF/LISP-ACTION:CL-SOURCE-FILE {582A1E35}> 2. New ASDF breaks ECL for Quicklisp. The problem nails down to (require 'sockets). This form works for ECL unless new ASDF is loaded. To reproduce at cl-test-grid.cloud.efficito.com machine: rlwrap ~/lisps/ecl-bin-13.5.1/bin/ecl -norc (require 'sockets) ;;; Loading #P"/home/testgrid/lisps/ecl-bin-13.5.1/lib/ecl-13.5.1/sockets.fas" => ("SB-BSD-SOCKETS" "SOCKETS") ------ compare with: rlwrap ~/lisps/ecl-bin-13.5.1/bin/ecl -norc -load ~/asdf/build/asdf.lisp (require 'sockets) ASDF could not load sockets because In function MAPCAR, the value of the second argument is #P"SYS:SOCKETS.FAS" which is not of the expected type LIST. The report: http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-33.html Best regards, - Anton

2 5

[asdf-devel] READTABLE isolation in ASDF
by Robert P. Goldman 08 Apr '15

08 Apr '15

Attila Lendvai wrote: > this reminds me of the general idea of backwards compatibility: people > who want to live without this feature can chose not to upgrade, as > always. or if they need the new stuff, then they can just patch asdf > locally to disable the enforcement of this. or asdf could even > accommodate this with a defsystem property that can opt a system out > of this otherwise useful isolation. Yes, that is right; please see my earlier email with next steps: 1. The READTABLE isolation feature WILL NOT BE IN THE NEW RELEASE. 2. When/if it is released, the READTABLE isolation feature will only be an *opt-in* strict mode item. Thanks! R

1 0

[asdf-devel] Pushed 3.1.0.50 -- non-release version
by Robert P. Goldman 08 Apr '15

08 Apr '15

Fixed minor warning issue that caused a test problem on ACL. Added a check for BUNDLE-OP on unsupported platforms (ABCL + Mac OSX; ECL + Mac OSX). Cheers, r

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel April 2015