asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

RFS: cl-asdf/3.3.1 - Another System Definition Facility
by Kambiz Darabi 15 Nov '17

15 Nov '17

Hello, I have packaged the new upstream release 3.3.1 of the Common Lisp ASDF software and looking for a sponsor: Package name : cl-asdf Version : 2:3.3.1-1 Upstream Author : Robert P. Goldman <rpgoldman(a)sift.info> URL : https://common-lisp.net/project/asdf/ License : Expat Section : lisp The cl-asdf source package builds this binary package: cl-asdf - Another System Definition Facility The package appears to be lintian (2.5.59) clean, apart from: - testsuite-autopkgtest-missing which is in level 'info'. I will try to fix it for the next release after reading the documentation. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/cl-asdf Alternatively, you can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/cl-asdf/cl-asdf_3.3.1-1.dsc Changes since the last upload: New upstream release 3.3.1: * UIOP compatibility fix: Introduced new replacement "timestamp" comparison functions, because of inadvertent change in the API. Functions that are compatible with the old semantics are retained as "stamp" comparison functions, but will eventually be deprecated. * Upgrade fix: Upgrade from 3.2.1 needed repair. * Syntax manipulation: Fix for bugs that could be introduced when the default readtable was manipulated during the loading of a defsystem-depends-on system. * Tests: tests for new capabilities and bugs * Documentation: a number of improvements and clarifications. Thank you Kambiz Darabi -- m-creations gmbh Acker 2 55116 Mainz Germany

2 1

Can not upgrade to ASDF 3.3.0
by Vince 07 Nov '17

07 Nov '17

Hello lispers ! I wanted to install the latest ASDF 3.3.0 but got a bunch of errors. I extracted the tar into quicklisp's local-projects and loaded the installation script: (load #p"~/quicklisp/local-projects/asdf/tools/install-asdf.lisp") While evaluating the form starting at line 22, column 0 of #P"/home/vince/quicklisp/local-projects/asdf/tools/load-asdf.lisp": While evaluating the form starting at line 46, column 0 of #P"~/quicklisp/local-projects/asdf/tools/install-asdf.lisp": stacktrace: When attempting to set the slot's value to NIL (SETF of SLOT-VALUE), the slot ASDF/FORCING:FORCED is missing from the object #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}>. [Condition of type SIMPLE-ERROR] Restarts: 0: [RETRY] Retry ASDF operation. 1: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 2: [RETRY] Retry EVAL of current toplevel form. 3: [CONTINUE] Ignore error and continue loading file "/home/vince/quicklisp/local-projects/asdf/tools/load-asdf.lisp". 4: [ABORT] Abort loading file "/home/vince/quicklisp/local-projects/asdf/tools/load-asdf.lisp". 5: [RETRY] Retry EVAL of current toplevel form. --more-- Backtrace: 0: ((:METHOD SLOT-MISSING (T T T T)) #<unused argument> #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}> ASDF/FORCING:FORCED SETF NIL) [fast-method] 1: ((LAMBDA (SB-PCL::NEW-VALUE SB-PCL::OBJECT) :IN SB-PCL::SLOT-MISSING-INFO) NIL #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}>) 2: ((:METHOD INITIALIZE-INSTANCE :AFTER (ASDF/PLAN:PLAN-TRAVERSAL)) #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}> :FORCE NIL :FORCE-NOT NIL :SYSTEM NIL) [fast-method] 3: ((SB-PCL::EMF INITIALIZE-INSTANCE) #<unused argument> #<unused argument> #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}> :FORCING #<ASDF/SESSION:FORCING :PERFORMABLE-P T>) 4: ((:METHOD MAKE-INSTANCE (CLASS)) #<STANDARD-CLASS ASDF/PLAN:SEQUENTIAL-PLAN> :FORCING #<ASDF/SESSION:FORCING :PERFORMABLE-P T>) [fast-method] 5: ((LAMBDA NIL :IN ASDF/PLAN:MAKE-PLAN)) 6: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION ASDF/COMPONENT:COMPONENT)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "asdf"> :PLAN-CLASS NIL :PLAN-OPTIONS NIL) [fast-method] 7: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "asdf">) 8: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 9: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "asdf">) [fast-method] 10: ((LAMBDA NIL :IN ASDF/SYSTEM:FIND-SYSTEM)) 11: (ASDF/SESSION:CONSULT-ASDF-CACHE (ASDF/SYSTEM:FIND-SYSTEM "asdf") #<CLOSURE (LAMBDA NIL :IN ASDF/SYSTEM:FIND-SYSTEM) {1006E7BB6B}>) 12: ((:METHOD ASDF/COMPONENT:FIND-COMPONENT (STRING T)) "asdf" NIL :REGISTERED NIL) [fast-method] 13: ((:METHOD ASDF/OPERATE:OPERATE (SYMBOL T)) ASDF/LISP-ACTION:LOAD-OP :ASDF :VERBOSE NIL) [fast-method] 14: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> ASDF/LISP-ACTION:LOAD-OP :ASDF :VERBOSE NIL) 15: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 16: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/LISP-ACTION:LOAD-OP :ASDF :VERBOSE NIL) [fast-method] 17: (ASDF/OPERATE:LOAD-SYSTEM :ASDF :VERBOSE NIL) 18: (ASDF/UPGRADE:UPGRADE-ASDF) 19: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) --more-- To Continue a few times does not help. Any hints on that ? I'm on SBCL 1.3.19 and ASDF 3.2.1. Now the reason I want to do this is that it looks like my last solution to build an executable with ECL (I'd like to build a smaller executable than with SBCL). I was hit by the fact that ASDF did not ship make-build, which is the build procedure documented by ECL. Other options like program-op are not really documented either. I explained and keep track of the issue here: https://stackoverflow.com/questions/46520876/building-an-executable-with-ec… :) Regards, Vincent

4 3

Introducing Seed, an interactive software environment built on ASDF
by Andrew Sengul 05 Nov '17

05 Nov '17

Hi everyone, I've created a new software environment based on Common Lisp and it'd be great to get your feedback. Called Seed, this system can be used to create Lisp programs and interact with them in many ways. It's a bit like a web-based IDE, but unlike most IDEs, it uses a visual programming language as its foundation. Seed displays Lisp code in the form of an interactive tree grid. It's possible to create customized interface elements within the tree grid; these elements are converted into Lisp code for compilation. A simple example is a color picker for use choosing colors inside a HTML template. Drop-downs and toggle switches are also easy to insert, and these elements can be composited to create more sophisticated interfaces. And unlike Emacs and other editors that are designed around text files, Seed is designed around editing ASDF systems. When using Seed, the top-level interactive elements are called "systems" - contrast to "buffers" in Emacs. Each Seed system is an ASDF system with particular extensions. Specifically, Seed systems all have a .seed file in their source directory that defines their behavior within the scope of the Seed environment. Check out this video to see Seed in action and a brief tutorial: https://vimeo.com/237947324 This is a slide deck that goes into further detail: https://www.dropbox.com/s/ssjd05bmrfnzg5e/SeedPresentationTechnical.pdf?dl=0 I don't know if Seed is the first general-purpose visual programming environment, but I'm sure its paradigm is among the most flexible. It is implemented as a Web application, with each atom and form within a Lisp program represented by a module manifested using the React framework for JavaScript. Because Seed's interface is implemented in React, the entire ecosystem of React components can be brought to bear when building custom software interfaces. Ready to try Seed out yourself? It's free software and the repo is here: https://github.com/phantomics/seed The installation instructions start here: https://github.com/phantomics/seed#the-first-step-installing-and-running-se… Read the usage tutorial here: https://github.com/phantomics/seed/wiki/Introductory-Tutorial So far, only SBCL has been tested. This is alpha software and you will encounter bugs aplenty. I envision Seed as something that could one day encompass most of the desktop productivity functions that people now use office apps for. The data-driven nature of the interface will make it easy to mash up and modify these tools to design custom workflows.With Lisp's homoiconicity it may even be possible to develop machine learning algorithms to tailor Seed systems to the jobs they're intended to do. Emacs has always been seen as the flagship of Lisp-based environments, but because of its byzantine interface and its tight coupling to the text buffer as the main interactive unit, I can't see a future where Emacs is usable by regular people for desktop productivity. I think Seed may be able to get there. Let me know what you think of Seed, particularly as an ASDF use case. Best, Andrew Sengul

2 6

uiop non-problems
by Faré 21 Oct '17

21 Oct '17

Dear Xach, I saw your blog post: http://lispblog.xach.com/post/166534341423/uiop-330-problems There are no comments on your blog, so I'll just clarify things on the asdf-devel list: * The situation you describe is not at all a problem specific to uiop 3.3.0, or any other version of uiop. uiop.asd hasn't changed since 3.2.0, and the "issue" already existed before, and exists when there is no uiop.asd available but only the builtin uiop. * The situation you describe, where some libraries are loaded multiple times, is a bug in ASDF, that was fixed in 3.3.0 --- actually, fixing this situation and other related situations was the very reason why I had to teach ASDF about build phases, which lead to the big refactoring done in 3.3.0. * All build systems have to either face the issue of build system extension, or put their head in the sand and do the wrong thing. At least ASDF 3.3.0 does the right thing now, whereas earlier versions put their head in the sand as far as that issue was concerned. (I also know that Bazel has a proper solution, though it involves using a non-extensible DSL for extensions). * At least in that case, the issue is not too bad: just some system recompiled, that will also cause more recompilation the next time, but don't cause an infinite loop, just a waste of CPU time. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org In Italia i fascisti si dividono in due categorie: i fascisti e gli antifascisti. — Ennio Flaiano

3 4

Re: Warning: Computing just-done stamp in plan NIL for action
by Stas Boukarev 18 Oct '17

18 Oct '17

ASDF keeps inventing good reasons all the time... On Wed, Oct 18, 2017 at 7:43 PM Faré <fahree(a)gmail.com> wrote: > Oh, is it a case where you're insisting on using a secondary system > name that doesn't follow the convention B/A when the primary system is > B ? That might explain it. There is also a warning against such a > thing, and for good reason. > > —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• > http://fare.tunes.org > Doing well is the result of doing good. That's what capitalism is all > about. > — Ralph Waldo Emerson (1803–1882) > > > On Wed, Oct 18, 2017 at 12:15 PM, Stas Boukarev <stassats(a)gmail.com> > wrote: > > cat b.asd > > (defsystem A) > > > > (defsystem B > > :depends-on (A)) > > > > (asdf:load-system 'b) is enough to trigger it. > > > > On Wed, Oct 18, 2017 at 6:51 PM Faré <fahree(a)gmail.com> wrote: > >> > >> See section 4 of the ASDF 3.3 paper at ILC 2017 for a quick overview: > >> https://github.com/fare/asdf2017 > >> > >> To support proper phase separation, ASDF has a new operation, > >> define-op, that tracks the dependencies of loading a .asd file (i.e. > >> other systems you operate on, e.g., via load-system or > >> defsystem-depends-on, etc.) > >> > >> I don't know exactly what is your system A and how you use it, but > >> apparently it's unhappy about depending on the primary system for > >> define-op yet being earlier in the .asd file, so the other system > >> hasn't been defined yet. > >> > >> Maybe ASDF should refrain from registering a dependency here between > >> sibling systems. Or not. It was quite subtle to debug about a year > >> ago, and it fell out of my working cache. > >> > >> Is there anything special you do between A and B except a :depends-on ? > >> > >> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• > >> http://fare.tunes.org > >> You think war is economically beneficial? Then why share those benefits > >> with > >> dirty foreigners? Let's have a civil war — A war we're sure to win! > >> > >> > >> On Wed, Oct 18, 2017 at 11:34 AM, Stas Boukarev <stassats(a)gmail.com> > >> wrote: > >> > It’s a regular depends-on, but why did it work before without > problems? > >> > > >> > On Wed, 18 Oct 2017 at 18:32 Faré <fahree(a)gmail.com> wrote: > >> >> > >> >> On Wed, Oct 18, 2017 at 11:25 AM, Stas Boukarev <stassats(a)gmail.com> > >> >> wrote: > >> >> > B is primary, but A has to be loaded before it. It precedes B, and > B > >> >> > depends > >> >> > on it. > >> >> > > >> >> If it's a regular :depends-on, then B should be able to appear before > >> >> A, and that should actually work better. > >> >> > >> >> If it's a :defsystem-depends-on, it used to be that A must be before > >> >> B, but the new situation is that they have to be in separate files > for > >> >> define-op to work at all. > >> >> > >> >> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• > >> >> http://fare.tunes.org > >> >> For ultimately, the most visible trait of a just man is to have no > >> >> desire > >> >> at all to rule others, and only want to rule himself. This decides > >> >> everything. In other words, the worst people will rule. — Alain > >> >> > >> >> > >> >> > >> >> > On Wed, Oct 18, 2017 at 6:23 PM Faré <fahree(a)gmail.com> wrote: > >> >> >> > >> >> >> On Wed, Oct 18, 2017 at 11:13 AM, Stas Boukarev < > stassats(a)gmail.com> > >> >> >> wrote: > >> >> >> > Looks like this happens because I have two systems in B.asd, A > and > >> >> >> > B, > >> >> >> > and B > >> >> >> > depends on A. > >> >> >> Maybe changing the order of the two systems will help. > >> >> >> Which is primary? Which depends on the other? > >> >> >> > >> >> >> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• > >> >> >> http://fare.tunes.org > >> >> >> All honest people are welcome to come and live here. > >> >> >> All dishonest people are welcome to come and die here. > >> >> >> — Libertarian Open-Borders, Open-Skulls Policy >

2 4

Warning: Computing just-done stamp in plan NIL for action
by Stas Boukarev 18 Oct '17

18 Oct '17

More new warnings from ASDF 3.3, this time I have no idea what it means. WARNING: Computing just-done stamp in plan NIL for action (ASDF/LISP-ACTION:LOAD-OP "system"), but dependency (ASDF/FIND-SYSTEM:DEFINE-OP "system") wasn't done yet! The .asd file is not public, but it looks perfectly normal without using any complicated features.

4 12

monolithic-concatenate-source-op misses a few dependencies
by Ben Vulpes 17 Oct '17

17 Oct '17

On SBCL 1.3.11, when producing a monolithic source concatenation with the library "Postmodern", asdf produces a file that needs a Lisp image to need manual calls to (require :usocket) and (require :md5) in order to load completely. Given: concatenatrix.asd as: (asdf:defsystem :concatenatrix :build-operation monolithic-concatenate-source-op :build-pathname "build/full-concatenation" :depends-on (:postmodern) :components ((:file "concatenatrix"))) concatenatrix.lisp as: (defpackage :concatenatrix (:use :cl :postmodern)) (in-package :concatenatrix) (defun wat (it) (format t "~A~%" it)) Concatenated sources produced with: (asdf:make :concatenatrix) Loading tested with: sbcl --noinform --disable-debugger --load build/full-concatenation.lisp Produces: Unhandled SB-C::INPUT-ERROR-IN-LOAD in thread #<SB-THREAD:THREAD "main thread" RUNNING {10027FE873}>: READ error during LOAD: Package SB-ROTATE-BYTE does not exist. Line: 221, Column: 29, File-Position: 8706 Stream: #<SB-INT:FORM-TRACKING-STREAM for "file /home/b/quicklisp/local-projects/concatenatrix/build/full-concatenation.lisp" {1003CFCA03}> Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {10027FE873}> 0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<SB-C::INPUT-ERROR-IN-LOAD {1004014AC3}> #<unavailable argument>) 1: (SB-DEBUG::RUN-HOOK SB-EXT:*INVOKE-DEBUGGER-HOOK* #<SB-C::INPUT-ERROR-IN-LOAD {1004014AC3}>) 2: (INVOKE-DEBUGGER #<SB-C::INPUT-ERROR-IN-LOAD {1004014AC3}>) 3: (ERROR #<SB-C::INPUT-ERROR-IN-LOAD {1004014AC3}>) 4: (SB-C:COMPILER-ERROR SB-C::INPUT-ERROR-IN-LOAD :CONDITION #<SB-INT:SIMPLE-READER-PACKAGE-ERROR "Package ~A does not exist." {10040149E3}> :STREAM #<SB-INT:FORM-TRACKING-STREAM for "file /home/b/quicklisp/local-projects/concatenatrix/build/full-concatenation.lisp" {1003CFCA03}>) 5: (SB-C::%DO-FORMS-FROM-INFO #<CLOSURE (LAMBDA (SB-KERNEL:FORM &KEY :CURRENT-INDEX &ALLOW-OTHER-KEYS) :IN SB-INT:LOAD-AS-SOURCE) {1003D004FB}> #<SB-C::SOURCE-INFO {1003D004B3}> SB-C::INPUT-ERROR-IN-LOAD) 6: (SB-INT:LOAD-AS-SOURCE #<SB-INT:FORM-TRACKING-STREAM for "file /home/b/quicklisp/local-projects/concatenatrix/build/full-concatenation.lisp" {1003CFCA03}> :VERBOSE NIL :PRINT NIL :CONTEXT "loading") 7: ((FLET SB-FASL::LOAD-STREAM :IN LOAD) #<SB-INT:FORM-TRACKING-STREAM for "file /home/b/quicklisp/local-projects/concatenatrix/build/full-concatenation.lisp" {1003CFCA03}> NIL) 8: (LOAD #P"build/full-concatenation.lisp" :VERBOSE NIL :PRINT NIL :IF-DOES-NOT-EXIST T :EXTERNAL-FORMAT :DEFAULT) 9: (SB-IMPL::PROCESS-EVAL/LOAD-OPTIONS ((:LOAD . "build/full-concatenation.lisp"))) 10: (SB-IMPL::TOPLEVEL-INIT) 11: ((FLET #:WITHOUT-INTERRUPTS-BODY-90 :IN SB-EXT:SAVE-LISP-AND-DIE)) 12: ((LABELS SB-IMPL::RESTART-LISP :IN SB-EXT:SAVE-LISP-AND-DIE)) There is another complaint about usocket, which is confusing, as cl-postgres explicitly doesn't require usocket on sbcl by my read ( http://marijnhaverbeke.nl/git/?p=postmodern;a=blob;f=cl-postgres.asd;h=683e… ). Loading is resolved by requiring both libraries in question, as: sbcl --eval "(require :md5)" --eval "(require :usocket)" --load build/full-concatenation.lisp Yours, Benjamin

3 5

asdf defsystem worked in 3.2.1 but not 3.3.0
by Raymond Toy 15 Oct '17

15 Oct '17

The following defsystem worked in asdf 3.2.1 but no longer works in 3.3.0. The error message doesn't really help in figuring out what's circular. And I just can't see what's circular. The system: (asdf:defsystem :pcl-test :pathname "pcl/" :components ((:file "pkg") #+gerds-pcl (:file "ctor" :depends-on ("pkg")) (:file "defclass" :depends-on ("pkg")) (:file "make-instance" :depends-on ("pkg" #+gerds-pcl "ctor")) (:file "reinitialize-instance" :depends-on ("pkg" "make-instance")) (:file "slot-value" :depends-on ("pkg" "make-instance")) (:file "slot-boundp" :depends-on ("pkg" "make-instance")) (:file "slot-missing" :depends-on ("pkg" "make-instance")) (:file "slot-accessors" :depends-on ("pkg" "make-instance")) (:file "slot-type" :depends-on ("pkg" "slot-value")) (:file "inline-access" :depends-on ("pkg" "slot-type")) (:file "method-combination" :depends-on ("pkg")) (:file "pv" :depends-on ("pkg")) (:file "defgeneric" :depends-on ("pkg")) (:file "defmethod" :depends-on ("pkg")) (:file "find-method" :depends-on ("pkg")) (:file "methods" :depends-on ("pkg")))) -- Ray

3 5

syntax-control
by Faré 14 Oct '17

14 Oct '17

Due to the readtable bug in ASDF 3.3.0 I updated the "syntax-control" branch that for the last three years was supposed to solve all readtable bugs when building with ASDF. I merged 3.3.0.1 into the branch, but the branch itself is not ready for merging into master: it does either too much or too little, and must be either completed or simplified. I think it stands a better chance of bieng merged soon if it is simplified, so I re-read and re-wrote the documentation for what this branch should be doing, and detailed a "Proposal 1" for minimal changes to ASDF that would go a long way towards bringing sanity in builds of software that modify the syntax. I sollicit your feedback: https://gitlab.common-lisp.net/asdf/asdf/blob/syntax-control/doc/syntax-con… —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Problem of the day: finding suction cups that don't suck.

2 1

Debian package: signing-key.asc
by Kambiz Darabi 13 Oct '17

13 Oct '17

Hello, there are questions from the Debian dev who helps publishing the package about the signing key which is in the debian/ subtree. Can someone please comment? Thank you Kambiz ----- Forwarded Message ----- From: "Sébastien Villemot" <sebastien(a)debian.org> To: "Kambiz Darabi" <darabi(a)m-creations.com> Cc: 878167(a)bugs.debian.org Sent: Friday, 13 October, 2017 5:07:45 PM Subject: Re: Bug#878167: RFS: cl-asdf/3.3.0 - Another System Definition Facility Also, there is a GPG key under debian/upstream/signing-key.asc, but I see no signature on upstream website (https://common-lisp.net/project/asdf/archives/). Am I missing something? Or should the key be removed? Thanks, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org

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