asdf-devel November 2015

asdf-devel@common-lisp.net

13 participants
16 discussions

12 Nov '15

the export entry in the package was not renamed, it still exports REGISTER-IMMUTABLE-SYSTEM. -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “You can get love only from a free agent whose uniqueness is respected by you, whose freedom is respected by you. It is out of the freedom of the other that this moment of love has happened. Don’t destroy it by trying to possess, by trying to hold, by creating a legal bondage, a marriage. Let the other be free, and remain free yourself. Don’t let anybody else possess you either. To possess or to be possessed, both are ugly. If you are possessed you lose your very soul.” — Osho (1931–1990), 'From Darkness to Light' (1985)

1 1

two ASDF bugs holding back a slick quicklisp experience with projectured
by Attila Lendvai 12 Nov '15

12 Nov '15

dear ASDF maintainer(s), let me draw your attention to two bugs that hold back a simple (ql:quickload :projectured.sdl.test) to work out of the box: https://bugs.launchpad.net/asdf/+bug/1276846 https://bugs.launchpad.net/asdf/+bug/1515372 (the second one is actually not a showstopper once the first one is fixed) could you please update the issues with whatever you can? e.g. it would be nice to know an ETA because if it'll take long then i may look into getting up to speed with ASDF development and fixing them myself. thanks for all your efforts, -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “Anti-intellectualism has been a constant thread winding its way through our political and cultural life, nurtured by the false notion that democracy means that 'my ignorance is just as good as your knowledge.” — Isaac Asimov (1920–1992)

2 1

How do I query what files need to be recompiled?
by Ahmon Dancy 11 Nov '15

11 Nov '15

http://www.cliki.net/asdf has this FAQ: Q: How do I query what files need to be recompiled? A: With ASDF 3, you can (asdf:required-components system :force nil :force-not nil :keep-component 'asdf:cl-source-file :keep-operation 'asdf:compile-op) However, with ASDF 3.1.6, I find that this does not work as advertised: ;;; system1.asd (asdf:defsystem :system1 :serial t :default-component-class asdf:cl-source-file.cl :components ((:file "one") (:file "two") (:file "three"))) cl-user(8): (asdf:compile-system :system1) t cl-user(9): (asdf:required-components :system1 :force nil :force-not nil :keep-component 'asdf:cl-source-file :keep-operation 'asdf:compile-op) (#<asdf/lisp-action:cl-source-file.cl "system1" "one"> #<asdf/lisp-action:cl-source-file.cl "system1" "two"> #<asdf/lisp-action:cl-source-file.cl "system1" "three">) Is there a new way to achieve the same goal?

3 2

Re: How do I query what files need to be recompiled?
by Robert Goldman 11 Nov '15

11 Nov '15

On 11/11/15 Nov 11 -3:03 PM, Andreas Davour wrote: > On Mon, 9 Nov 2015, Robert Goldman wrote: > >> BTW, I have whacked the content of that cliki page. We don't have the >> resources to maintain the cliki pages, the cl.net homepage, and the >> manual. > > I just realized I had assumed I knew what was the SOA, but maybe I > should ask? My apologies, but I have no idea what SOA means in this context. I suspect it's not "Service Oriented Architecture."

1 0

How do I query what files need to be recompiled?
by Ahmon Dancy 11 Nov '15

11 Nov '15

1 0

minimakefile branch merged
by Faré 04 Nov '15

04 Nov '15

TL;DR: the infrastructure to build asdf is now in Lisp; no change to asdf itself. Dear ASDF developers and power-users, I've merged the minimakefile branch into master, with the blessing of Robert. This branch replaces the Makefile and its attendant shell scripts with a Lisp system asdf-tools plus shims to invoke it. It fixes a number of release engineering bugs, in addition to making things generally more robust, better documented and more portable (notably to Windows). As in all big changes, there may be bugs lurking in untested cases. If you use ASDF on anything but Linux/x64 or MacOS X, we'd appreciate it if you ran the ASDF test suite: make -C .../asdf l=clisp test or cd .../asdf ; ./make l=sbcl test See the minimal Makefile for some documentation. The implementations supported are the same as before and/or as by the lisp-invocation library. You can look at the work done with: git diff 4a7c25c 8315d23 (use git diff --stat for a quick summary of which files changed). More details than you care for below: The minimakefile, which has been more than a year in the making and debugging, replaces the Makefile and its attendant shell scripts (notably run-tests.sh) with a system asdf-tools completely written in Lisp, plus small shims to invoke it from the shell (shell scripts and Windows .BAT files, and a minimized Makefile). The branch fixes a number of release engineering bugs: * Some cases of failure to fail during testing are fixed (e.g. test-load). * When a test fail the instructions on how to reproduce it are correct by construction, based on the same expressions used to run the test. * When -no-stop tests are run, a summary of all failures is reported. * Output visible during testing is minimal; the copious dribble remains available in log files. * Support for debian packaging is much improved. * Building and testing on Windows doesn't require Unix tools anymore (cygwin, etc.) * ASDF should be more robust with respect to interference between its ext/ dependencies and any other versions of the same libraries in your CL_SOURCE_REGISTRY. * The infrastructure is better documented. * Probably several other minor bugs. If you read the source code, you may (or then again not) enjoy how we used Lisp to replace make and shell scripting. Most of the code should be straightforward and somewhat documented. It notably uses inferior-shell for invoking shell pipes with suitable string interpolation. And it also uses cl-scripting to manage a notion of failure context, so it can report what failed when running a series of many tests; this is an improvement over what make -k could do. Actually a lot of the residual complexity in deftestcmd is due to the desire to preserve the abitlity to invoke asdf-tools functions from the Makefile as well as more directly by a shell script, or at the SLIME REPL. This lead to implementing a triple calling convention. Most programs would only care about the REPL, or about the REPL and a shell script, not about crazy ways to pass parameters through a Makefile via environment variables. A lot of the bootstrap machinery (make.{sh,.bat}, asdf-tools{,.bat}) is unique to ASDF and its need to mostly not rely on libraries, and (on Windows) not even on any of the Unix toolchain. If you need to distribute a Lisp program in a similar setup, you could copy and modify those scripts; but more realistically, you should probably be using cl-launch instead to produce the binaries you need from source. The doc/Makefile hasn't been replaced with Lisp code yet, but there's no reason it couldn't be — that would be a good exercise for someone who wants to get familiar with this codebase (nudge, nudge). To me, it's also a demonstration of how Lisp can be used to replace shell-scripting, even in constrained situations that make bootstrap tricky. http://fare.livejournal.com/184127.html —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Have the courage to take your own thoughts seriously, for they will shape you. — Albert Einstein

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel November 2015