asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] 3.0.3 release plans
by Robert P. Goldman 08 Apr '15

08 Apr '15

I was hoping to release this past week, but was unable to get further testing done. Before releasing, I try to test a number of large systems that we use here at SIFT with the latest ASDF. This provides a real world add-on to the test suite. Unfortunately, I have not had a chance to make this test. I hope to do so in the next couple of days. That should either reveal bugs, or lead to an immediate release of 3.0.3. It would be great if the quicklisp issues could be resolved satisfactorily in time for 3.0.3. Best, r

3 3

[asdf-devel] Fixing asdf-system-connections
by Liam Healy 08 Apr '15

08 Apr '15

I am using asdf-system-connections and notice a glitch in its design. As the original author no longer maintains it, I'm try to fix this myself. This system is designed to allow the loading of a connected system (say "A") automatically when two or more dependent systems (say "B" and "C") are loaded. The problem I'm encountering is that when another system (say "D") is defined to depend on B and C, then A is not loaded until after D is done loading, but D may need the definitions in A. asdf-system-connections defines a function load-connected-systems which does the work of loading the connected system definitions, but this is called from a new #'operate :after method which apparently doesn't get called until A is done loading. I am looking for a place from which to call load-connected-systems that will trigger its call as soon as it's able, i.e., immediately once both "B" and "C" are loaded. I'm not familiar with the internals of ASDF and wonder if someone can guide me to a good place to define this. Thanks, Liam

2 1

[asdf-devel] ASDF 3.0.1
by Faré 08 Apr '15

08 Apr '15

Dear Lisp hackers, ASDF 3.0.0 was decidedly short-lived. Longer live ASDF 3.0.1! An undocumented feature of version-satisfies, since the early days of ASDF 1, was that it would reject a component that didn't exactly match the specified major version as well as otherwise be same or newer as specified version. Of course, this broke quicklisp's check for a newer ASDF when ASDF went from major version 2 to major version 3. Since the feature was undocumented, and that users don't seem to ask for it, whereas many power users are inconvenienced by it, I just removed it. A future maintainer of ASDF may extend the `(:version ,dependency ,minimum-version) pattern for specifying dependencies with a `(:version ,dependency ,minimum-version ,too-large-version) pattern that allows to specify an exclusive upper bound on compatible versions. This would allow finer specification of compatible version ranges than just a match on the major version. But I didn't implement it. I leave it as an exercise for whoever volunteers to replace me, since I'm definitely leaving active maintenance of ASDF and unwilling to implement new features, though I will still fix bugs until a new maintainer rises. PS: this fiasco also suggests that a new maintainer shall include some typical quicklisp usage as part of the automated test suite. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org When you are young you are afraid people will steal your ideas; when you are old you are afraid they won't. — David D. Friedman

2 1

[asdf-devel] add-cldir helper script
by Daniel Herring 08 Apr '15

08 Apr '15

Re: [asdf-devel] Alternate default lisp system location On Wed, 12 Mar 2014, Zach Beane wrote: > Is there some easy way, supported by ASDF, to make a system known to > ASDF if you have its pathname? I added the following function to my ~/bashrc shortly after migrating to the new ASDF config mechanism. add-cldir() { cfg="$HOME/.config/common-lisp/source-registry.conf.d/10-$USER.conf" grep $PWD $cfg || echo "(:directory \"$PWD/\")" >> $cfg } This could easily be converted to a standalone shell script and batch file, suitable for all major platforms. - Daniel

2 1

[asdf-devel] is there a built in way to prevent ASDF from trying to upgrade itself?
by Gary King 08 Apr '15

08 Apr '15

thanks, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

3 2

[asdf-devel] ASDF3, or Why Lisp is Now an Acceptable Scripting Language
by Faré 08 Apr '15

08 Apr '15

Dear Common Lispers, I've submitted this article to ELS 2014. Happily, the deadline has been extended by two weeks, which leaves me time to rewrite it better, with your feedback. Can some of you proofread the article, both/either at a low-level and a high-level? I feel I didn't tie the parts of the article together enough, especially the end, that I rushed. What is worse, the limit is 16 pages, and I went overboard (NB: appendices don't count), so I'll have to cut stuff or move it to appendices. The source code: https://github.com/fare/asdf3-2013/blob/master/asdf3-2014.scrbl The latest compiled versions: http://fare.tunes.org/files/tmp/asdf/asdf3-2014.html http://fare.tunes.org/files/tmp/asdf/asdf3-2014.pdf Is this article useful at all? What high-level questions would you like answered? Note how writing this article has led to a lot of improvements to ASDF and cl-launch in the last few weeks, and is driving some of the discussions currently on asdf-devel. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Every program has at least one bug and can be shortened by at least one instruction — from which, by induction, one can deduce that every program can be reduced to one instruction which doesn't work.

1 0

[asdf-devel] New status of Mac tests
by Robert P. Goldman 08 Apr '15

08 Apr '15

All passing, with the exception of test-stamp-propagation on ABCL. Grr! As before: TEST ABORTED: These two expressions fail comparison with EQUAL: (SANITIZE-LOG (RELOAD ASDF/DEFSYSTEM:DEFSYSTEM)) evaluates to ((:COMPILING :SYSTEM)) (QUOTE ((:COMPILING :SYSTEM) (:COMPILE-TOPLEVEL :FILE1) (:LOAD-TOPLEVEL :FILE1) (:COMPILE-TOPLEVEL :FILE2) (:LOAD-TOPLEVEL :FILE2))) evaluates to ((:COMPILING :SYSTEM) (:COMPILE-TOPLEVEL :FILE1) (:LOAD-TOPLEVEL :FILE1) (:COMPILE-TOPLEVEL :FILE2) (:LOAD-TOPLEVEL :FILE2)) Above backtrace due to this condition: These two expressions fail comparison with EQUAL: (ASDF-TEST::SANITIZE-LOG (ASDF-TEST::RELOAD ASDF/DEFSYSTEM:DEFSYSTEM)) evaluates to ((:COMPILING :SYSTEM)) (QUOTE ((:COMPILING :SYSTEM) (:COMPILE-TOPLEVEL :FILE1) (:LOAD-TOPLEVEL :FILE1) (:COMPILE-TOPLEVEL :FILE2) (:LOAD-TOPLEVEL :FILE2))) evaluates to ((:COMPILING :SYSTEM) (:COMPILE-TOPLEVEL :FILE1) (:LOAD-TOPLEVEL :FILE1) (:COMPILE-TOPLEVEL :FILE2) (:LOAD-TOPLEVEL :FILE2)) Will test on Linux and report results from there, too.

2 1

Re: [asdf-devel] Alternate default lisp system location
by Faré 08 Apr '15

08 Apr '15

>>: Faré >: janderson >> Daniel, if you want changes only every 5 to 10 years, do like >> janderson: try an upgrade every 5 years, find that it breaks your code >> somehow and downgrade back to the old version without further >> investigation. Then maybe 10 years from now you'll get the system >> dependency bug fixed. > > if one wishes to ascribe expectations to my actions, allow me to correct the > presumption, as more accurate would be the hope, in ten years to have the > luxury to work with a build system which leaves my dependency descriptions > alone and uses them to do what it should, without failing for unrelated > reasons. > Well, after 5 to 10 years, some amount of bitrot is to be expected, especially for software that wasn't abandoned but saw active development. It is very unfair of you to complain without ever submitting a bug report: we get no chance to defend ourselves. Did we do something stupid? Did you? Was the issue a known backward incompatibility? Was there a trivial fix, whether already documented or not yet? We'll never know. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org You can of course keep using any old ASDF 1 you like, or whichever or even MK-DEFSYSTEM, which is quite stable. Only if you ever want to use recent libraries that depend on new ASDF features or bug fixes, will you have to upgrade your ASDF.

1 0

[asdf-devel] ASDF, primary-system-name and Quicklisp
by Faré 08 Apr '15

08 Apr '15

Dear Common Lispers, Zach reminds me that one thing is blocking his upgrading the ASDF in Quicklisp is the fact that currently, every user-defined function in *system-definition-search-functions* currently has to be aware of ASDF 3's primary-system-name feature, or it may fail to properly extend ASDF. Here is a patch that will hopefully make things better: whenever ASDF is looking for a non-primary system, it first looks for the associated primary system, in case it defines necessary meta-data. Zach, can you test? If this satisfies you, there's a chance of getting it out of the door as part of the imminent ASDF 3.0.3 release (or else, 3.0.4 next month or so, I hope). —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If Government is the solution to any alleged "failure" of free society, what is the solution to blatant failures of Government?

1 1

[asdf-devel] Bundle tweaks, commit policy
by Faré 08 Apr '15

08 Apr '15

Dear Robert, since I'm tweaking bundle-op, what about we rename fasl-op and load-fasl-op to compile-bundle-op and load-bundle-op? For backward compatibility, we would leave the old names as trivial selfward-operation's that depend on the new ones. That's the kind of change that requires maintainer approval. NB: I've been taking the liberty to commit stuff without review when I feel it's "just bug fixes" and nothing worth of a policy decision. Also, since I've done it so much in this current release, some increment of it won't make things worse. But if I'm taking too much liberty, please tell me: I can stop now, and/or I can be more cautious after your 3.1.1 release. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Mathematicians are like Frenchmen: whatever you say to them they translate into their own language, and forthwith it is something entirely different. — Johann Wolfgang von Goethe

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel