asdf-devel March 2015

asdf-devel@common-lisp.net

7 participants
8 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

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

os-cond patch pushed and version bumped to 3.1.4.4
by Robert P. Goldman 30 Mar '15

30 Mar '15

This patch passes all the tests for me that were passing before. I'm still not convinced that our patch for Bug 1437480 is ready to go yet, so I have held off that one, to minimize chances we'll need to backtrack.

1 0

Bug in UIOP XDG implementation
by Jason Miller 29 Mar '15

29 Mar '15

Hi, With $XDG_CONFIG_DIRS unset, (uiop:user-configuration-directories) returns only $XDG_CONFIG_HOME/common-lisp/ However, with it set to "/etc/xdg" it returns a list that starts with "/etc/xdg/common-lisp" There are two problems with this: 1) The XDG Base Directory Specification says that "If $XDG_CONFIG_DIRS is either not set or empty, a value equal to /etc/xdg should be used." 2) My understanding of uiop:user-configuration-directories is that it's listed in order of importance, but, from the XDG spec: "The base directory defined by $XDG_CONFIG_HOME is considered more important than any of the base directories defined by $XDG_CONFIG_DIRS" So, what I think is correct is that with $XDG_CONFIG_DIRS set it should return a list starting with $XDG_CONFIG_HOME, followed by the lists in $XDG_CONFIG_DIRS, and with it not set, should return a list of $XDG_CONFIG_HOME followed by /etc/xdg/common-lisp/ Even if that's not correct, due to #1 the current implementation is definitely wrong. Regards, Jason

4 6

Re: manual version
by Robert P. Goldman 24 Mar '15

24 Mar '15

Robert P. Goldman wrote: > DJ wrote: >> Thanks, Robert. >> >> I can find the latest manual, of course, on the asdf website. And I >> know that I am running asdf 3.1.3, which comes with ccl 1.10-r16196. >> (Clozure does not, as far as I can tell, supply a manual.) >> >> I always use the pdf version. Just a personal prefence - I dislike >> html manuals. I also tend to print such manuals out (I know, I know - >> very old school). Anyway, that makes it easy to get out of sync. >> >> What I am thinking is that it might be useful for the manual to >> contain an indication of the version of asdf that it pertains to. As, >> for example in the GNU Make manual, which has on the title page "GNU >> make Version 4.1". Perhaps an indication of this is already there in >> the manual, but I can't spot it. > > I'm not an expert on Texinfo, but I think we can figure out a way to have it get @value{VERSION} from the make scripts, and then we can put that in as a subtitle. > > I'll keep you posted. > OK, I have pushed a patch that will put the version numbers into the ASDF texinfo manual. The makefile for this uses a horrible snippet of perl, but I don't know a substitute. I am open to replacements. good night, all, r

2 1

How do I get the pathname of a CL-SOURCE-FILE
by Christian Schafmeister 23 Mar '15

23 Mar '15

I was given some code to extract all of the source files that a system requires for building. It gave me what you see below: How would I get the full pathname of one of these CL-SOURCE-FILE objects? saw file: #<CL-SOURCE-FILE "cleavir-io" "packages" @0x113ac3518> saw file: #<CL-SOURCE-FILE "cleavir-io" "io" @0x113bacdd8> saw file: #<CL-SOURCE-FILE "cleavir-meter" "packages" @0x1152baf68> saw file: #<CL-SOURCE-FILE "cleavir-meter" "meter" @0x1153b4068> saw file: #<CL-SOURCE-FILE "cleavir-ast" "packages" @0x115d73ba8> saw file: #<CL-SOURCE-FILE "cleavir-ast" "general-purpose-asts" @0x115f98b08> saw file: #<CL-SOURCE-FILE "cleavir-ast" "fixnum-related-asts" @0x115a1a978> saw file: #<CL-SOURCE-FILE "cleavir-ast" "float-related-asts" @0x11549ce78> saw file: #<CL-SOURCE-FILE "cleavir-ast" "cons-related-asts" @0x115027ab8> saw file: #<CL-SOURCE-FILE "cleavir-ast" "standard-object-related-asts" @0x115196838> saw file: #<CL-SOURCE-FILE "cleavir-ast" "array-related-asts" @0x115303658> saw file: #<CL-SOURCE-FILE "cleavir-ast" "graphviz-drawing" @0x1153fdec8> saw file: #<CL-SOURCE-FILE "cleavir-ast" "map-ast" @0x114073f68> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "packages" @0x113d2ffb8> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "clone" @0x113e0ec48> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "replace" @0x113ed67e8> saw file: #<CL-SOURCE-FILE "cleavir-ast-transformations" "hoist-load-time-value" @0x113f9bba8> saw file: #<CL-SOURCE-FILE "cleavir-primop" "packages" @0x1140c5c98> saw file: #<CL-SOURCE-FILE "cleavir-internationalization" "packages" @0x1144b0928> … Deleted another 100 entries ... Christian Schafmeister

3 2

How would I get a list of Common Lisp source files from a system
by Christian Schafmeister 22 Mar '15

22 Mar '15

Hi there, I’d like to get an ordered list of source files for a system that I would normally load with (asdf:load-system :cleavir) I need this because I’d like to compile the Cleavir source code (many interdependent systems) without having to compile and load ASDF. Then I could compile ASDF a lot faster and users would load it. Best, Christian Schafmeister Professor Chemistry Department Temple University

2 4

[Asdf-devel] :homepage :bug-tracker :mailto :long-name :source-control
by Faré 12 Mar '15

12 Mar '15

Shamed by a tweet by @hexstreamsoft, I made a very minimal attempt at documenting the existence since ASDF 2.27 of the :homepage :bug-tracker :mailto :long-name :source-control keywords to defsystem. I will leave for someone else to make real manual entries out of the information. NB: AFAIR, none of the types of these arguments is enforced by ASDF. Good luck! —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Efficiency is doing things right; effectiveness is doing the right things. — Peter Drucker

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel March 2015