On 29 January 2011 11:18, Cyrus Harmon ch-l...@bobobeach.com wrote:
And, even worse, how do we asdf:load-op .asd files that contain non-ascii
characters? (besides changing the locale, which, while it will work for a
single .asd file, doesn't address the issue of how to load multiple ASDF
On 29 January 2011 15:42, Anton Vodonosov avodono...@yandex.ru wrote:
You are right! Now I remember, when I worked on that project several years ago
I just opened asdf.lisp, found the compile-file call and introduced the
*compile-file-external-format* there, and then passed the encoding via
On 21 January 2011 05:31, Pascal Costanza p...@p-cos.net wrote:
I guess this is going to be a nice exercise in writing portable programs... ;)
Not for me :-/
1 (truename (user-homedir-pathname))
Error: File #4Phome: does not exist.
While executing: TRUENAME
Whoa, RMCL seems badly broken.
On 20 January 2011 06:49, Pascal Costanza p...@p-cos.net wrote:
It seems that ASDF 2.x doesn't work with RMCL (ASDF 1.x did). Is that a known
issue?
What is RMCL? Digitool's MCL? It might very well have bitrotten,
since I don't think anyone has tried it since we started working on ASDF 2.
I
Based on the patch by Chun Tian, and tests by Robert Goldman, I
committed preliminary support for RMCL in ASDF 2.012.3. Things that
you may want to debug further:
1- In lisp-version-string, the (subseq s 8) may or may not be
warranted anymore. Is there still a big DIGITOOL starting the
I intend to release asdf 2.012 on dec 31. Hopefully, it would be my
last release, and I would push for it to be included in all
implementations. It would be nice if you would test the latest asdf
2.011.x to work on your platform before I do, maybe even try our
regression test suite. Windows
On 15 December 2010 07:10, Tobias C Rittweiler t...@freebits.de wrote:
What is the way to get a textual representation of
the plan of a system?
I wasn't aware that there were one.
Some mix of traverse and operation-description might help.
I would have thought that this is what ASDF:EXPLAIN
responsibilities under that carpet. — Faré
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
On 23 November 2010 23:24, Robert Goldman rpgold...@sift.info wrote:
This branch has patches that add the :here directive to Faré's
configuration DSL. This allows for configuration files to have contents
like:
(:source-registry
(:tree (:here src/lisp/))
(:tree (:here extlib/lisp))
I renamed 2.147 into 2.010.1. We were going back and forth in version
numbers (according to version-satisfies) between 2.1xx and 2.0xx, and
at least that's stopped. We now have quite a few unstable 2.1xx
releases in git with the wrong order, but presumably the few people
who use asdf from git will
I just release ASDF 2.010 (same as 2.146), and I'd like all CL
implementation vendors to test it and include it on their platforms so
one could universally (require :asdf).
As compared to 2.009:
* much faster and more ported recursive groveling through directories
looking for .asd's (notably
1- we probably want conditionally included components, as in xcvb:
(:when (:featurep (:and :sbcl sb-thread)) (:file sbcl-threaded-support))
(:when (:featurep (:or :cmu :scl)) (:file cmucl-support))
2- is depending on a suppressed component a bug, a nop, or something
that forces the component to
1- ASDF has no such mechanism yet. Many people have asked for it (at
least nikodemus, manic12, and myself recently).
2- the feature feature was never working before I fixed and cerror'ed
it, and only does conditional *dependency* on another component, that
has to independently exist or
Dunno what you're trying to do. Works for me.
$ ccl
Welcome to Clozure Common Lisp Version 1.6-dev-r14324M-trunk (LinuxX8664)!
? (require :asdf)
:ASDF
(ASDF)
? (asdf:find-system :asdf)
#SYSTEM asdf
? (asdf:asdf-version)
2.008
? (describe 'asdf:find-system)
ASDF:FIND-SYSTEM
Type: SYMBOL
Class:
On 18 October 2010 12:46, Lou Vanek lou.va...@gmail.com wrote:
I just deleted ALL FASLs in ~/.cache/* and ~/.slime/* and that didn't
change anything.
On Mon, Oct 18, 2010 at 3:36 PM, Lou Vanek lou.va...@gmail.com wrote:
I using asdf version 2.009. That is shown in my first email (in the
On 18 October 2010 12:13, Lou Vanek lou.va...@gmail.com wrote:
http://paste.lisp.org/+2H95
The only thing that I can think of that has changed is I updated truck
and rebuilt ccl.
? (rebuild-ccl :full t)
OK, the error seems to be that you load asdf from your .ccl-init. That
confuses the hell
the output-translations layer seems to be working fine and doing its job.
However, something else seems broken, that supplies the path
d:/grouptix/d:/lisp/cl-pdf/pdf-template.ofasl to AOT, so something
is horribly wrong earlier.
Can you contact me over IRC or Skype (fahree), gtalk
Which version of Lispworks are you using? (asdf:asdf-version)
Can you (trace asdf::apply-output-translations
asdf::translate-pathname* asdf::merge-pathnames*) ?
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
Be wiser than other people if you can; but do not tell
On 11 October 2010 12:12, Zach Beane x...@xach.com wrote:
The problem is not stale fasls in the normal sense of a fasl format
change. The problem is that the package structure of ASDF changed from
minor version to minor version, so fasls that reference one minor
version's packages might
On 8 October 2010 22:56, Zach Beane x...@xach.com wrote:
Daniel Herring dherr...@tentpost.com writes:
On Fri, 8 Oct 2010, Zach Beane wrote:
Say I download a tarball that has a number of projects in it:
$ tar xzvf fooprojects.tgz
fooprojects/neato/neato.asd
fooprojects/neato/neato.lisp
On 9 October 2010 00:02, Daniel Herring dherr...@tentpost.com wrote:
On Fri, 8 Oct 2010, Zach Beane wrote:
Daniel Herring dherr...@tentpost.com writes:
On Fri, 8 Oct 2010, Zach Beane wrote:
...
If these are now unpacked in ~/src/fooprojects/, how can I add that tree
to my ASDF source
| ReflectionCybernethics | http://fare.tunes.org ]
God gave me brains so that I use it, and appreciate his work with the eyes
of a critic and a connoisseur; not so that I behave like a fool, and
believe the twaddles of the first come prophets and priests.
— Faré
here's another one:
In ASDF 1, (component-pathname (find-system ...)) returned the system's
*directory*, which was coherent because the system is a module, so its
pathname is a directory just like for any other sub-module.
In ASDF 2, it seems to return the .asd file instead.
Is this
On 23 September 2010 11:37, Didier Verna did...@lrde.epita.fr wrote:
[ Please, Cc: me as I'm not on the mailing list ]
I already replied to all your questions on c.l.l but I'll reply again here.
1/ why isn't source-registry.conf named asdf-source-registry.conf ?
Because it's not used solely
Which legacy versions of ASDF should we support?
Xach and/or one of his users had trouble with ASDF from SBCL 1.0.38.
# git show sbcl_1_0_38:contrib/asdf/asdf.lisp /tmp/asdf-from-sbcl-1.0.38.lisp
# sha1sum /tmp/asdf-from-sbcl-1.0.38.lisp
fd7eab8cd8e5eaeb34264896d62a8bb3847b4d00
We can identify
standard.
On 16 September 2010 17:42, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
On Sat, Sep 11, 2010 at 7:41 PM, Faré fah...@gmail.com wrote:
I hope that 2.008 will be my last ASDF release. I may still make
emergency bug fixes (if any is needed), or merge patches sent
That said, the problem with *COMPILE-FILE-WARNING-BEHAVIOUR*
is that it's applied *after* COMPILE-FILE finished; it would
be much more intuitive if it failed right at the point
a warning is signaled. More intuitive because the message
of the warning would not be hidden somewhere in the
Dear all,
I hope that 2.008 will be my last ASDF release. I may still make
emergency bug fixes (if any is needed), or merge patches sent to me,
but I don't intend to actively develop ASDF anymore. I feel it has
reached the point where I wanted it to be, although it took much more
efforts than I
On 22 May 2010 18:03, Devon Sean McCullough asdf-u...@jovi.net wrote:
Fix two unreachable code removal warnings in CMUCL: [...]
PS: Is this a good venue for patches?
Thanks a lot! Yes, that's the right venue for patches.
Committed as 2.127.
[ François-René ÐVB Rideau | ReflectionCybernethics |
On 2 September 2010 08:43, Zach Beane x...@xach.com wrote:
Fare, you mentioned that you committed a new version, 2.126. I'd like to
test it by building all Quicklisp projects with it. However, that
revision doesn't show up in the git repo I'm using,
On 2 September 2010 02:11, Daniel Herring dherr...@tentpost.com wrote:
I think ASDF2 makes these steps easier.
- make sure LibCL's ASDF is loaded (ASDF's upgrading handles old
implementations, and blocks a downgrade?)
ASDF doesn't block downgrades.
If you are confident that your
On 20 August 2010 04:32, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
On Thu, Aug 19, 2010 at 9:04 PM, Faré fah...@gmail.com wrote:
I think the too-many-packages problem is not worth wasting time. I would
rather be interested on a _simpler_ bootstrapping process, which
On 31 August 2010 16:39, Robert Goldman rpgold...@sift.info wrote:
#:aif
#:appendf
#:ends-with
#:length=n-p
#:remove-keys
#:remove-keyword
I removed these from the export list in 2.126. Does this require an
urgent 2.008
I can't reproduce your issue.
sbcl --eval '(require :asdf)' --eval '(trace compile-file load
asdf::perform sb-ext:run-program)' --eval '(require :sb-posix)'
sbcl --eval '(require :asdf)' --eval '(trace compile-file load
asdf::perform sb-ext:run-program)' --eval '(asdf:load-system
:sb-posix)'
(Adding sbcl-devel to a thread started on sbcl-help.)
Could it be that you're running from a dumped image and that you're
not exporting SBCL_HOME to a proper value? ASDF does something magic
with SBCL_HOME for those output files.
But yeah, I shall submit a patch to SB-GROVEL so that things
juanjose.garciarip...@googlemail.com wrote:
On Sun, Jul 25, 2010 at 12:48 AM, Faré fah...@gmail.com wrote:
I don't see what probe-file does that's different from (ignore-errors
(truename ...)),
I explained it in the previous email. Determining whether a file exists has
a very very small cost, just
Dear Juanjo,
thanks for your input and sorry for not looking at the details of your
patch earlier.
I don't see what probe-file does that's different from (ignore-errors
(truename ...)), but OK for the sake of performance I can see it being
done. Is CLISP the only one to error when probe-file'ing
On 14 July 2010 16:40, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
Why using TRUENAME + ERROR + HANDLER-CASE instead of PROBE-FILE?
I have been tracking a completely unrelated bug in ECL but found that for
loading all files ASDF calls TRUENAME with the names of FASLs
I blessed 2.111 as 2.004 and released it all.
Several minor bugs have been fixed, and implementation vendors are
recommended to upgrade.
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
It is a miracle that curiosity survives formal education.
— Albert
The contents of laturk-unique.asd:
(in-package :asdf)
(defsystem laturk-unique
:version 0.1.0
:name laturk-unique
:author Louis A. Turk
:description Converts utf-8 text file to list of sorted unique
words.
:components ((:file packages)
(:file iterate :depends-on
28 -10:39 AM, Louis A. Turk wrote:
asdf version 2.104
It looks suspiciously like either (1) you are mixing different versions
of ASDF, including one from before Faré eliminated the internal
'ASDF::AROUND method qualifier, (2) someone in the definition of
ITERATE, or possibly another
Dear Vsevolod,
Approximately after the release of ASDF 2 I've got interested in creating
yet another system distribution management system on top of ASDF, and that
made me investigate ASDF internals. Through that investigation, I've
understood 2 things:
* ASDF has support for much more,
On 28 June 2010 15:03, Louis A. Turk l...@dayspringpublisher.com wrote:
Thanks for replying. You were right about this. However, I'm still
having a problem. I'm getting the following error message:
failed to find the TRUENAME of /home/lat/lisp/il/collate.lisp:
The problem is that
: Faré
: Vsevolod Dyomkin
Dear
If I may suggest a simpler, cheaper and more useful strategy for
helping with the version management of Lisp software, it would be to
automatically produce Debian, RPM or Nix packages from ASDF
specifications, and let those tools do the rest of the integration
Sorry, I've forgotten to address that. I agree, that supporting full
Debian/RPM style versioning is better. I'm not currently familiar enough
with that, so I will be thankful, if you point me to some good resource.
You can google for rpm compare versions and dpkg compare versions
and things
On 24 June 2010 09:41, Attila Lendvai attila.lend...@gmail.com wrote:
is this a bug, or am i doing something wrong?
if a bug, shall i record it as ASDF bug or SBCL bug?
alend...@ed101:/usr/share/common-lisp/source$ rlwrap
~/workspace/sbcl/run-sbcl.sh --no-userinit
(running SBCL from:
I just committed 2.105, then blessed it as the new RELEASE 2.003 on
the release branch.
Nobody complained about the concept of COMPILE-FILE* so I decided it
would be OK to include it in the 2.0 branch.
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
Not only is
Can ABCL upgrade its ASDF to 2.003 or whichever is latest in the
release branch (if possible NOT the master branch)?
That would be great. It should fix several bugs that may have hit ABCL
users since then. Xach at least reported that upgrading ASDF on ABCL
made his software work.
As usual,
The latest ASDF doesn't work well on Windows Vista/7 and Lispworks.
LispWorks regards pathnames such as #PC:/a-dir//anotherdir as illegal
because of the double slashes in it.
I could fix it but it's a really ugly kludge not worth sharing.
Anyway, I could understand where the problem lies:
On 19 June 2010 13:39, Alessandro Piras lay...@gmail.com wrote:
Works like a charm, thanks!
Will this fix be pushed to the git repository?
Pushed to 2.002 in the release branch, and 2.100 in the master branch.
Can you confirm that ASDF 2.002 works well on LispWorks on Windows?
[ François-René
Jun 16 -11:13 AM, Faré wrote:
Robert: any thoughts re: branching?
I am so far from being a git expert, that I will not venture any
suggestions.
A while ago I read the following article which proposes a branching
policy for use with git. It seemed, to my limited understanding
Looking at Stelian's recent patches to iolib, I saw that he uses things like:
(asdf:defsystem :iolib.syscalls
...
:pathname #-asdf2 (merge-pathnames syscalls/ *load-truename*)
#+asdf2 syscalls/
...)
This shocked me, as I new (for having been hit badly by the issue at
ITA and
On Mon, 2010-06-07 at 20:47 -0400, Faré wrote:
After actually using the configuration system, I came to the conclusion
for the sake of simplicity, ASDF should always inherit configuration,
that :inherit-configuration and :ignore-inherited-configuration should
not exist, and be replaced
On 12 June 2010 16:42, Stelian Ionescu sione...@cddr.org wrote:
If searching through :tree hierarchies weren't so desperately slow,
especially on SBCL, I would agree. Unhappily it *is* slow.
And so until and unless performance is fixed, I think it's necessary
to allow to not inherit but
On 12 June 2010 13:45, Robert Goldman rpgold...@sift.info wrote:
On 6/12/10 Jun 12 -6:37 AM, Faré wrote:
Looking at Stelian's recent patches to iolib, I saw that he uses things like:
(asdf:defsystem :iolib.syscalls
...
:pathname #-asdf2 (merge-pathnames syscalls/ *load-truename
On 7 June 2010 00:33, Stelian Ionescu sione...@cddr.org wrote:
Signed-off-by: Stelian Ionescu sione...@cddr.org
---
asdf.lisp | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/asdf.lisp b/asdf.lisp
index 859d93c..0b4ba6c 100644
--- a/asdf.lisp
+++ b/asdf.lisp
Dear Common Lispers,
I have finally released ASDF 2, officially starting with release 2.000.
http://common-lisp.net/project/asdf/
ASDF 2 is an evolution of ASDF that tries to be backwards compatible
with previous releases and their many extensions,
while at the same time improving the
On 30 May 2010 22:00, Seth Burleigh s...@tewebs.com wrote:
Here's the problem i found, is it a bug?
Place
(cffi:defctype Time :unsigned-long)
in any asdf file youre loading. It will produce an error on loading
after requiring once and then it will load successfully after second
require.
I
Plausible.
Seth: can you post on launchpad the error log, and the .asd file, too?
Is your code browsable online?
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
Obstacles are those frightful things you see
when you take your eyes off your goal. — Henry Ford
On
On 26 May 2010 09:20, Robert Goldman rpgold...@sift.info wrote:
On 5/25/10 May 25 -11:11 AM, Faré wrote:
I'm not sure what you want, but try for current directory, .. for up,
etc.
.. is actually not recognized by ASDF but passed to the
implementation, and from it to the OS.
Question
I made an incompatible change in 1.721: before that, it was a
*convention* that configuration files in configuration directories
:include'd by the source-registry or the output-translations
configuration should have :type conf. This interacted poorly with
backup files stored in same directory by
I don't know the status of ASDF-INSTALL.
It looks like ASDF-INSTALL is being maintained outside ASDF.
We probably should remove the asdf-install and cclan files from our repository.
Since ASDF-INSTALL has its own repository, they should probably
#+asdf2 ify any compatibility changes. Sorry
Dear SBCL developers,
could you test for inclusion with your implementation
the current release candidate of ASDF 2 (version 1.715 as of this writing)?
http://common-lisp.net/project/asdf/
ASDF 2 is an evolution of ASDF that tries to be backwards compatible
with previous releases and
Dear CLISP developers,
could you test for inclusion with your implementation
the current release candidate of ASDF 2 (version 1.715 as of this writing)?
http://common-lisp.net/project/asdf/
ASDF 2 is an evolution of ASDF that tries to be backwards compatible
with previous releases and
On 2 May 2010 07:53, Alan Ruttenberg alanruttenb...@gmail.com wrote:
I'm attaching two subsequent calls to
(swank:operate-on-system-for-emacs owl2 (quote load-op)) with
tracing of perform and the two functions you mention. I haven't
touched any files in between, but you will notice the same
Works for me on ASDF.
For load-op and compile-op, times are stored in the operation-times
slot of the component, as accessed by component-operation-times.
Load-source-op should be doing the same, really. I've just added a
method component-operation-time that allows one to do the Right
Thing(tm)
I'd like to freeze the main branch of ASDF tomorrow for anything but
bug fixes and documentation updates.
Is there anything any of you want to commit before the freeze? Or as
an exception to the freeze.
I'm thinking in particular of the stuff in asdf-ecl. Juanjo, do you
think it should be merged
: rpg
: dherring
: rpg
Do we have the system dependencies right yet?
Probably not. However, I don't see that as a regression, nor has it
prevented ASDF from gaining dominance. Thus it can probably wait until
after the ASDF 2 release. No?
You are half right.
You are right that the
: rpg
: dherring
It's not a blocker to not have good system-dependencies, as Daniel says.
But given that, I think the blocker is that we should rip out the
system-dependencies misfeature. It's not right yet, so we shouldn't
ship it, and encourage people to use it.
Would it be possible to
Robert,
I believe that the system-depends-on support, unsatisfactory as it is,
is already useful in some cases, and probably forward-compatible with
a future satisfactory solution, which is why I favor leaving it as is
for 2.0.
However, I will not object if you remove that support or add a
: fare
: james anderson
And even then you'll have a hard time fixing things that users
can now trivially do with the following translation:
(:root (C:/my/cl/cache :implementation))
This will work and make his file in
\\remote-host\myshare\cl\cl-foo\foo-V2.000\bar_baz.lisp
be compiled as
to be correct overcome your desire to have been correct
(which you were not, anyway).
On 20 April 2010 04:10, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
On Mon, Apr 19, 2010 at 8:01 PM, Faré fah...@gmail.com wrote:
I pushed Juanjo's patch for :ASDF-DEPENDENCIES as 1.704, except
Dear James,
before one can declare asdf 2.0 to be feature complete, one should
have a specification of its intended function and then gauge the
implementation in those terms.
I humbly disagree. The standards that I have set to myself for ASDF 2.0
are as follows:
1- improve the ASDF
Dear all,
I think that Juanjo's and Janderson's propositions are on the right
track, and I'm glad Juanjo is stepping forward as ASDF maintainer. I
just have a few points to make:
* while being the XCVB author and ASDF maintainer, I've become acutely
aware of the distance between a simple idea, a
I pushed Juanjo's patch for :ASDF-DEPENDENCIES as 1.704, except that I
renamed the feature :SYSTEM-DEPENDENCIES. Maybe it should have been
:SYSTEM-DEPENDS-ON. Ahem. You tell me what you think.
As for optional dependencies, I think things like
ASDF-SYSTEM-CONNECTIONS are a walking nightmare, and
On 15 April 2010 08:48, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
Just a warning:
Setting up a webpage with a redirect message is not advised by Google.
If you do so instead of setting a redirection via .htaccess, or a permanent
link, then this will be regarded as
I did a big rewrite of TRAVERSE and a bunch of other fixes. Can you
try out ASDF 1.700 ?
Note that this breaks POIU. I don't understand what POIU does to
TRAVERSE and PARSE-COMPONENT-FORM.
I will have to fix it since the reason why I'm interested in fixing
TRAVERSE is to be able to use POIU to
:19 , Faré wrote:
I did a big rewrite of TRAVERSE and a bunch of other fixes. Can you
try out ASDF 1.700 ?
http://lab.setf.de/metadata/reports/2010/04/15/
http://lab.setf.de/metadata/lib/html/build-20100415T233724Z00.html
___
asdf-devel mailing
To prevent Lisp files from being redirected, you can add a rule such as
((:root #p**/*.lisp) t)
in your translations.
OR, you can make sure your output-file methods return T as a second
value to prevent relocation.
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
Ahem. Does it work better with 1.679?
It's hard to test these things without access to a Windows machine...
Also, I realize that in Unix, I rely on absolute-pathname-p meaning
a completely qualified pathname, which breaks down on Windows,
with potentially interesting implications. Sigh.
[
Please open a bug about this.
Is this a regression from old ASDF 1? If it is, make it a asdf 2
milestone, otherwise an asdf 2.1 milestone.
At ITA, we have local extensions to control the ASDF output. I'll have
to dig into the topic someday.
[ François-René ÐVB Rideau | ReflectionCybernethics |
-program
enough to be called a non-programmer. So I'm a non-non-programmer, which,
in intuitionistic logic, is weaker than a programmer. — Faré
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
1- Would making unix-dso a subclass of component but not of module
somehow help solve the problem?
2- I admit I have little familiarity with TRAVERSE. Looking at it
makes me shudder. I really don't want to try understanding it enough
to be able to modify it in ways that I can say for
OK, so there's this dso that at some point ASDF thinks should be
in a translated path, but isn't.
1- First you might want to have a method like this one to create the
output directories:
(defmethod perform :before ((operation compile-op) (c unix-dso))
(map nil #'ensure-directories-exist
The previous .asd had it right in not using make-pathname in the perform,
but instead calling (first (output-files op f)). This one should do
the same, too.
And if it wants to translation for this file, it should also have
output-files return
(values (list ...) t).
[ François-René ÐVB Rideau |
Does it work better with ASDF 1.672? If not, you might have to define
some method for operation-done-p or some such.
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
The equation that makes a harmonous society of free individuals:
LIBERTY = RESPONSIBILITY =
/ When Sorrow walked with me!
— Robert Browning Hamilton
On 5 April 2010 16:05, Robert Goldman rpgold...@sift.info wrote:
On 4/5/10 Apr 5 -9:53 AM, Tobias C. Rittweiler wrote:
Robert Goldman rpgold...@sift.info
writes:
On 4/4/10 Apr 4 -9:50 PM, Faré wrote:
I would in order prefer
Dear Mark,
I merged your patch in, after rearranging it a little bit. Tell me how
it's working for you...
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
Procrastination is great. It gives me a lot more time
to do things that I'm never going to do.
On 5 April
On 5 April 2010 21:26, james anderson james.ander...@setf.de wrote:
On 2010-04-05, at 21:36 , Faré wrote:
Looks like a bug in CMUCL. Sigh.
Does it work better if all occurrences of (user-homedir-pathname) are
replaced with
(truename (user-homedir-pathname)) ?
yes it does.
OK, you can
On 5 April 2010 14:12, Robert Goldman rpgold...@sift.info wrote:
On 4/4/10 Apr 4 -9:50 PM, Faré wrote:
I would in order prefer the following:
1. disable output-translations by default.
I think we can't do that, because of things like system-installed source code
and users who use both
On 6 April 2010 04:58, Daniel Herring dherr...@tentpost.com wrote:
On Tue, 6 Apr 2010, Faré wrote:
I lean the central cache way. But I can be convinced otherwise.
I agree that central caching is a good idea, but think a single central
cache is overly simplistic. Traditional unix systems
I would in order prefer the following:
1. disable output-translations by default.
I think we can't do that, because of things like system-installed source code
and users who use both clisp and ecl (that share the .fas suffix) or
i386 and x86-64 SBCL (that share the .fasl suffix), etc.
If a
Oops, the website is out of date. We really ought to fix that.
I just added this FAQ to the manual (in doc/asdf.texinfo):
@subsection ``How can I wholly disable the compiler output cache?''
To permanently disable the compiler output cache
for all future runs of ASDF, you can:
@example
mkdir -p
There are many things to clarify about logical pathnames and the use
thereof or not, but I don't think this should block a release of ASDF
2. Should it? And so I'd like to declare it an ASDF 2.1 or ASDF 3
issue, and invite you to focus on blocking issues for ASDF 2. (Of
course, if someone has a
Dear Mark,
Fare's suggestion that I use an output translation based on the jar
pathname doesn't quite work, because in our current implementation,
the pathname of the jar is stored in DEVICE, separate from the rest
of the jar pathname. I extended PATHNAME-MATCH-P to match jars
correctly, but
One site per system looks like it will quickly pollute the host
namespace. What about we instead use a single logical host with
subdirectories?
#PCOMMON-LISP:SYSTEMS;CL-PPCRE;CL-PPCRE.ASD
The problem I have with this approach with logical pathnames at all is
that I don't understand whether or
of which civilization is made.
Anyone who rejects tradition per se should be left naked in a desert island.
— Faré
On 27 March 2010 11:32, Futu Ranon futura...@gmail.com wrote:
Hello,
I wanted to test closure-html so I installed and attempted to load it in
LispWorks 6 on Windows.
CL
.
— Faré
On 27 March 2010 11:32, Futu Ranon futura...@gmail.com wrote:
Hello,
I wanted to test closure-html so I installed and attempted to load it in
LispWorks 6 on Windows.
CL-USER 3 (asdf:load-system 'closure-html)
Error: External format (:UTF-8 :EOL-STYLE :LF) produces characters of type
-registry
configuration...
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
Majority, n.:
That quality that distinguishes a crime from a law.
On 24 March 2010 04:14, Mark Evenson even...@panix.com wrote:
On 3/23/10 4:53 PM, Faré wrote:
[…]
I hope ABCL has
, Robert Goldman wrote:
On 3/24/10 Mar 24 -1:36 PM, Faré wrote:
You mean, things like
(asdf:system-relative-pathname :xcvb ) or
(asdf:system-relative-pathname :xcvb master.lisp) ?
Should be working well since 1.649.
It's even documented. The example with should be given, though.
Great. I
1201 - 1300 of 1393 matches
Mail list logo
