Thigs deserving attention:
- blas-complex
- blas-real
These two seem to be a problem of ASDF integration with cl:require.
To reproduce:
./lisps/ecl-bin-12.12.1/bin/ecl -norc -eval
'(ext::install-bytecodes-compiler)' -load quicklisp-patched2/setup.lisp
-eval
Maybe the test script runner should just export SHELL=/bin/sh ?
That sounds right for the short term.
I don't claim to have fully grokked ASDF:RUN-PROGRAM yet. Would it be
reasonable to modify it so that when :force-shell is T (a) it prefers
/bin/sh to alternatives, or CMD.EXE on windows?
That smells like a bug in ECL.
This works:
rlwrap ecl -norc -eval \
'(#.(require :asdf) #.(format t \~S~%\ (asdf:asdf-version))
#.(asdf:load-system :sockets))
2.26.6
This doesn't:
rlwrap ecl -norc -load asdf/build/asdf.lisp -eval '(#.(require :asdf)
#.(format t \~S~%\ (asdf:asdf-version))
...@yandex.ru:
23.02.2013, 02:30, Faré fah...@gmail.com:
And so that is my workaround for 2.30.5.
I will run the tests
when you push it
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf
On Thu, Feb 21, 2013 at 4:46 PM, Juan Jose Garcia-Ripoll
juanjose.garciarip...@gmail.com wrote:
On Wed, Feb 20, 2013 at 11:18 PM, Faré fah...@gmail.com wrote:
Implementations that make the standard readtable read-only:
allegro sbcl
Implementations that don't:
abcl ccl clisp cmucl ecl
On Fri, Feb 22, 2013 at 8:42 PM, Dave Cooper david.coo...@genworks.com wrote:
I must be missing something because I thought Quicklisp already rejects at
least new dists if they throw warnings on compiling. Maybe they were/are some
different class of warnings, but I remember clearly that
On Thu, Feb 21, 2013 at 6:44 AM, Anton Vodonosov avodono...@yandex.ru wrote:
Comparision for building with (setf asdf:*default-encoding* :utf-8):
http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-14.html
Wow, it's all positive! Not that surprising, when you think about it.
Maybe I
, 2013-02-21 at 08:00 -0500, Faré wrote:
On Thu, Feb 21, 2013 at 6:44 AM, Anton Vodonosov avodono...@yandex.ru
wrote:
Comparision for building with (setf asdf:*default-encoding* :utf-8):
http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-14.html
Wow, it's all positive
On Thu, Feb 21, 2013 at 10:04 AM, Attila Lendvai
attila.lend...@gmail.com wrote:
dear asdf devels,
i want to conditionally compile and load some lisp files on-demand at
runtime, and i would like to use the asdf machinery for that. the set
of files are not known at development time.
the code
Dear Common Lisp hackers,
Inspecting with Anton Vodonosov the latest batch of cl-test-grid issues
when running with asdf 2.29.x, we found an interesting case
that mirrors the previous failure of iolib 0.7.3 with 2.29.
In the hope of making the semantics of asd files more deterministic,
with an
Dear Lisp hackers,
ASDF 2.30 is another stability release in preparation for ASDF 3.
Since 2.29, in addition to specific portability fixes for CCL and CMUCL,
it notably restores some backward compatible behavior for
syntax tables around loading .asd files, using mutable global tables,
instead of
When we enable the checking of deferred warnings, the following 57
systems have issues. Now to contact the authors.
Then of course, there are all the style-warnings that we are ignoring,
but oh well.
s-xml
mcclim
cl-csv
clsql-helper
lisp-on-lines
regex
zlib
cl-mediawiki
cl-neo4j
cleric
coleslaw
://fare.tunes.org
May you live all the days of your life. — Jonathan Swift
On Wed, Feb 20, 2013 at 9:54 PM, Faré fah...@gmail.com wrote:
When we enable the checking of deferred warnings, the following 57
systems have issues. Now to contact the authors.
Then of course, there are all the style-warnings that we
On Tue, Feb 19, 2013 at 11:27 PM, Dave Cooper david.coo...@genworks.com wrote:
When saving a world (i.e. dumping an image, e.g. dumplisp in Allegro
CL), which has asdf (and quicklisp) loaded in it, what is the proper way to
clear the output-translations and any other local path residue from
On Wed, Feb 20, 2013 at 12:46 AM, Dave Cooper david.coo...@genworks.com wrote:
Holy Cow I started looking through ADSF3 (asdf 2.29) and it is starting to
do everything under the sun!
Well, not *everything*, just everything needed to portably bootstrap
the building of Common Lisp code.
The new
Anton Vodonosov was kind enough to run cl-test-grid against ASDF 2.29,
and here are the results, which I'm sharing with the asdf-devel list
because some people might find this status informative.
I am thinking to add backtraces. Wasn't sure how (to depend
on some library like trivial-backtrace,
Dear Lisp hackers,
ASDF 2.27 was a major rewrite of ASDF, and everything since then
should be considered as candidate releases for ASDF 3:
http://lists.common-lisp.net/pipermail/asdf-announce/2013-February/14.html
ASDF 2.28 was released shortly after 2.27, without an announcement,
If I do a (require FOO) for FOO some internally supplied library of
SBCL, doesn't that trigger the use of ASDF to load FOO?
It does. For example, (require :sb-bsd-sockets) also loads ASDF.
Note that if and when SBCL uses ASDF 3, it will be trivial to update
its contrib to use the
Well, remove-method could be used in some cases,
but it doesn't by far cover all cases:
1- sometimes, the function signature changed;
key arguments were added (or removed?),
a function was made generic that wasn't before,
or generic no more that was before.
Only fmakunbound can handle these
On Thu, Feb 7, 2013 at 9:22 PM, Anton Vodonosov avodono...@yandex.ru wrote:
Diff between unpatched quicklisp 2013-01-28 and quicklisp 2013-01-28 + asdf
2.28.6 for SBCL and CCL:
http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-9.html
07.02.2013, 07:16, Faré fah...@gmail.com:
On Thu
Dear Robert,
it looks like the issue is that you loaded your methods
to extend ASDF before upgrading ASDF itself, which won't work.
Upgrading ASDF includes a FMAKUNBOUND on several functions,
including PERFORM, which indeed UNTRACE's them on many implementations.
ASDF 3 will always try to
On Wed, Feb 6, 2013 at 3:48 PM, Robert Goldman rpgold...@sift.info wrote:
ASDF 3 will always try to upgrade itself before any operation,
precisely to avoid squashing your methods in the middle of the operation,
which would be far worse.
I'm afraid that this behavior needs refinement.
For those who are interested, lp#515807 contains a discussion about
how we'd like to customize LOAD-OP so that on some files it would load
the source
(but what on ECL and MKCL?), whereas on some systems it would load a
bundle, etc.
https://bugs.launchpad.net/asdf/+bug/515807
—♯ƒ • François-René
On Wed, Feb 6, 2013 at 9:22 PM, Anton Vodonosov avodono...@yandex.ru wrote:
Trying with ASDF 2.28.4
The ECL problem has gone, but CCL still can't run quicklisp:
OK, I committed a workaround to ASDF 2.28.5.
lisps/ccl-1.8/lx86cl --no-init --load quicklisp-patched2/setup.lisp
Error: Error
07.02.2013, 05:54, Faré fah...@gmail.com:
On Wed, Feb 6, 2013 at 9:22 PM, Anton Vodonosov avodono...@yandex.ru wrote:
OK, I committed a workaround to ASDF 2.28.5.
Have you pushed it? The comment on the top of asdf.lisp still says This is
ASDF 2.28.4
I was experiencing Internet connection
Anton,
the failure you found seems to be a case of
quicklisp compiling asdf without having loaded it as source first.
To compile asdf even when a previous asdf was loaded,
it is currently necessary to first load asdf.lisp as source.
quicklisp (require)'s the previous asdf,
then compiles the new
On Tue, Feb 5, 2013 at 4:03 AM, Anton Vodonosov avodono...@yandex.ru wrote:
I placed new asdf.lisp into quicklisp and changed (defvar
*required-asdf-version* 2.28)
in quicklisp/setup.lisp to the lates version - 2.28.
This looks like the bad interaction of files compiled with a previous
ASDF
After discussion with people on #lisp and via private chat, I decided
to use a shorter name. Here is what was released in 2.27:
:long-name Another System Definition Facility
:homepage http://common-lisp.net/projects/asdf/;
:bug-tracker https://launchpad.net/asdf/;
:mailto
On Thu, Jan 31, 2013 at 4:13 AM, Bill Robinson wivl...@gmail.com wrote:
Sorry, I haven't touched it for a while. Is this causing a problem? For what
projects? The actual cl-glfw-opengl system is probably a lot less used than
cl-glfw.
Oh, that appeared while blindly loading software from
On Fri, Feb 1, 2013 at 8:19 PM, Anton Vodonosov avodono...@yandex.ru wrote:
01.02.2013, 23:23, Faré fah...@gmail.com:
After discussion with people on #lisp and via private chat, I decided
to use a shorter name. Here is what was released in 2.27:
:long-name Another System Definition
On the one hand, I am deprecating component-property in ASDF3,
Why? What will be the new mechanism for what component-property
provides?
I propose that any data that component-property is actually used for
should be in appropriate slots of the system.
This will introduce a new round of
Synchronization is NOT necessary to add new slots.
If you want a new slot, just create a new class with that slot,
and use both :defsystem-depends-on and :class in your defsystem form.
This usage pattern wouldn't work on ASDF 1 or early ASDF 2, but
it works quite well since ASDF 2.016 from
Dear all,
is anyone of you using any of these functions from ASDF, ASDF-UTILS or
XCVB-DRIVER ?
I've removed them and here are the alternatives I am using.
Since previous code didn't have any numbered release API,
I will only provide compatibility trampolines if there is a declared user base.
Feel free to adopt this technique for your proposed website slot, so it
does not cause compatibility problems. Please do not remove other
techniques.
There is no compatibility problem whatsoever with adding optional slots.
I just tried, and got this:
Error while trying to load
I did an analysis of how system properties are used in Quicklisp systems,
and this suggests that the following initargs be added:
:website-url === widely requested. the URL suffix makes it less ambiguous.
:bug-tracker-url === Zach's request that makes a *whole* lot of sense
:development-email ===
In 2.26.174, I added the following initargs to system with system-FOO accessors.
I also added an :initform nil to all those optional metadata slots and
previous ones.
:long-name Another System Definition Facility
:website-url http://common-lisp.net/projects/asdf/;
:bug-tracker-url
Dear Red,
as a follow up to my previous email, I eventually added in 2.26.174
the following initargs to defclass system, with system-FOO accessors.
:long-name Another System Definition Facility
:website-url http://common-lisp.net/projects/asdf/;
:bug-tracker-url
(Replying in public to this private email; I hope this is not a faux-pas.)
On Thu, Jan 31, 2013 at 11:23 PM, Daniel Herring dherr...@tentpost.com wrote:
:long-name Another System Definition Facility
:website-url http://common-lisp.net/projects/asdf/;
:bug-tracker-url
Fare On the other hand, now is a good time for me to add new slots to
system objects.
Fare I will add a website slot in 2.26.171, though you'll have to
Fare #+asdf3 :website #+asdf3 http://xxx; for now.
Does :website do anything other than record that info? If not, then
why
Getting closer to release. The codebase is stable now, and I'm just
making minor adjustments. Now at 2.26.164.
I'm going to release 2.27 as soon as all tests pass on all
implementations. The magic feature is #+asdf3, and 2.27 should be
considered a pre-release. Hopefully by next month, after some
On Sun, Jan 27, 2013 at 12:13 PM, Robert Goldman rpgold...@sift.info wrote:
On 1/26/13 Jan 26 -6:12 PM, Faré wrote:
I think the whole temporary package thing is a failure, and we
should just have
an ASDF-USER package that uses ASDF.
Does anyone have any objection to having .asd files
On Sat, Jan 26, 2013 at 7:58 PM, Stelian Ionescu sione...@cddr.org wrote:
I think the whole temporary package thing is a failure, and we
What problems does it actually cause ?
It causes having to maintain this weird system,
having functions and classes the symbols of which become
Because the package was delete-package'd in an unwind-protect form
after loading the .asd file, and its symbols are thereafter
uninterned.
Then keep it, store it somewhere and perhaps delete it only when no
longer referenced.
I have no way to know when the package is not referenced.
ASDF
On Thu, Jan 24, 2013 at 9:58 AM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
fare-matcher fails because FARE-UTILS does not designate any package.
Oops, I had removed xcvb-utils, but still needed fare-utils (previous
imported through fare-utils).
This affects weblocks
On Thu, Jan 24, 2013 at 11:41 AM, Zach Beane x...@xach.com wrote:
By the way, this steady stream of oops, ooops, oops, oops, is causing
me a huge, huge, huge headache.
My apologies. I've been focusing so much on ASDF that I forgot to update
all the systems I maintain that indirectly depend on
I'm in the opinion that if you want W-C-U, you should do it yourself explicitly.
However, for the sake of backward compatibility,
and since you have a strong opinion otherwise,
I'll restore the W-C-U :around perform-plan.
The deferred-warning feature (currently on CCL and SBCL only)
will continue
On Thu, Jan 24, 2013 at 8:14 PM, Robert Goldman rpgold...@sift.info wrote:
If you get an error in compilation, and rebuild the system, even on
SBCL, it doesn't seem like the warnings lists get cleared
At least I see ones that are clearly fixed reappear when I use the
restart
Each
as anyone else's. — Faré
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
Now I don't get a package conflict, I get Your ASDF version is too old.
I'm using 2.26. Is taht really too old?
tldr: just update whichever libraries used to depend on xcvb-driver.
Long version:
That's message from xcvb-driver. I will make it clearer.
Yes, on the one hand, 2.26 is too old
When will that work? Right now many things still fail with the most
recent updates of everything, e.g. fare-utils, rpm, cl-launch, exscribe,
etc.
I just fixed rpm, but apart from that, the other ones have already
been fixed yesterday at most.
—♯ƒ • François-René ÐVB Rideau
ABCL is one of the three implementations, together with CLISP and CMUCL,
where I ultimately punted on ASDF hot-upgrade, by just trying to
rename away the ASDF package if it's too old.
I don't know if you're interested in making the kind of package
surgery I was indulging in work,
but it involves
On Mon, Jan 21, 2013 at 11:51 AM, Sam Steingold s...@gnu.org wrote:
* Faré snu...@tznvy.pbz [2013-01-20 22:46:35 -0500]:
Of all the lisp implementations, CLISP has given me the most trouble
with ASDF upgrade. Unlike all other Lisps, it won't let me undefine
functions and redefine them
Of all the lisp implementations, CLISP has given me the most trouble
with ASDF upgrade.
Unlike all other Lisps, it won't let me undefine functions and
redefine them in the same fasl file.
Somehow, I always end up with CLISP either complaining that a function
signature doesn't match
(was or wasn't
Here's another one for James Knight:
ASDF now correctly (I hope) saves undefined function warnings at
compile-time in SBCL,
to check them at the end of a system's build.
All the low level support is in asdf-driver, and the necessary hooks
in asdf-defsystem.
This builds upon work by Douglas Katzman
Lovely. It's a case of merging with the *default-pathname-defaults*
being #p and how I tried to limit the amount of truenaming but
overshot. And while debugging it, running into more bugs in my code,
and loveliness in the implementation such as (equal #pccl: #p/)
== T.
2.26.120 is at your
On Fri, Jan 18, 2013 at 6:12 PM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
OK, so I've put in the archives/ directory of asdf a few tarballs. See:
http://common-lisp.net/project/asdf/archives/
Would you consider adding an URL like asdf-driver-latest.tgz
On Tue, Jan 15, 2013 at 12:27 PM, Raymond Toy toy.raym...@gmail.com wrote:
Is this the right place to talk about asdf-encodings? Apologies if
this is the wrong place.
This is the right place indeed.
One minor issue with asdf-encodings and cmucl: It looks like
find-implementation-encoding
Cc'ng asdf-devel.
On Wed, Jan 16, 2013 at 9:30 AM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
How do I get asdf-driver?
It's currently part of the asdf git tree. Should I make it separate?
I think you can already include asdf-driver.asd without including asdf.
What
On Wed, Jan 16, 2013 at 10:23 AM, Zach Beane x...@xach.com wrote:
For nearly all other libraries, there is a repo or .tgz file I can
download to package it up for Quicklisp. It would be nice if that was
the case for asdf-driver, too.
Sure. Which format do you prefer?
If I remember correctly,
On Wed, Jan 16, 2013 at 10:48 AM, Robert Goldman rpgold...@sift.info wrote:
ccl now passes.
clisp fails to build ASDF successfully:
clisp now passes. I've had a lot more package woes with it
than with any other implementation, and
I can't find a perfect way to upgrade with it.
2.26.103 passes
Works for me. Were you running these tests at the same time?
The two runs could interfere with each other.
—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
Have the courage to take your own thoughts seriously, for they will shape you.
— Albert Einstein
Yes, to run this test, one needs asdf-encodings installed next to asdf.
I've added a check to disable the rest of the test when asdf-encodings
is missing.
I've also made many, many improvements to the runtime part of ASDF,
so it provides things like backtraces, image dump and resume hooks,
Dear Lisp hackers,
I've completed yet another major pass of refactoring of ASDF.
It is now divided into many files, that are concatenated together for
single-file delivery.
(An idea that I once rejected when James Anderson proposed it 3 years ago;
he might have known better. The file has more
On Fri, Jan 11, 2013 at 12:26 PM, Raymond Toy toy.raym...@gmail.com wrote:
Is the plan that asdf is still delivered as one giant file or will it
eventually move to being delivered as multiple files?
Just curious.
ASDF will still be delivered as one giant file.
That's what makes sense for
Dear Xf,
thanks for the patch. On allegro 8.1, is it only compile-file-pathname
that refuses the :external-format argument, or compile-file as well?
In the latter case, how does allegro 8.1 control encoding for input
files? Does it rely on a special variable?
Maybe I should somehow predicate the
Dear Xiaofeng,
assuming it's indeed a bug in allegro 8.1's compile-file-pathname,
can you try to edit the call to compile-file-pathname this way,
in defun compile-file-pathname* ?
(apply 'compile-file-pathname input-file
(remove-keys `(#+(and allegro (not (version= 8
2)))
into bits. See branch exploded on git.
—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
Politicians are like diapers: they must be changed often.
And for the same reasons. [Also, adults don't need either of them. — Faré]
___
asdf
On Tue, Jan 8, 2013 at 11:09 PM, Daniel Herring dherr...@tentpost.com wrote:
On Sun, 6 Jan 2013, Faré wrote:
I will add a concatenate-all-source-op
that recursively descends into all system dependencies,
concatenates all sources, and creates the output file asdf.lisp,
also including
On Sun, Jan 6, 2013 at 5:59 AM, Anton Vodonosov avodono...@yandex.ru wrote:
06.01.2013, 08:02, Faré fah...@gmail.com:
Dear ASDF developers,
so as to not issue ASDF release candidates that are totally bogus anymore,
I've written this program, ql-test, inspired by ql-mapper:
ssh
Dear Robert,
regarding ASDF and libraries,
I think I have a solution that will satisfy everyone.
I will adopt the plan once proposed by James Anderson,
back when ASDF was one third the size that it is now:
split ASDF into many parts, and programmatically reconstitute it
into a single source file
Unhappily, ASDF as it stands follows a plan then perform model
that does not allow for interleaving dependency detection and computation.
The best it can provide is to have two stages, with
a second-stage system that :defsystem-depends-on the first-stage system
for each step that requires such
support for output-translations (lack for
pathname-match-p).
—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
When you've seen one nuclear war, you've seen them all.
On Mon, Dec 31, 2012 at 12:57 PM, Faré fah...@gmail.com wrote:
Another conceptual bug in ASDF
Do you have failure logs I can inspect?
I build each of the hundreds of Quicklisp systems in alphabetical
order. Perhaps some state created by that mechanism is triggering the
problem in a way that doesn't happen when building a system in
isolation.
I'll try to create an easy-to-reproduce
Another conceptual bug in ASDF.
Checking the plans generated for load-fasl-op, I find that with my new
ASDF 2.26.x (currently x=45), it systematically loads all the
individual .fasl's before it loads the .system.fasl, defeating the
purpose.
This was not the case before: in 2.26.7 and earlier,
Dear Gary,
here is a patch to trivial-timeout to prevent unnecessary recompilation,
now that ASDF actually propagates timestamp information
based on static file dependencies.
It basically fixes the .asd file to not reference non-existing files,
so that the absence of those files doesn't cause
On Fri, Dec 28, 2012 at 10:55 AM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
OK, so 2.26.45 is my new release candidate for ASDF 2.27.
Please grab it and test it.
It still breaks gbbopen and fset.
Ouch. I will work with the authors to resolve these issues.
FSet clearly
it.
—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
A real person has two reasons for doing anything ... a good reason and
the real reason.
On Fri, Dec 28, 2012 at 3:50 PM, Robert Goldman rpgold...@sift.info wrote:
On 12/28/12 Dec 28 -9:55 AM, Zach Beane wrote:
Faré fah
OK, so 2.26.45 is my new release candidate for ASDF 2.27.
Please grab it and test it.
Since last release candidate 2.26.24,
* lots of work was done towards backwards compatibility,
fixing bugs introduced or uncovered
during the previous fixing of essential conceptual bugs
through massive
In the meantime, I've moved the parent slot from child-component to
component, to improve backward compatibility.
With this change, hu.dwim.reiterate and lisp-executable-example also
pass.
Has the change been pushed yet?
Oops. I've clearly been lacking in sleep. Pushed.
—♯ƒ •
Scott, here's a trivial patch that makes fset compile to me.
—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
Suppose 2/3 Congress were incinerated, what would we lose to offset our gain
of their salaries and the salaries of their parasites? — H. L. Mencken
My bad. I tried to remove the default type on source-file;
obviously, it's too late and many systems use it already.
Restored it to nil in 2.26.35.
For next time I'm ill-inspired like that, is there a way to load everything
*that's suppose to work* in quicklisp?
I found I could try to load
The FSet failure is due to its using (:system misc-extensions)
amongst its components.
That's always been invalid, I wonder how it could ever possibly work,
and I'm not willing to kluge ASDF into keeping supporting it.
misc-extensions is already present in the depends-on,
which is the correct
On Wed, Dec 19, 2012 at 4:57 PM, Robert Goldman rpgold...@sift.info wrote:
You don't need acl-file any more.
You can now use cl-source-file.cl, which is exported from ASDF.
You can make legacy-acl-source-file inherit from cl-source-file.cl and
cut the ACL-FILE class entirely. That will take
On Tue, Dec 18, 2012 at 8:46 AM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
On Mon, Dec 17, 2012 at 2:19 PM, Christophe Rhodes cs...@cantab.net wrote:
Zach Beane x...@xach.com writes:
Faré fah...@gmail.com writes:
OK, this is now committed as of ASDF 2.26.21 and POIU
It works for me. I suspect you might not have compiled sb-md5 from clean,
and due to that bug I fixed in 2.26.9 which required a substantial
refactoring,
ASDF can now see that file was not up-to-date, when it couldn't see it
earlier.
Can you recompile this contrib from clean, either in
OK, I understand the bug that Xach found:
There was an ancient bug whereby input-files for a module always returned
a singleton list containing the module's component-pathname, its directory.
That wasn't an issue then due to the even greater deep design flaw
of timestamps not being propagated.
On Tue, Dec 18, 2012 at 5:01 PM, Faré fah...@gmail.com wrote:
OK, I understand the bug that Xach found:
There was an ancient bug whereby input-files for a module always returned
a singleton list containing the module's component-pathname, its directory.
That wasn't an issue then due
Casualties of the cleanup were :feature and :if-component-dep-fails.
They were just horrible things.
FYI, the sb-rotate-byte contrib in SBCL uses :if-component-dep-fails.
I've contacted the SBCL maintainers. Hopefully they will revert to
#+x86-64 and such until a new asdf is universal. But
On Mon, Dec 17, 2012 at 2:19 PM, Christophe Rhodes cs...@cantab.net wrote:
Zach Beane x...@xach.com writes:
Faré fah...@gmail.com writes:
OK, this is now committed as of ASDF 2.26.21 and POIU 1.29.3.
It's slightly smaller, it's much cleaner, and it all works.
I hope I have not broken users
Dear Felix,
sorry for having taken so long getting back to you.
On Mon, Dec 10, 2012 at 8:08 PM, Felix Lange f...@twurst.com wrote:
Hi,
I've been thinking a lot about the structure of Common Lisp projects lately
and would like to turn those thoughts into a public discussion.
I believe that
Considering that I ran out of energy with respect to ASDF hacking
following the marathons of refactoring last week,
I'm declaring 2.26.24 a candidate for release of 2.27.
Please test thoroughly, since this is quite a MAJOR release,
with a lot of significant changes.
The only reason I'm not
Dear Nathan,
at least as far as quicklisp-included software goes,
your ironclad and nibbles seem to be the only user of ASDF's
:if-component-dep-fails and :feature features.
These features are a crock and I'd like to plainly remove them.
In the future, I might provide a better-thought-out
On Fri, Dec 14, 2012 at 12:15 PM, Nathan Froyd froy...@gmail.com wrote:
I can probably do that, yes. Why do you say they're a crock? They're very
useful for defining what's supposed to happen at a higher level than
scattering #+/- about source files everywhere.
Oh, they serve a useful
rpgoldman:
I think, if we remove :if-component-dep-fails and replace it with
something better (a choice I heartily applaud), and also add your
prepare-op, that sounds to me like a big enough change to the API to
warrant calling this ASDF 3 sometime soon
There are enough API differences
Problem: asdf's current versioning scheme will declare that asdf 3 is
incompatible with asdf 2, so anyone who tries (asdf:version-satifies
3.0 2.26) is in for a big disappointment.
As long as we reasonably don't break compatibility, I propose we keep
the asdf 2 series going indefinitely.
for Dan Barlow his ASDF apology.
—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
There are two kinds of pacifists: those who try to disarm the criminals, and
those who try to disarm the victims.
On Fri, Dec 14, 2012 at 2:48 AM, Faré fah...@gmail.com wrote:
I have
ASDF 2.26.21 removed the horribly clunky :if-component-dep-fails.
ASDF 2.26.22 added a much more meaningful :if-feature.
Any component can use the :if-feature option, which can be an
arbitrary keyword expression, just like #+.
The difference is that unlike #+ it doesn't magically change the
On Fri, Dec 14, 2012 at 6:40 PM, Robert Goldman rpgold...@sift.info wrote:
On 12/14/12 Dec 14 -3:13 PM, Faré wrote:
Personally, I have pretty much lost track of when features I need were
added to ASDF.
If you care to specify the proper version of asdf to depend on,
the release-to-release
I intend to release 2.27 next week. Can people test on their systems
and their implementations?
Xach, are things all clear with Quicklisp now?
There is an unusual issue with the periods library that I can't quite
puzzle out. It does not have any trouble with ASDF 2.26, but it fails to
load
the results?
—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org
Democracy is a pathetic belief in the collective wisdom of
individual ignorance. — H.L. Mencken
On Thu, Dec 13, 2012 at 9:27 AM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
I intend
901 - 1000 of 1393 matches
Mail list logo
