Sorry, that was a bit over the top. I was having a bad day, I'll be
more considerate. I don't actually think that you are obliged to
change anything to suit me.
I'll figure something out, I'm sure, I always have so far.
Robert
On Sun, Sep 15, 2024 at 6:30 PM Robert P. Goldman wrote:
> As far as I can tell, the current behavior is buggy, because it implies that
> ASDF will behave differently when the user chooses to use logical pathnames
> versus when they don’t. That’s not a Good Thing. That’s bad.
Well, all right
On Sun, Sep 15, 2024 at 7:29 PM phoebe Goldman wrote:
> if you're newly adding system definitions, it seems like you must be at
> liberty to choose whatever names you want for those systems, right?
Yes, and I might end up there, but I'd rather keep the name of the
system the same as the name of
On Sun, Sep 15, 2024 at 4:00 PM Robert P. Goldman wrote:
> In afraid that the system lookup works for you but will not work in general
> so the documentation must remain as is.
No, the documentation incorrectly implies that system names containing
uppercase and underscores are invalid in genera
On Sun, Sep 15, 2024 at 3:42 PM Robert P. Goldman wrote:
> I’m away from my desk, so can’t check, but If I recall correctly there are
> name canonicalization functions that downcase. I don’t know if these are
> only applied when a system designator is a symbol or to strings as well.
I looked
On Sun, Sep 15, 2024 at 9:00 AM Faré wrote:
> > Just to be clear, I don't *want* to use logical pathnames, but I will
> > if it provides a solution to the problem.
> Logical pathnames will make anything WA worse.
I am trying to avoid them. I thought perhaps that it would be
necessary --
On Sat, Sep 14, 2024 at 8:45 PM Faré wrote:
> If you're using logical pathnames, you're asking for trouble
> (especially on SBCL). I wasted weeks of my life on logical pathnames,
> and STRONGLY recommend that no one should ever use them anymore under
> any circumstances.
Just to be clear, I don'
On Sat, Sep 14, 2024 at 11:01 AM Robert P. Goldman wrote:
> I’ve got to push back on your rant. There’s a perfectly good reason for those
> two limitations you dislike: they are the same as the limitations on logical
> pathnames. So if you wish to be able to find an ASDF system relative to a
>
Perhaps that's impossible; if so I'd just like to know.
I've tried some different things and haven't come up with anything
that seems to work. A web search finds a few aging and/or obsolete
references, and in any event, nothing specifically directed towards
solving this problem.
Thanks for any insights.
Robert Dodier
On Fri, Sep 22, 2023 at 3:05 PM Blake McBride wrote:
> How can I force asdf to load and use the package in the local directory
> rather than the cached standard distribution?
My understanding is that the following is poor form (I seem to recall
ASDF:*CENTRAL-REGISTRY* is deprecated), however, p
sed to scan the handlers directory, but
something in that process didn't work, so it's loaded by hand.
ADG constructs a new .asd file from the inferred dependencies (and
writes it into the ASDF output cache -- maybe that could be mentioned
in a readme or something) and I present it
On Fri, Dec 16, 2022 at 2:25 PM Faré wrote:
> sbcl --eval "'(#.(require :asdf) #.(in-package :asdf) #.(upgrade-asdf)
> #.(load-system :asdf-dependency-grovel))" --quit
> No error.
I tried it again with ASDF 3.3 + SBCL 2.1.1, and I can load adg
successfully, with a couple of (push "path/to/adg/"
On Fri, Dec 16, 2022 at 3:07 AM Faré wrote:
> Or later. I recommend testing with the latest ASDF.
I tried a later version (3.2 or 3.3, I forget which) and adg fails to
load. I think I'll stick w/ the last known working version until I
sort out getting it to run ...
> This output doesn't help me
I've managed to get asdf-dependency-grovel to load. There is a comment
in adg/tests/grovel-test.lisp that ASDF 3.1 is required. Okay, I have
ASDF 3.1.5 laying around so I loaded that. Now SBCL can load adg.
The test script adg/tests/run-tests.sh runs (with modifications) but
all of the tests fail
Robert, thanks for your reply. I have made some progress.
>> Just performed compiling #> "test-serial-system" "package"> but failed to mark it done
> It would help to get a backtrace here. I can't tell from this if the error is
> happening in ASDF or in ASDF-DEPENDENCY-GROVEL (which probably isn
to extract any
cycles, if I had a directed graph in hand. I don't suppose someone has
already automated looking for cycles in .asd files?
Thanks in advance for any advice, I appreciate your help.
best,
Robert Dodier
PS. Here's my patch for asdf-dependency-grovel.
$ diff -u tests/run-tes
On Wed, Nov 17, 2021 at 10:45 AM Robert Goldman wrote:
> I favor something like this because it would be nice to have prerelease
> versions of ASDF that perform version checks properly.
>
> What I mean is, if we are going to add a feature in version 3.4, right now
> that would be in a prereleas
eemed appropriate.
Any future releases would be on a new branch, presumably version-3_4
or version-4 or whatever; the version-3_3 branch would not be reused
for that purpose.
The benefit of such a scheme, I believe, is just to make it clearer
what's what.
FWIW
Robert Dodier
people will load it by hand instead of
ASDF. But if it is being loaded by ASDF, then I'd like to know that.
Thanks a lot for any info,
Robert Dodier
ame as saying that it is required to be
lowercase.
I found the text about pathname specifiers as well. I didn't see a
requirement there because neither the system name nor component names
were specified by the grammar or the commentary on the grammar to be
pathname specifiers.
Thanks again for
Thanks again, and best wishes.
Robert Dodier
u don't have my maxima-file hackery. If it turns out we need to go
into this in more detail, I will devise a more minimal example. But
first maybe someone can say what the name requirement is.
best,
Robert Dodier
PS.
(defsystem "SolveSolvable2"
:defsystem-depends-on ("max
conscious intent to assert that one condition or
another must prevail. Any improvements by more knowledgeable people
would be welcomed by me.
All the best,
Robert Dodier
the file. That seems like
unfriendly behavior; it seems better that either it should complain or
do nothing.
Thanks for your help, I think I'm in good shape on this front now.
best,
Robert Dodier
PS.
;; info-index.lisp -- ASDF component type for Maxima documentation index
;; copyright 2018 by R
DF maintainer should in the future
> replace all current occurrences of static slots :initform with this style
I dunno -- I think I'm going to play it safe and use the old pattern,
if it's necessary at all ... I'm a pretty casual ASDF user, I don't
know if I can invest the time to figure the old vs new stuff.
All the best,
Robert Dodier
error may be raised. ASDF currently returns the
first system found, ...".
Is there any way to intervene to return a specific system,
specifically the most recent one?
Thank you once again for your help,
Robert Dodier
t? I would have expected (on
little reason) that the parent class CL-SOURCE-FILE would supply that.
(2) In INPUT-FILES, why doesn't (info-index-type c) yield "lisp"?
Doesn't INFO-INDEX have an accessor INFO-INDEX-TYPE?
I may well be very confused about simple things. Thank you for y
found, just
as it is when the index.lisp is loaded via LOAD).
I suppose I could create a class that has the effect of copying the
info files without any other operation on them?
best,
Robert Dodier
I don't doubt that this systems has flaws, but at this point I am
taking it as a given; I'm trying to make progress on a lot of fronts,
and cleaning up this monstrosity is a lower priority item.
best,
Robert Dodier
you
> don't have to use *LOAD-TRUENAME*.
Hmm, examining the cache after running ASDF, I don't see the static
files there. But I think using the component slot to get the file
location is promising, I will give that a try.
best,
Robert Dodier
nal symbols but couldn't puzzle out anything.
The more general idea is that the system contains a non-Lisp data
file. Is there a general approach to work with that?
Thanks for any light you can shed on this problem.
Robert Dodier
ds-on list?
Thanks for your help,
Robert Dodier
re something like
$HOME/.cache/common-lisp/.
I'm constructing the /... part of it. I wonder if it's
possible to tell ASDF it doesn't need to put in the
part.
Thanks for your help, and if you have any comments, I would be
interested to hear about it.
best
Robert Dodier
maxima_asdf.lisp
Description: Binary data
Break 1 QL-SETUP[4]>
Thanks again,
Robert
PS. Here's the example foo.asd I've been working with.
(defsystem foo
:name "foo"
:version "2015.09.21"
:maintainer "Robert Dodier"
:author "Robert Dodier"
:licence "GPL"
:descrip
wnload and
install Maxima packages, and Quicklisp uses ASDF to compile
and load stuff.
Thanks in advance for any light you can shed on this problem.
Robert Dodier
35 matches
Mail list logo
