Re: ASDF 3.3.3 is Released

2019-03-29 Thread Robert Goldman
Thank you for catching that, Mark!!! It turns out that `make release-push` didn't actually... push. My bad! I have updated the repo now. Please have another look. Thanks! On 29 Mar 2019, at 6:28, Mark Evenson wrote: On Mar 27, 2019, at 17:49, Robert Goldman wrote: In honor

ASDF 3.3.3 is Released

2019-03-27 Thread Robert Goldman
In honor of the impending 2019 European Lisp Symposium, today we release ASDF 3.3.3, the third bugfix release for the 3.3 release series. We urge implementations that are currently bundling previous versions of ASDF -- and especially those bundling 3.3.0 or 3.3.1 -- to upgrade to 3.3.3 at

Re: long-description

2019-02-25 Thread Robert Goldman
On 25 Feb 2019, at 13:56, Faré wrote: On Mon, Feb 25, 2019 at 2:32 PM Robert Goldman wrote: The more we discuss this, the more I think it's a solution in search of a problem. Just using the standard ASDF file-inclusion capabilities (that Faré shows in his email) seems sufficient to me

Re: long-description

2019-02-25 Thread Robert Goldman
prefer not to give the yak any more facial hair!  On 25 Feb 2019, at 10:43, Raymond Toy wrote: On Thu, Feb 21, 2019 at 8:23 AM Robert Goldman wrote: On 20 Feb 2019, at 22:14, Faré wrote: I've seen the pattern of using :long-description #.(uiop:read-file-string (uiop:subpathname *load-pathname

Re: long-description

2019-02-21 Thread Robert Goldman
On 20 Feb 2019, at 22:14, Faré wrote: I've seen the pattern of using :long-description #.(uiop:read-file-string (uiop:subpathname *load-pathname* "README.md")) spread among CL libraries. I see it only as a waste of kilobytes of data (quadrupled on 32-bit unicode lisps such as SBCL).

Re: Shims for old systems

2019-02-19 Thread Robert Goldman
On 19 Feb 2019, at 1:18, 73budden wrote: Hi! Every time I read "asdf", I feel a pain. I've read that there is an attempt to gain resources to improve asdf. I have a sort of plan. 1. Shims. Recent tightening of rules for system definitions is ok, but there are old systems with no maintainers.

Re: ASDF upgrade script fails on cmucl/Linux

2019-02-19 Thread Robert Goldman
critical is being able to upgrade? Cmucl snapshots usually provide the very latest version of asdf. Fare has reported the issues with cmucl's pcl and I've just been really lazy to dig into the hairy pcl code. On Thu, Feb 14, 2019 at 2:16 PM Robert Goldman wrote: On 14 Feb 2019, at 4:55, Anton

Re: Lowercase naming requirement for systems?

2019-02-19 Thread Robert Goldman
nitely use an extensive overhaul, but this band-aid is well better than nothing. Best regards, Robert On 19 Feb 2019, at 13:30, Robert Dodier wrote: On Sun, Feb 17, 2019 at 4:08 PM Robert Goldman wrote: It's actually there, at least if you are looking for it. In my own defense: I did look for it

Re: Lowercase naming requirement for systems?

2019-02-17 Thread Robert Goldman
I plan to import this into the manual. ... in my copious free time. Best, R On 17 Feb 2019, at 15:01, Florian Margaine wrote: > Hi, > > On Sun, Feb 17, 2019 at 9:54 PM Robert Dodier > wrote: > >> On Sun, Feb 17, 2019 at 6:25 AM Robert P. Goldman >> wrote: >> >>> Quick response for now: yes,

Re: Lowercase naming requirement for systems?

2019-02-17 Thread Robert Goldman
On 17 Feb 2019, at 14:53, Robert Dodier wrote: On Sun, Feb 17, 2019 at 6:25 AM Robert P. Goldman wrote: Quick response for now: yes, lowercase naming is a requirement. Hi Robert, thanks for your reply. Got it, no problem. I will adjust my stuff accordingly. It would really help a lot if

Re: Lowercase naming requirement for systems?

2019-02-17 Thread Robert Goldman
It's actually there, at least if you are looking for it. Looking for "lower" I found this, but in the discussion of `asdf:load-system`, which isn't great placement. ``` Note that the canonical name of a system is a string, conventionally lowercase. A system name can also be specified as a

Re: Lowercase naming requirement for systems?

2019-02-17 Thread Robert Goldman
Another reason is that we allow the programmer to refer to systems with symbols as well as strings, and symbols are not -- without a substantial nuisance -- case-sensitive. I'm afraid you are better off with "solve-solvable2". And avoid "solve_solvable" because underscores are not legal

Re: ASDF upgrade script fails on cmucl/Linux

2019-02-14 Thread Robert Goldman
On 14 Feb 2019, at 4:55, Anton Vodonosov wrote: 13.02.2019, 01:44, "Robert Goldman" : On a happier note, both (Home)brew and Ubuntu have newish versions of clisp which, AFAICT, pass all the ASDF tests. Yay! What newish clisp it is? I have been hoping clips will release somem &q

Re: ASDF upgrade script fails on cmucl/Linux

2019-02-12 Thread Robert Goldman
://fare.tunes.org Every great truth begins as heresy and ends as superstition. — Thomas Henry Huxley On Tue, Feb 12, 2019 at 3:51 PM Robert Goldman wrote: I'm getting a failure of the ASDF upgrade tests on CMUCL since the UIOP dependencies mod: Upgrading ASDF from version 3.1.7 to version

Re: ASDF upgrade script fails on cmucl/Linux

2019-02-12 Thread Robert Goldman
Huxley On Tue, Feb 12, 2019 at 3:51 PM Robert Goldman wrote: I'm getting a failure of the ASDF upgrade tests on CMUCL since the UIOP dependencies mod: Upgrading ASDF from version 3.1.7 to version 3.3.2.13 TEST ABORTED: Error while trying to load definition for system test-asdf from

ASDF upgrade script fails on cmucl/Linux

2019-02-12 Thread Robert Goldman
I'm getting a failure of the ASDF upgrade tests on CMUCL since the UIOP dependencies mod: Upgrading ASDF from version 3.1.7 to version 3.3.2.13 TEST ABORTED: Error while trying to load definition for system test-asdf from pathname /var/lib/jenkins/workspace/asdf-upgrade/test/test-asdf.asd:

Re: how to distinguish public vs private (entry-point vs internal) systems

2019-02-07 Thread Robert Goldman
I think the approach of disabling operate is not a good solution to this problem because, for example (this is one I have actually encountered), one might have multiple test systems that one wishes to test separately. E.g., "Foo/input-test" "Foo/processing-test" ... and so on. So I think it's

Re: how to distinguish public vs private (entry-point vs internal) systems

2019-02-06 Thread Robert Goldman
`. Harder would be getting people to adopt it. But if there's interest, I could try to make one or, given the limited amount of time I have to work on ASDF these days, I would be happy to accept a pull request. Best, Robert On 06 Feb 2019, at 15:36, Robert Goldman wrote: On 6 Feb 2019, at

Re: how to distinguish public vs private (entry-point vs internal) systems

2019-02-06 Thread Robert Goldman
On 6 Feb 2019, at 2:22, Jim Newton wrote: When creating an lisp application I usually have one (or several) what I call top-level asdf systems which advertise the public interface to the application, and I may have several internal systems which are used but not intended for public use. What

Re: clisp testing on linux

2018-12-18 Thread Robert Goldman
c 18, 2018 at 3:58 PM Robert Goldman wrote: The latest tweak was followed by a Jenkins (linux) test failure for clisp on test-encodings.script, with a segmentation fault. I cannot reliably replicate this, and I don't see any reason to assume that this is ASDF's fault, rather than clisp's. I'

clisp testing on linux

2018-12-18 Thread Robert Goldman
The latest tweak was followed by a Jenkins (linux) test failure for clisp on `test-encodings.script`, with a segmentation fault. I cannot reliably replicate this, and I don't see any reason to assume that this is ASDF's fault, rather than clisp's. I'm not sure that there is anything I can do

Bad system name warning and ASDF

2018-12-14 Thread Robert Goldman
I have just pushed 3.3.2.12, which will no longer complain about CL-PPCRE.

Re: why does ASDF ask to please only define system/test?

2018-12-14 Thread Robert Goldman
I have decided I'm tired of having my chain pulled. I have dropped Stas from asdf-devel.common-lisp.net and will reject all messages from him in the future. Also I will be ignoring direct mails from him in the future. I'm done.

Re: why does ASDF ask to please only define system/test?

2018-12-14 Thread Robert Goldman
I have just created a merge request https://gitlab.common-lisp.net/asdf/asdf/merge_requests/116 that *specifically* quashes `BAD-SYSTEM-WARNING` from CL-PPCRE. I'm sick and tired of Stas stoking anger about this issue, so I'm taking the social engineering handle away from him. I welcome

Re: Timing compilation

2018-12-05 Thread Robert Goldman
On 5 Dec 2018, at 10:04, Didier Verna wrote: "Robert Goldman" écrivait: Depending on the host lisp you are using, couldn't you wrap the calls to COMPILE-FILE and LOAD in code that times those operation? I could, but since I want per-library numbers, I would need to r

Re: Timing compilation

2018-12-05 Thread Robert Goldman
On 5 Dec 2018, at 9:46, Didier Verna wrote: François-René ÐVB Rideau écrivait: Simplest method: 1- load the dependencies, possibly using (asdf:operate :prepare-op s) 2- (time (asdf:make s)) Nice, thank you. If I want to time separately the compilation and loading phases of several

Re: ASDF 3 on WIn 10 doesn't find component

2018-09-18 Thread Robert Goldman
df") CL-USER 2 > (asdf:load-system "test") component "test" is not found although it's in d:/grouptix/ On 9/18/2018 3:51 PM, Robert Goldman wrote: You could fix this by doing a bit of configuration, but TBH, it will just be easier to move your common-lisp director into

Re: ASDF 3 on WIn 10 doesn't find component

2018-09-18 Thread Robert Goldman
` (which is C:\Users\Mitch\\) On 9/18/2018 3:27 PM, Robert Goldman wrote: Can you tell us what version of asdf you have? `(asdf:asdf-version)`? Will you please also report what `user-homedir-pathname` returns? It should be the parent of your `common-lisp` directory (I.e., the same as the value

Re: ASDF 3 on WIn 10 doesn't find component

2018-09-18 Thread Robert Goldman
Can you tell us what version of asdf you have? `(asdf:asdf-version)`? Will you please also report what `user-homedir-pathname` returns? It should be the parent of your `common-lisp` directory (I.e., the same as the value of `%LOCALAPPDATA%`; if not, we have found your problem. If so, we

Re: Oddities in ECL tests on Linux

2018-09-02 Thread Robert Goldman
res are due to a bug in ECL, which has already been fixed in the 16.1.3 release. Am 31.08.2018 um 23:36 schrieb Robert Goldman: Unfortunately, this patch doesn't seem to work. Maybe it interferes with condition handlers? At any rate, after I insert it into script-support.lisp I now get two /new/ t

Re: Oddities in ECL tests on Linux

2018-08-31 Thread Robert Goldman
rom stopping, the tests in which ECL would stop without the workaround will fail on ECL versions <= 16.1.2. Am 31.08.2018 um 17:54 schrieb Robert Goldman: On 31 Aug 2018, at 10:35, Marius Gerbershagen wrote: This is most likely a bug in ECL. I recommend trying out a newer version of

Re: Oddities in ECL tests on Linux

2018-08-31 Thread Robert Goldman
patch ASDF. But even someone who doesn't want to patch ASDF, but who would be willing to run the test suite (or help figure out how it could be run through, e.g., Travis), would be a great help. Am 30.08.2018 um 21:51 schrieb Robert Goldman: I'm experimenting with your changes now but, for some rea

Re: Oddities in ECL tests on Linux

2018-08-30 Thread Robert Goldman
0.9f from 2005. Please note, that this test can fail anyway if ECL is built without support for the respective module (be it :rt or :sockets). The change only prevents it from failing on a default build configuration. Am 30.08.2018 um 19:53 schrieb Robert Goldman: Thank you very much

Re: Oddities in ECL tests on Linux

2018-08-30 Thread Robert Goldman
Thank you very much for these, Marius. I will look into fixing them directly. One question - do I need to check for ECL version number when requiring sockets in the test? I.e., to I need to test with `:rt` in older versions and `:sockets` in newer? Or will `:sockets` work in older versions

Oddities in ECL tests on Linux

2018-08-23 Thread Robert Goldman
My Jenkins job is failing to test ECL successfully.  What's interesting is that it looks like the tests are successful, but the checker is failing.  Here's what I see in the transcript: These two expressions fail comparison with EQUAL: (UIOP/UTILITY:NEST

Re: Extracting a UIOP's manual

2018-08-15 Thread Robert Goldman
On 15 Aug 2018, at 8:59, Hugo Ishimaru wrote: Hi all, I have extracted a UIOP's manual from docstrings: https://privet-kitty.github.io/etc/uiop.html It's not perfect in any means as docstring isn't written in a markup langugage, but will be at least a comprehensive reference. The relevant

Re: bootstrapping asdf

2018-08-05 Thread Robert Goldman
bug fixes in 3.3.2.5 — thanks and congratulations again to Robert Goldman for his careful reviewing and testing. —♯ƒ • François-René ÐVB Rideau •Reflection• http://fare.tunes.org It is deplorable that many people think that the best way to improve the world is to forbid something. However, they'

Another apology...

2018-07-31 Thread Robert Goldman
I accidentally committed something with a stupid typo. I force-pushed the last push to keep the history clean. Thanks

More apologies needed

2018-07-29 Thread Robert Goldman
Sorry *again*. My history fixing was done wrong initially. But 3.2.3.3 should be in place fine now. Best, r

A little history rewriting...

2018-07-29 Thread Robert Goldman
Sorry -- I accidentally pushed tag 3.3.3.3 instead of 3.3.2.3. I have fixed that, but it involved deleting the tag from cl.net gitlab after having pushed it. Apologies and thanks to Fare for catching my mistake! R

Re: Issues with Jenkins and clisp

2018-07-29 Thread Robert Goldman
://fare.tunes.org There is no meaning without words, no shape without matter, no soul without body. On Sat, Jul 28, 2018 at 4:28 PM Robert Goldman wrote: For some reason, the ASDF tests are failing on Jenkins on linux with clisp, but only when run in Jenkins and only for clisp. At the command line

Issues with Jenkins and clisp

2018-07-28 Thread Robert Goldman
For some reason, the ASDF tests are failing on Jenkins on linux with clisp, but *only when run in Jenkins and only for clisp*. At the command line, all the tests pass for me. Under Jenkins, I get this failure on `test-program.script`: ``` ;; Loading file test-program.script ... FOO

Re: POIU is bitrotten

2018-07-26 Thread Robert Goldman
PM Robert Goldman wrote: Hi, Faré -- I had a look at POIU, because I thought it would be interesting to fix this. I got pretty badly bogged down, though, because there's a really high barrier to entry in trying to run the tests. The tests require that I have your exscribe system and its

Re: POIU is bitrotten

2018-07-24 Thread Robert Goldman
Hi, Faré -- I had a look at POIU, because I thought it would be interesting to fix this. I got pretty badly bogged down, though, because there's a really high barrier to entry in trying to run the tests. The tests require that I have your exscribe system and its full dependency tail. I

Re: A thing I should know myself....

2018-06-24 Thread Robert Goldman
On 22 Jun 2018, at 23:55, Stas Boukarev wrote: On Fri, Jun 22, 2018 at 5:13 PM Robert Goldman wrote: I have a library that provides DEF-UNIMPLEMENTED as a macro for defining stub functions. When you compile a file with unimplemented functions, you get a warning of the type

Re: A thing I should know myself....

2018-06-22 Thread Robert Goldman
Not sure why that took 8 days to post... On 14 Jun 2018, at 12:50, Robert Goldman wrote: I have a library that provides `DEF-UNIMPLEMENTED` as a macro for defining stub functions. When you compile a file with unimplemented functions, you get a warning of the type `FOO:UNIMPLEMENTED-STUB

Re: gentoo package broken

2018-06-22 Thread Robert Goldman
On 22 Jun 2018, at 12:52, Konstanski, Carlos wrote: The gentoo packaging for the new ASDF version is broken. !!! Fetched file: asdf-3.3.2.2.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 484988 !!! Expected: 487861 -- Carlos Konstanski I am afraid that

A thing I should know myself....

2018-06-22 Thread Robert Goldman
I have a library that provides `DEF-UNIMPLEMENTED` as a macro for defining stub functions. When you compile a file with unimplemented functions, you get a warning of the type `FOO:UNIMPLEMENTED-STUB` in my library `FOO`. I'd like to put in an asdf system definition a file spec something like

Re: ASDF with-muffled-compiler-conditions gripe`

2018-06-11 Thread Robert Goldman
gt; asdf::*warnings-file-type* NIL thanks, Cyrus On 6/9/18 2:13 PM, Robert Goldman wrote: Two suggestions: 1. Let us know the implementation, implementation version, and ASDF version 2. Look at the values of |*uninteresting-conditions*|, |*uninteresting-compiler-condition

Re: ASDF with-muffled-compiler-conditions gripe`

2018-06-09 Thread Robert Goldman
-warnings form) makes the trace output reappear. I could well be overestimating of that particular form, but somehow the TRACE output is being swallowed unless that form is removed. On 6/9/18 1:54 PM, Robert Goldman wrote: On 9 Jun 2018, at 12:38, Cyrus Harmon wrote: Dear ASDF folks, I

Re: ASDF with-muffled-compiler-conditions gripe`

2018-06-09 Thread Robert Goldman
On 9 Jun 2018, at 12:38, Cyrus Harmon wrote: Dear ASDF folks, I was trying to trace calls to compile-file today and noticed that the with-muffled-compiler-conditions form in uiop:compile-file* muffles trace output. Is there anyway to make it not do that? thanks, Cyrus I think you are

Re: Introspecting test suite passing/failing

2018-06-07 Thread Robert Goldman
On 7 Jun 2018, at 1:03, Mark Evenson wrote: On Jun 7, 2018, at 00:21, Robert Goldman wrote: When I replaced fiveam-tester-system with :fiveam-tester-system or "FIVEAM-TESTER-SYSTEM", the load went fine for me with the latest ASDF on Allegro, SBCL, and ABCL 1.5.0. I must have be

Re: Introspecting test suite passing/failing

2018-06-06 Thread Robert Goldman
When I replaced `fiveam-tester-system` with `:fiveam-tester-system` or `"FIVEAM-TESTER-SYSTEM"`, the load went fine for me with the latest ASDF on Allegro, SBCL, and ABCL 1.5.0. Really, no one should be running with an ASDF that's older than 3.2 these days. I thought that all the OSS lisps

Re: Introspecting test suite passing/failing

2018-06-06 Thread Robert Goldman
xtensively. Also, I tend *not* to use the `ASDF/USER` package, but instead be old school and make a package for each `.asd` file. Best, r On 6 Jun 2018, at 13:45, Mark Evenson wrote: On Jun 6, 2018, at 19:14, Robert Goldman wrote: […] If you get a chance, can you eyeball [my example c

Re: Introspecting test suite passing/failing

2018-06-06 Thread Robert Goldman
One more thing. I *believe* that all `fiveam-test-system`s automagically depend on `fiveam`. If I'm wrong about that, I should fix it Cheers, r On 6 Jun 2018, at 12:14, Robert Goldman wrote: On 6 Jun 2018, at 11:37, Mark Evenson wrote: On Jun 5, 2018, at 18:44, Robert Goldman

Re: Introspecting test suite passing/failing

2018-06-06 Thread Robert Goldman
On 6 Jun 2018, at 11:37, Mark Evenson wrote: On Jun 5, 2018, at 18:44, Robert Goldman wrote: I have pushed the system fiveam-asdf, which supports integration between ASDF and the FIVEAM test library, to the contribs directory in the ASDF repo. Please have a look. Be warned! It is old

Re: Introspecting test suite passing/failing

2018-06-05 Thread Robert Goldman
I have pushed the system `fiveam-asdf`, which supports integration between ASDF and the FIVEAM test library, to the contribs directory in the ASDF repo. Please have a look. Be warned! It is old, and not being broke, hasn't been fixed. It inappropriately is housed in the `ASDF` package and

Pushed fix for SBCL deferred warnings as 3.3.2.1

2018-06-02 Thread Robert Goldman
Squashed and merged this, pushed, and deleted the feature branch. Thanks to Eric Timmons for detecting the bug, and to Fare and Attila for reviewing the fix. We can think about a bug fix release sometime soon. I think right before merging the syntax fix, which should give us the basis for

Last call for suggestions on merge request 95 (fix deferred warnings on SBCL)

2018-06-01 Thread Robert Goldman
I believe all the critiques are now addressed. I am rerunning the tests on Mac and Linux, and if all goes well with squash-merge this topic branch to master. So if there are any last issues, please let me know. thanks, r

New candidate patch for DEFERRED-WARNINGS on SBCL

2018-05-31 Thread Robert Goldman
Many thanks to Attila and Fare for suggesting ways to rewrite my original patch. New version now available in the repo. Note: has not been tested on *old* SBCL yet: I will do that later today when I get to the office. Best, r

Re: Is anyone actually using the deferred warnings code?

2018-05-30 Thread Robert Goldman
On 30 May 2018, at 17:28, Stelian Ionescu wrote: I used to use it, then it broke months ago on my local setup so I just disabled it. Two questions: 1. I'm curious about why you used it. Anything you could share would be helpful. 2. Was the breakage due to the change in the compiler

Is anyone actually using the deferred warnings code?

2018-05-30 Thread Robert Goldman
AFAICT, it is disabled by default, and it is not documented in the ASDF manual. So is this code even live, except for in the test scripts? It was pretty painful to get this to work because it relies on unexported (and hence unstable) SBCL internals. My *guess* is that this was originally

Fixing deferred warnings on SBCL 1.4.7+

2018-05-30 Thread Robert Goldman
OK, I have pushed a better solution to gitlab on cl.net, as merge request 95. The history of this branch is a little messy, so I will squash-merge it later. But I would definitely appreciate other eyes on. I had hoped to localize the fix, but it was too hard for me -- getting it right

Re: Deferred warnings broken on SBCL 1.4.7

2018-05-30 Thread Robert Goldman
://fare.tunes.org Passive hope is wishful thinking, a poison of the mind. Active hope is creative passion, the mover of the universe. On Wed, May 30, 2018 at 4:12 PM Robert Goldman wrote: Whoops. Looks like this doesn't work on older SBCLs. I'll fix that now. R On 30 May 2018, at 15:08, Robert Goldman

Re: Deferred warnings broken on SBCL 1.4.7

2018-05-30 Thread Robert Goldman
Whoops. Looks like this doesn't work on older SBCLs. I'll fix that now. R On 30 May 2018, at 15:08, Robert Goldman wrote: I have just pushed a merge request and topic branch for this. See https://gitlab.common-lisp.net/asdf/asdf/merge_requests/95 I'm pretty scared about this -- we

Re: Deferred warnings broken on SBCL 1.4.7

2018-05-30 Thread Robert Goldman
I have just pushed a merge request and topic branch for this. See https://gitlab.common-lisp.net/asdf/asdf/merge_requests/95 I'm pretty scared about this -- we are getting in there and rooting around in SBCL internals in ways that seem almost guaranteed to break again later. But for now, I

ASDF 3.3.2 Released

2018-05-04 Thread Robert Goldman
Today we release ASDF 3.3.2, the second bugfix release for the 3.3 release series. Of primary interest in this release are 1. Multiple fixes in handling misnamed (or "legacy-named," if you prefer) secondary systems ("foo-test" instead of "foo/test"). Thanks to Eric Timmons, there is also a

Re: Problems with DEFSYSTEM-DEPENDS-ON

2018-04-09 Thread Robert Goldman
, r On 9 Apr 2018, at 12:13, Faré wrote: On Mon, Apr 9, 2018 at 12:22 PM, Robert Goldman <rpgold...@sift.info> wrote: On 9 Apr 2018, at 11:17, Attila Lendvai wrote: A cheesy fix would simply be to wrap it in IGNORE-ERRORS. But it might cause errors in its present form. i've l

Re: Building from clean on Allegro Windows

2018-04-09 Thread Robert Goldman
://fare.tunes.org You may easily play a joke on a man who likes to argue — agree with him. — Edgar Waston Howe On Sat, Apr 7, 2018 at 3:22 PM, Robert Goldman <rpgold...@sift.net> wrote: Got the same issue: Warning: FIRST-FEATURE is defined more than once as `operator' in file

Re: Problems with DEFSYSTEM-DEPENDS-ON

2018-04-09 Thread Robert Goldman
On 9 Apr 2018, at 11:17, Attila Lendvai wrote: A cheesy fix would simply be to wrap it in IGNORE-ERRORS. But it might cause errors in its present form. i've learned, painfully, that indiscriminate ignore-errors will almost always bite you back (in the form of wasted debugging time), no

Re: Problems with DEFSYSTEM-DEPENDS-ON

2018-04-09 Thread Robert Goldman
On 7 Apr 2018, at 15:56, Robert Dodier wrote: Thanks to everyone for their interest in this topic. In reference to https://github.com/quicklisp/quicklisp-client/pull/128/, it is only a minimal stop-gap measure which I found could fix the immediate problem which I encountered. I know very

Re: Problems with DEFSYSTEM-DEPENDS-ON

2018-04-07 Thread Robert Goldman
it would work in ASDF 2 and I'm afraid that I don't have the time for the ASDF archaeology required to figure out how to "past-proof" this code. HtH, Best, r On 6 Apr 2018, at 4:20, Mark Evenson wrote: On Apr 2, 2018, at 18:23, Robert Goldman <rpgold...@sift.info> wrote: On

Re: Problems with DEFSYSTEM-DEPENDS-ON

2018-04-02 Thread Robert Goldman
On 1 Apr 2018, at 7:57, Mark Evenson wrote: On Apr 1, 2018, at 14:20, Attila Lendvai wrote: The usage of DEFSYSTEM-DEPENDS-ON to specify dependencies that will be satisfied by QL:QUICKLOAD no longer seems to be working in asdf-3.3.1. FTR, here's the history of this

Re: follow-up about handling .info file and index

2018-03-22 Thread Robert Goldman
On 21 Mar 2018, at 14:09, Robert Dodier wrote: Thanks for your comments, Robert. I've revised the INFO-INDEX class and made it a lot simpler (and still working the same). For what it's worth, I've pasted it below. I noticed that UIOP:COPY-FILE doesn't seem to behave well if told to copy a file

Re: follow-up about handling .info file and index

2018-03-20 Thread Robert Goldman
On 20 Mar 2018, at 12:31, Robert Dodier wrote: Hi, I was asking recently about how to handle a .info file and its index (CL) in ASDF. What I finally settled on is this. When the operation is COMPILE-OP, the .info file is copied to same location where the index fasl will go (because the index

Re: using most recent .asd file, if multiple are present

2018-03-20 Thread Robert Goldman
I think what you want might be more easily done through intervening in Quicklisp, instead of in ASDF. "Newest" as defined by the filesystem might not correspond to "newest" in the intuitive sense, depending on how the files get there. In quick lisp, maybe you could make these different

Re: Testing for ASDF 3.3.2 and beyond?

2018-03-17 Thread Robert Goldman
Thank you very much, Anton. Question: is the inner-conditional-test failure on SBCL 1.3.21 not a regression? I just loaded this system and tested it on my mac with SBCL 1.4.3, and it worked fine, so I'm inclined to treat this is not a problem. Also, the inner conditional system has a readme

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Goldman
On 16 Mar 2018, at 17:52, Robert Dodier wrote: On Fri, Mar 16, 2018 at 1:59 PM, Robert Goldman <rpgold...@sift.info> wrote: Another trick you could try is to define a special class of files for the info files (probably just a subclass of cl-source-file). Then you could tell ASDF not t

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Goldman
On 16 Mar 2018, at 15:03, Robert Dodier wrote: Thanks, Robert, that helps a lot. Using ASDF:SYSTEM-RELATIVE-PATHNAME is a big step forward. A follow-up question: Is there a way to know, within a file which is being loaded, whether or not it's being loaded via ASDF? The index file might be

Re: Finding out from where the .asd was loaded and/or referencing a non-executable data file

2018-03-16 Thread Robert Goldman
On 16 Mar 2018, at 13:05, Lucien P wrote: On Fri, Mar 16, 2018, 11:25 Robert Dodier wrote: Hi, I am resuming my tinkering on the Maxima interface to ASDF. I have bumped into a kind of minor problem for which I don't see a solution. Maxima can read .info files for

Re: Best Practice for an ASDF Variable Like *compile-file-failure-behaviour*

2018-03-09 Thread Robert Goldman
On 9 Mar 2018, at 17:02, Faré wrote: On Fri, Mar 9, 2018 at 5:34 PM, Robert Goldman <rpgold...@sift.info> wrote: Are you just using this for yourself? If so, a simple (let ((asdf:*compile-file-failure-behaviour* :warn)) (asdf:load-system "my system")) will suffice. Yup.

Re: Best Practice for an ASDF Variable Like *compile-file-failure-behaviour*

2018-03-09 Thread Robert Goldman
is behavior reliably. - Original message - From: Robert Goldman <rpgold...@sift.info> To: "Mark H. David" <m...@yv.org> Cc: "ASDF-devel" <asdf-devel@common-lisp.net> Subject: Re: Best Practice for an ASDF Variable Like **compile-file-failure-behaviour**D

Re: Best Practice for an ASDF Variable Like *compile-file-failure-behaviour*

2018-03-09 Thread Robert Goldman
Are you just using this for yourself? If so, a simple ``` (let ((asdf:*compile-file-failure-behaviour* :warn)) (asdf:load-system "my system")) ``` will suffice. Alternatively, you could put something like this in the `.asd` file: ``` (defmethod operate :around ((operation load-op)

Re: package-inferred-systems and primary-system-name

2018-03-08 Thread Robert Goldman
On 1 Mar 2018, at 10:47, Eric Timmons wrote: > MR sent. I took the approach of setting the source-file. The etypecase > approach would have either introduced a circular dependency between > system.lisp and package-inferred-system.lisp or would have required > the package-inferred-system symbol to

Re: Testing for ASDF 3.3.2 and beyond?

2018-03-02 Thread Robert Goldman
On 1 Mar 2018, at 21:45, Faré wrote: You might be interested to know that ACL binds *readtable* on startup to an unmodifieble readtable (which is a violation of CLHS http://clhs.lisp.se/Body/02_aac.htm : "The initial readtable is distinct from the standard readtable. It is permissible for a

Re: Testing for ASDF 3.3.2 and beyond?

2018-03-01 Thread Robert Goldman
On 1 Mar 2018, at 20:33, Faré wrote: > PS: The newer test results look good. I'd like to see the results with > the syntax-control branch, though. There also are a few minor bug > fixes in the pipe that mean we'll have to re-test before release, > anyway. Concur...

Re: package-inferred-systems and primary-system-name

2018-02-28 Thread Robert Goldman
On 28 Feb 2018, at 15:46, Eric Timmons wrote: If a have a package-inferred-systems "a" and "a/b/c", the following code used to return "a": (primary-system-name (find-system "a/b/c")) But after commit 069cd2a6 it returns nil. Happy to patch it, but I wanted to check how to do it before

Re: test-bundle

2018-02-21 Thread Robert Goldman
On 21 Feb 2018, at 10:55, Faré wrote: On Tue, Feb 20, 2018 at 4:44 PM, Robert Goldman <rpgold...@sift.info> wrote: I still see these "dependency not done" warnings in test-bundle on SBCL and other implementations (I haven't checked them all, but at least my big three: SBCL,

test-bundle

2018-02-20 Thread Robert Goldman
I still see these "dependency not done" warnings in test-bundle on SBCL and other implementations (I haven't checked them all, but at least my big three: SBCL, Allegro, and CCL). ``` Running test-bundle.script with sbcl-1.4.3-macosx-x64 ; loading

Releasing 3.3.2

2018-02-20 Thread Robert Goldman
I think we are ready to release 3.3.1.5 as 3.3.2 I am quite busy this week, so it will probably take me a while to get through the necessary drudgery to actually make the release, but there is a good population of fixes to send out, so I'll make it happen. Best, r

Re: Issues with package location information on SBCL

2018-02-20 Thread Robert Goldman
This does seem to illustrate an issue with the current "export everything that's in UIOP" strategy. Should we consider changing this policy? Or, if we have "internal" functions that we don't want to be visible through `UIOP/DRIVER`, should we simply not export them from the sub-packages and

Re: Test-multiple

2018-02-20 Thread Robert Goldman
On 20 Feb 2018, at 10:49, Faré wrote: I don't know what the root cause is here, but this looks like the same bug that is supposed to be fixed, and the fix works for me. Does Jenkins use some fancy filesystem setup that confuses the timestamp checking? It might. Jenkins does everything in a

Re: Test-multiple

2018-02-20 Thread Robert Goldman
been planning an update to the latest ASDF for my upcoming (RSN) release of MKCL 1.1.11, so I may as well squeeze that question in. Regards, JCB On Mon, Feb 19, 2018 at 6:56 PM, Robert Goldman <rpgold...@sift.info> wrote: The failure isn't replicable to me, which bothers me some. I s

Re: Testing for ASDF 3.3.2 and beyond?

2018-02-19 Thread Robert Goldman
enabled.test )#.(quit))" Often failures in cl-test-grid are "just" the result of using too little memory, or batching system loads, or some other reason, and have to be retried. I can try to activate that Windows VM and run the all the tests there, if you want... —♯ƒ • Franç

Test-multiple

2018-02-19 Thread Robert Goldman
Faré --- Would you please add some comments to test-multiple? I got a failure on that with MKCL under jenkins on linux, but cannot replicate that failure running it myself. There's no comment saying what this is supposed to test, other than the name, which suggests that it's about testing

Re: Testing for ASDF 3.3.2 and beyond?

2018-02-16 Thread Robert Goldman
-x86 ecl-16.1.2-unknown-linux-x86-bytecode ecl-16.1.2-unknown-linux-x86-lisp-to-c sbcl-1.3.21-linux-x86 Best regards, \- Anton 14.02.2018, 22:02, "Robert Goldman" <rpgold...@sift.net>: OK, as I said, sorry about the delay. Anton, in place of Fare's #3 below, will you please

Re: Testing for ASDF 3.3.2 and beyond?

2018-02-14 Thread Robert Goldman
OK, as I said, sorry about the delay. Anton, in place of Fare's #3 below, will you please just test what's in the `syntax-control-based-on-standard-syntax` branch? The comparison between 2 and 3 will tell us to what extent it's an issue to lock in standard syntax instead of whatever happens

Re: Multiple processing compiling the same file

2018-01-30 Thread Robert Goldman
Sorry for the late response. What you have seems like it will work, but couldn't you just as easily use the ASDF output translations configuration facility that is described here:

Re: Multiple processing compiling the same file

2018-01-30 Thread Robert Goldman
On 23 Jan 2018, at 5:47, Pascal Bourguignon wrote: > On 23 Jan 2018, at 12:00, Jim Newton wrote: If I run several sbcl processes on different nodes in my compute cluster, it might happen that two different runs notice the same file needs to be recompiled (via asdf),

Re: "deprecated recursive use" warning

2018-01-30 Thread Robert Goldman
On 30 Jan 2018, at 15:53, Attila Lendvai wrote: I haven't used CFFI in a while. TL;DR: is this a sane fix? https://github.com/cffi/cffi/commit/4b9b06f15912e823581b1aeb8a0d5c2ef11f702d -- and here follows the elaborate email that led me to find the above solution: a bit of

  1   2   3   4   5   6   7   8   9   10   >