Faré fah...@gmail.com writes:
On Fri, Mar 28, 2014 at 11:00 AM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
Once it's accepted that ASDF will enforce the syntax variables decided
This seems more like an if than a once to me.
Then please argue that. I for one fully agree
Attila Lendvai attila.lend...@gmail.com writes:
I do have control: If femlisp or any other library makes a boneheaded
decision that breaks my software, I can stop using it.
yes, resolving that is trivial -- once you have identified the
problem.
regarding the recent discussions i'm
Attila Lendvai attila.lend...@gmail.com writes:
regarding the recent discussions i'm generally baffled why it is at
all a question whether to make a build software deterministic or
not. in my view if there's anything in the global state that has an
effect on the building of a software,
Faré fah...@gmail.com writes:
femlisp raises an interesting issue: it has (setq
*READ-DEFAULT-FLOAT-FORMAT* 'double-float) in setup.lisp, which is
cancelled by the with-standard-io-syntax that I introduce in my
syntax-control branch. I just pushed a change in said branch to make
the
Faré fah...@gmail.com writes:
On Thu, Mar 27, 2014 at 12:30 PM, Robert Goldman rpgold...@sift.net wrote:
Zach Beane wrote:
Faré fah...@gmail.com writes:
femlisp raises an interesting issue: it has (setq
*READ-DEFAULT-FLOAT-FORMAT* 'double-float) in setup.lisp, which is
cancelled
Faré fah...@gmail.com writes:
Should ASDF fail the libraries which modify global readtable - I doubt it's
ASDF role.
Yes it is, see my paper:
http://fare.tunes.org/files/tmp/asdf/asdf3-2014.html#%28part._.Safety_before_.Ubiquity%29
So you want to make a change rapidly to suit the deadlines
Stelian Ionescu sione...@cddr.org writes:
On Thu, 2014-03-13 at 13:40 -0500, Robert P. Goldman wrote:
I'm a little concerned about making BUILD-OP be the default operation.
It seems to me that BUILD is not a good synonym for LOAD, which is
how BUILD-OP is currently interpreted.
I agree.
Robert P. Goldman rpgold...@sift.info writes:
Stelian Ionescu wrote:
On Thu, 2014-02-27 at 22:30 -0600, Robert P. Goldman wrote:
How would you all feel about an alternate default location for lisp
systems, in addition to
~/.local/share/common-lisp/source/
I'm sure that .local was chosen
Robert Goldman rpgold...@sift.net writes:
Zach Beane wrote:
The complexity of the registry configuration is one reason why I added
the ~/quicklisp/local-projects/ mechanism.
Right, so I don't see why there's such a huge objection to having a
similar mechanism for ASDF. Stellian suggests
Dave Cooper david.coo...@genworks.com writes:
The source-registry :tree thing already provides for recursive exclusions.
Ok good. Then how about having ASDF loudly announce that it is registering
the default directory (e.g. ~/cl/), as well as providing the hint about
using a .conf file
Dave Cooper david.coo...@genworks.com writes:
On Wed, Mar 12, 2014 at 2:05 PM, Zach Beane x...@xach.com wrote:
I don't think I want to read loud announcements from ASDF. If it isn't
acting like I want, I'd rather read about how to make it do what I want
in a tutorial or manual.
Loud
Faré fah...@gmail.com writes:
On Wed, Mar 12, 2014 at 6:07 PM, Pascal Costanza p...@p-cos.net wrote:
Can I set CL_SOURCE_REGISTRY to a value that deactivates all default
paths? Then I don't care what the default is...
Yes, the example I gave you did that:
export
Robert P. Goldman rpgold...@sift.info writes:
Faré wrote:
Should non-lowercase strings be either forbidden or case-converted?
That's a backward incompatible change that would need to be tested
with cl-test-grid before it's committed — and even then might affect
unpublished or proprietary
Robert P. Goldman rpgold...@sift.net writes:
Zach, when ASDF reads a system name from a symbol, it takes the symbol
name and down cases it. So loading :foo is the same as loading foo.
So I don't think this should break anything for you, unless quicklisp
has some systems with camel-cased
Faré fah...@gmail.com writes:
PS: is it only me, or is quicklisp disabling output translations for its
Its what? Postscripts?
Zach
This is caused because in older ASDF, a version of 1.whatever was not
considered to satisfy a version requirement of 0.whatever. This was
changed because ASDF updated to 3.0 but was not considered satisfying
2.whatever as required by Quicklisp.
Mirko Vukovic mirko.vuko...@gmail.com writes:
Hello,
this is on recently upgraded SBCL1.1.13 and ASDF 3.0.2
I have a system sitting in ~/quicklisp/local-dists and a development
version sitting in ~/.../lisp-development/
I would like ASDF to open the latter one. I use asdf:load-system.
Some system files look like this:
myproject.asd
(asdf:load-system some-prerequisite)
(defsystem myproject ...)
Can you recommend a good way to detect that system myproject depends
on system some-prerequisite? Are there any hooks or other features of
ASDF that might make it
Robert Goldman rpgold...@sift.net writes:
Zach Beane wrote:
Some system files look like this:
myproject.asd
(asdf:load-system some-prerequisite)
(defsystem myproject ...)
Can you recommend a good way to detect that system myproject depends
on system some-prerequisite
Faré fah...@gmail.com writes:
Are you building binary distributions for the next version of quicklisp?
No, this is how Quicklisp dist building has always worked. The first
version from 2010 used the hackiest thing that worked quickly, and now
I'm trying to clean it up to make it easily
Zach Beane x...@xach.com writes:
Faré fah...@gmail.com writes:
Are you building binary distributions for the next version of quicklisp?
No, this is how Quicklisp dist building has always worked. The first
version from 2010 used the hackiest thing that worked quickly, and now
I'm trying
I've saved an executable SBCL image that includes asdf and calls
load-system. If the system it's loading depends-on sbcl contribs,
e.g. sb-bsd-sockets, it is recompiling the contrib sources.
What causes contribs to get recompiled? Is there an easy way to inhibit
it?
Thanks,
Zach
Faré fah...@gmail.com writes:
On Thu, Oct 31, 2013 at 2:43 PM, Zach Beane x...@xach.com wrote:
I've saved an executable SBCL image that includes asdf and calls
load-system. If the system it's loading depends-on sbcl contribs,
e.g. sb-bsd-sockets, it is recompiling the contrib sources.
What
Faré fah...@gmail.com writes:
No, that's the opposite: if it's preloaded, it should *never* be found
in preference to anything else, it's just available in the image as a
fallback in case no source code was found. And I don't want people to
have to retroactively modify quicklisp so it bumps
Faré fah...@gmail.com writes:
I'm not sure what you call this behavior, but yes, upgrade to a new
ASDF (and getting it fixed if there's a bug) is probably the official
solution as long as ASDF is being maintained. In case ASDF falls back
into not being actively maintained anymore, you can
I'd like to change the output translations for a little while and then
revert them to the previous configuration. Is that possible via the
output translation configuration API?
Zach
Faré fah...@gmail.com writes:
A solution that is both backward-compatible and forward compatible is
1- to rename the systems so they follow the foo/bar convention for
naming systems in foo.asd, so that ASDF3 can find them. This solves
forward compatibility
If anyone considering fixing
Robert Goldman rpgold...@sift.info writes:
Zach Beane wrote:
Faré fah...@gmail.com writes:
A solution that is both backward-compatible and forward compatible is
1- to rename the systems so they follow the foo/bar convention for
naming systems in foo.asd, so that ASDF3 can find them
Faré fah...@gmail.com writes:
On Mon, Jul 8, 2013 at 11:42 AM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
As for stripping the /, currently it's done by the individual functions in
*system-definition-search-functions* by calling primary-system-name.
I think this could
Anton Vodonosov avodono...@yandex.ru writes:
08.07.2013, 01:34, Zach Beane x...@xach.com:
A few projects in quicklisp work something like this:
;;; foo.asd
(defsystem foo ...)
(defsystem foo-extra ...)
;;; bar.asd
(defsystem bar :depends-on (:foo-extra :foo
A few projects in quicklisp work something like this:
;;; foo.asd
(defsystem foo ...)
(defsystem foo-extra ...)
;;; bar.asd
(defsystem bar :depends-on (:foo-extra :foo))
With asdf 2, (asdf:load-system bar) seems to work fine, I guess
because asdf 2 does the equivalent of
Robert Goldman rpgold...@sift.info writes:
Zach Beane wrote:
A few projects in quicklisp work something like this:
;;; foo.asd
(defsystem foo ...)
(defsystem foo-extra ...)
;;; bar.asd
(defsystem bar :depends-on (:foo-extra :foo))
With asdf 2, (asdf:load-system bar
Robert Goldman rpgold...@sift.info writes:
Zach Beane wrote:
Robert Goldman rpgold...@sift.info writes:
Zach Beane wrote:
A few projects in quicklisp work something like this:
;;; foo.asd
(defsystem foo ...)
(defsystem foo-extra ...)
;;; bar.asd
(defsystem bar
Faré fah...@gmail.com writes:
On Tue, Jun 11, 2013 at 1:32 PM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
Inferior-shell *should* be able to compile with ASDF 2.
If not, it's a bug. Meh: not as easy for me to test as I'd like.
It uses the slash/package name thing. I'm
Faré fah...@gmail.com writes:
Autodetection of foo/bar as meaning read it from foo.asd is an
asdf3-ism, but systems named like that work on asdf2 (and asdf1) just
like any other system defined in a .asd — of which there used to be a
lot even before this convention was invented. i.e. once
Faré fah...@gmail.com writes:
Oh shit, that's right: it uses version-satisfies instead of version=
(which didn't exist at the time), and of course, 3.0.0 doesn't satisfy 2.26
because of the major version mismatch. Ouch.
One solution would be that quicklisp be patched to accept asdf if
Faré fah...@gmail.com writes:
You do NOT need the prefix, unless you've explicitly changed package
to one that doesn't :use :asdf.
Or unless you want SLIME auto-indentation to work.
Zach
___
asdf-devel mailing list
asdf-devel@common-lisp.net
Dave Cooper david.coo...@genworks.com writes:
This is with no (in-package ...) form at the beginning.
In any case, it looks like as long as the .asd files are used as intended,
then no package prefix is needed on the (defsystem ...), and no (in-package
...) is needed at the top (when using
Anton Vodonosov avodono...@yandex.ru writes:
Fare, here are the results for quicklisp 2013-01-28 patched with asdf 2.28
and new version of asdf-system-connections:
http://common-lisp.net/project/cl-test-grid/asdf/asdf-diff-6.html
As you see there are failures. One of the most often errors
Faré fah...@gmail.com writes:
On the one hand, I am deprecating component-property in ASDF3,
Why? What will be the new mechanism for what component-property
provides?
Zach
___
asdf-devel mailing list
asdf-devel@common-lisp.net
Faré fah...@gmail.com writes:
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
Faré fah...@gmail.com writes:
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
Faré fah...@gmail.com writes:
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
Faré fah...@gmail.com writes:
I haven't added the slots yet, so of course it won't work.
As for disabling properties on old versions of ASDF that don't
actually support them,
that's what #+asdf3 is for, just like #+asdf2 before it.
When it is time to add support for a bug-tracker-url slot,
Faré fah...@gmail.com writes:
Now I get :ASDF does not match 2.26.114. Is that to be expected?
OK, that was a message from cl-launch.
I both improved the message, and scaled back the ASDF requirement to 2.015,
with explicit loading of asdf-driver if old than that.
While I was at it, I had
Faré fah...@gmail.com writes:
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
Faré fah...@gmail.com writes:
The short life of asdf-utils is causing me a huge headache.
asdf-utils still exists. Now it's just a thin wrapper over asdf-driver.
I broke it briefly, thinking it had no clients (none showing in quicklisp);
Also, Quicklisp is just a subset of the CL code out
Faré fah...@gmail.com writes:
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.
Now I get :ASDF
Faré fah...@gmail.com writes:
Does it also fix the issue with the asdf-utils package name conflict?
Which way do you want the conflict resolved?
The current resolution is that asdf-utils.asd is
an empty system that depends on asdf-driver.asd,
Now I don't get a package conflict, I get Your
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/
The driver is in asdf-driver-2.26.118.tar.gz, which has only the
general-purpose utilities.
Would you consider adding an URL like
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 that will
always refer to the latest version?
Done:
(defun link-archive ()
Faré fah...@gmail.com writes:
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
Faré fah...@gmail.com writes:
On Wed, Jan 16, 2013 at 10:32 AM, Zach Beane x...@xach.com wrote:
Faré fah...@gmail.com writes:
Sure. Which format do you prefer?
If I remember correctly, you will want a directory asdf-driver-2.26.100/
containing the code.
Either format is fine. Sometimes
Faré fah...@gmail.com writes:
Dear Zach,
: Faré
OK, so 2.26.45 is my new release candidate for ASDF 2.27.
Please grab it and test it.
: Zach Beane
It still breaks gbbopen and fset.
It still seems to trigger the package-at-variance issue in weblocks and
other projects.
Did you actually
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.
It still seems to trigger the package-at-variance issue in weblocks and
other projects.
If the new ASDF isn't backwards-compatible with
Faré fah...@gmail.com writes:
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?
Zach
Faré fah...@gmail.com writes:
On Thu, Dec 20, 2012 at 3:39 PM, Zach Beane x...@xach.com wrote:
Here are a few failures:
- Weblocks: http://report.quicklisp.org/weblocks/2012-12-20/failtail.txt
I could not reproduce this one. The mention of SWANK suggests some
previous use of SLIME.
Did
Here are a few failures:
- Weblocks: http://report.quicklisp.org/weblocks/2012-12-20/failtail.txt
- GBBopen also has the issue with :PARENT in the system file
- hu.dwim.reiterate:
http://report.quicklisp.org/hu.dwim.reiterate/2012-12-20/failtail.txt
- lisp-executable-example has
Zach Beane x...@xach.com writes:
A number of projects fail to build with the latest ASDF from git. A few
of them seem to be related to defining a custom file component class
that has a custom file type. For example, see jwacs and portable aserve:
[snip]
CommonQT's failure:
qt.asd: The slot
Faré fah...@gmail.com writes:
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
Faré fah...@gmail.com writes:
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.
Thanks. What about the fset :parent issue?
Zach
___
asdf-devel
Faré fah...@gmail.com writes:
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.
FYI, the projects I mentioned still fail with 2.26.35, with the same
symptoms.
Zach
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 1.29.3.
It's slightly smaller, it's much cleaner, and it all works
Faré fah...@gmail.com writes:
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
Zach Beane x...@xach.com writes:
Faré fah...@gmail.com writes:
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
Faré fah...@gmail.com writes:
sb-md5 hasn't been modified in years, but it depends on sb-rotate-byte
which was just tweaked because of :if-component-dep-fails.
ASDF used to not propagate timestamps from system to system,
or from .asd file to the system internals, but now it does both,
and so
Faré fah...@gmail.com writes:
Ok, I updated to the latest SBCL sources, did this:
sh clean.sh
sh make.sh
sudo sh install.sh
Then I change to the ASDF directory and do this:
sbcl --non-interactive --no-userinit --load asdf.lisp --eval (require
:sb-md5)
I still get the
Faré fah...@gmail.com writes:
Oh: It work for me in SLIME but I can reproduce the issue with your
command-line.
I'll investigate some more. My apologies for the frustration.
Great, I look forward to the diagnosis and cure!
Zach
___
asdf-devel
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 — please test.
Casualties of the cleanup were :feature and :if-component-dep-fails.
They were just horrible
Faré fah...@gmail.com writes:
The patch was applied. I should probably use the same emacs setting to
avoid tabs (what do you use?).
Also, I bumped the version for good measure.
I intend to release 2.27 next week. Can people test on their systems
and their implementations?
Xach, are
Faré fah...@gmail.com writes:
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
Faré fah...@gmail.com writes:
Also, I'd like to know if any package in Quicklisp relies on some ASDF
internals I'd like to rename. This is especially harder when users
define methods on a generic function — you can't rename the function,
then.
Is there an easy way to download EVERYTHING
Faré fah...@gmail.com writes:
Summary: please update asdf to 2.26.9 to test some major improvements
in its build algorithm.
On Sat, Dec 8, 2012 at 2:54 PM, Zach Beane x...@xach.com wrote:
Zach Beane x...@xach.com writes:
When I tried this, most Quicklisp systems failed. I get
Zach Beane x...@xach.com writes:
Faré fah...@gmail.com writes:
Summary: please update asdf to 2.26.9 to test some major improvements
in its build algorithm.
When I tried this, most Quicklisp systems failed. I get this (or
variations):
Error opening
#p/usr/local/lib/sbcl/sb-psoxi
Faré fah...@gmail.com writes:
I did a very quick pass at documenting compile-check, force-not,
require-system, *load-system-operation*. Nothing great, but better
than nothing.
Yes, another major pass at fixing asdf.texinfo would be great.
Robert, I hope everything is now going well with
rpgold...@sift.info writes:
As far as I can tell, this is a misfeature of texinfo. The links only work to
the node level (at least in the info browser). So we would need to reactor
the document into smaller nodes to fix that.
Unfortunately, in addition to requiring some work, that would
Robert Goldman rpgold...@sift.info writes:
FWIW, I never use the HTML version. I always use info inside emacs (not
the standalone version). If I want to read end-to-end, I use PDF, which
has links without the annoying choppiness of a multi-page HTML document.
If you use emacs as your
Faré fah...@gmail.com writes:
Dear Zach,
I'm a bit concerned about quicklisp shipping with a very old version
of ASDF. Quicklisp says it depends on ASDF 2.011 or later in its
*required-asdf-version*, but then you ship with 2.014.6 to load if the
implementation's ASDF is too old. Both
Juan Jose Garcia-Ripoll juanjose.garciarip...@gmail.com writes:
On Fri, Oct 12, 2012 at 4:31 PM, Zach Beane x...@xach.com wrote:
I stopped updating ASDF versions when it seemed to require asdf-ecl.lisp
to work on ECL. Is the case? Can ECL get by with asdf.lisp alone?
Since Faré
Faré fah...@gmail.com writes:
On Thu, Nov 3, 2011 at 21:04, Zach Beane x...@xach.com wrote:
If I'd like to extend the source registry by writing a registry
configuration file somewhere, what's the best place to write that file?
Is there a way to query the running system to get the answer
If I'd like to extend the source registry by writing a registry
configuration file somewhere, what's the best place to write that file?
Is there a way to query the running system to get the answer? Is that
necessary or is there some directory that is always good to use?
Zach
Faré fah...@gmail.com writes:
Do we want to (a) leave run-shell-command half-broken on various
combination of OSes and implementations as soon as any argument needs
quoting, do we want to (b) use heavy artillery to solve the problem
correctly, or should we not just (c) delete this broken
Say I download version 1 of the FOO library and put it in /tmp/foo-1/,
so it looks like this:
/tmp/foo-1/foo.asd
/tmp/foo-1/a.lisp
foo.asd has this:
(asdf:defsystem #:foo
:serial t
:components ((:file a)))
Then I add the path to the central registry and load it:
(push
Faré fah...@gmail.com writes:
There hasn't been much change since last month's flamewar. I'd like to
release ASDF 2.017 next weekend.
Can testers test 2.016.3 as release candidate? Thanks!
It passes all my tests, of course, but experience shows they are far
from sufficient to guarantee
Zach Beane x...@xach.com writes:
Faré fah...@gmail.com writes:
There hasn't been much change since last month's flamewar. I'd like to
release ASDF 2.017 next weekend.
Can testers test 2.016.3 as release candidate? Thanks!
It passes all my tests, of course, but experience shows
Bart Botta found the issue. clim-listener has this form:
(:file asdf :depends-on (package))
It should make explicit its dependency on file-types. I'll follow up
with a McCLIM committer.
Zach
___
asdf-devel mailing list
asdf-devel@common-lisp.net
Matus Kmit simply.nit...@gmail.com writes:
Hi
i have some basic question:
Let's say, i have defined a system where with four files: system.asd,
packages.lisp, file1.lisp, file2.lisp, where file1 and file2 share the
same package and are split more or less only for better organisation
Scott L. Burson sc...@sympoiesis.com writes:
On Mon, Jun 13, 2011 at 6:17 AM, Faré fah...@gmail.com wrote:
I don't see why you believe that ASDF 1.x isn't a viable option.
I'm not among those having trouble with ASDF v2, but I would just
point out that going back to v1 has been made rather
Chun Tian (binghe) binghe.l...@gmail.com writes:
Hi, Zach
I see current latest Quicklisp release 2011051901 ships with ASDF 2.014.6,
but which ASDF version was shipped in last months' Quicklisp? I believe in
that ASDF version I didn't met any issue with LispWorks' ASDF integration.
Before
Faré fah...@gmail.com writes:
Zach: so now I can replace *system-definition-search-functions* with
something else that I defvar instead of defparameter. Problem being
backward compatibility, which pretty much requires squashing the old
symbol or its contents. I propose I create a new variable
Chun Tian (binghe) binghe.l...@gmail.com writes:
Hi, Faré
Sorry, actually I'm using a old ASDF, now the latest. It's from latest
Quicklisp, the version is 2.014.6
I'm on LispWorks. Currently, every time I manually eval a definition, I was
prompted that the definition has been redefined
Zach Beane x...@xach.com writes:
Quicklisp systems are located via a function appended to the end of
ASDF:*SYSTEM-DEFINITION-SEARCH-FUNCTIONS*. It looks like ASDF defines
this variable with DEFPARAMETER, so every time asdf.lisp is loaded, the
value is set to ASDF's initial value. It seems
Chun Tian (binghe) binghe.l...@gmail.com writes:
Hi, ASDF users
Any one know how to reload a .asd file without touch it to let it have a
newer timestamp?
I have a snmp.asd file which contain the content of another file:
(defparameter *mib.lisp-expr*
(with-open-file
(s
Faré fah...@gmail.com writes:
Upgrading from ASDF1 is one thing.
Another thing is that on some implementations (notably SBCL), you
can't undo a defgeneric
What does that mean?
and if the signature changed, you have to use a new symbol, which
invalidates ASDF extensions, that have to be
Ernst van Waning e...@infometrics.nl writes:
Dear Robert,
However, I have one question: what is the reason that these
output translations are apparently not applied to the .asd
files? The way I understand my output-translations, I have
globally specified that all fasls are in an
Faré fah...@gmail.com writes:
I suppose I could break the assumption and see whether Xach comes
to my house with an axe for breaking Quicklisp once more —
or some user of a proprietary application I haven't heard of.
I'd rather not do it without Xach being in the loop.
The assumption that
Nikodemus Siivola nikode...@random-state.net writes:
What is happening is approximately this:
ASDF starts loading ~/tmp/flexi-streams.asd
DEFSYSTEM FLEXI-STREAMS is ok.
During processing of DEFYSTEM FLEXI-STREAMS-TEST, FIND-SYSTEM is
called for FLEXI-STREAM-TEST --
ironically _after_
Nikodemus Siivola nikodemus.siiv...@gmail.com writes:
Those who run into this and need to get work done with devhead SBCL
can in the meanwhile stick this in their .sbclrc after the #-quicklisp
stanza.
I think this should work as well - can you try it and let me know?
(setf
Faré fah...@gmail.com writes:
No, which is why I wrote that I'd be happy if the old behavior was restored.
It has been restored in 2.014.12.
For 2.014.13, I'm considering making asdf not verbose by default. I'm
wondering what you think of it.
I don't like these kinds of user-visible
Faré fah...@gmail.com writes:
On 27 April 2011 12:57, dherr...@tentpost.com wrote:
These are probably good things, but as Zach mentioned, recently ASDF has
started dragging users through internal development. Its a gripe I have
about Slime and some other key libraries, so you are in good
1 - 100 of 122 matches
Mail list logo
