Re: [asdf-devel] duplicate-names for module and file with same name?

Jianshi Huang wrote: > Hi, > > Currently in parse-component-form function, duplication of names are > checked but modules and files are put to the same category. Is there > any particular reason for this restriction? They are in the same namespace. > > e.g. I can't have both > > foo.lisp > foo/

Re: [asdf-devel] I'm too busy right now to be able to do a good job with ASDF

I volunteer for the commit bit, as well, as back-up to Faré. I'm primarily focused on documentation right now, but have some pending patches (notably "clean-op") on the back-burner. I suggest we also solicit a git-wizard to own the commit bit, as well, in case we need to do some funky rebasing or

[asdf-devel] ASDF minimality

Faré wrote: ... > * try to keep asdf.lisp itself small and recommend that unnecesary > features should be put in contribs instead. Do we have a protocol for loading ASDF that ensures that by virtue of loading it "authorized" contribs (i.e., contribs distributed with ASDF) will also be loadable. O

Re: [asdf-devel] Bizarre consequences of FIND-SYSTEM in ASDF.

Can you explain how you got hold of McCLIM and CL-Utilities? I'd be interested in seeing if I can replicate this, but I haven't used McCLIM in years, and back in those dark days we used only CVS (and we walked to school barefoot, uphill /both ways/). Maybe provide git urls for both mcclim and cl-

Re: [asdf-devel] Output Stream for ASDF

Tobias C. Rittweiler wrote: > Thomas Bartscher writes: > >> Why are warnings of asdf put into *standard-output*? >> Wouldn't it be easier to put those into something like *asdf-warnigs*? This >> way >> users of asdf could redirect those wherever they want. > > That's a pet peeve of RPG, in fact

Re: [asdf-devel] Bizarre consequences of FIND-SYSTEM in ASDF.

Daniel Herring wrote: > On Sun, 29 Nov 2009, Robert Goldman wrote: > >> Can you explain how you got hold of McCLIM and CL-Utilities? I'd be >> interested in seeing if I can replicate this, but I haven't used McCLIM >> in years, and back in those dark days

Re: [asdf-devel] Bizarre consequences of FIND-SYSTEM in ASDF.

dherr...@tentpost.com wrote: > Robert Goldman wrote: >> Daniel Herring wrote: >>> On Sun, 29 Nov 2009, Robert Goldman wrote: > > There would be several benefits if FIND-SYSTEM were to simply PROBE-FILE > for a system definition in each of the configured paths (e.g

Re: [asdf-devel] What is the release process for ASDF?

I just checked, and I see that my documentation patches have not been pushed. Any objection to pushing them before the release? If you are willing to do that, I'd appreciate it. I prefer not to do anything irrevocable to the git repo Best, r __

Re: [asdf-devel] What is the release process for ASDF?

Faré wrote: > 2009/12/1 Robert Goldman : >> I just checked, and I see that my documentation patches have not been >> pushed. Any objection to pushing them before the release? >> >> If you are willing to do that, I'd appreciate it. I prefer not to do >>

Re: [asdf-devel] What is the release process for ASDF?

Faré wrote: > 2009/12/1 Robert Goldman : >>> Sure. Those of you who have patches you want included in the next >>> release, please re-send them to me, if possible based on my >>> development repo at >>> http://common-lisp.net/project/xcvb/git/asdf.git >

Re: [asdf-devel] ASDF minimality

Tobias C. Rittweiler wrote: > Robert Goldman writes: > >> Similarly, I would prefer to have ASDF not fall into the SLIME trap. >> SLIME configuration seems to involve mastering an ever-changing number >> of contribs to get the features you really want > > Sl

[asdf-devel] How about a tabs versus spaces policy for asdf?

I would just be tickled to death if we were to ban tab characters from asdf code (I'm convinced by jwz's argument, and I've been harmed enough times by Windows-versus-others tab issues), but I'd be ok with keeping them. Do we have a consensus on tabs-versus-spaces? Cheerio, r ___

Re: [asdf-devel] How about a tabs versus spaces policy for asdf?

I should actually have been specific about something else: If we prefer spaces to tabs (and I will not attempt to stack my eloquence and vituperation against jwz's), we should probably stick the git-equivalent of a pre-commit-hook into the repo to refuse to accept tabs. Daniel --- is your git fu

Re: [asdf-devel] How about a tabs versus spaces policy for asdf?

Tobias C. Rittweiler wrote: > "Tobias C. Rittweiler" writes: > >> I can recommend to put the following into your .emacs >> >> (add-hook 'lisp-mode-hook >> #'(lambda () >> (setq whitespace-style 'color) >> (setq whitespace-chars '(trailing indentation))

[asdf-devel] testing latest release with allegro

With Allegro 8.1 in both ANSI and modern (case-sensitive) modes, two of the tests fail: test-retry-loading-component-1.script test-utilities.script I have not yet had a chance to debug this. This message may bounce from asdf-devel, since I have had to send it from gmail (linux box doesn't have

Re: [asdf-devel] Pre ML post review

I would like to suggest an addition from my experience of working with colleagues at other companies. I'd suggest that we have a way to specify files relative to something akin to *load-truename*. Here's the use case: you work on a large project with an enormous source code repository, cluttered

[asdf-devel] last patch

In trying to dig at one of TCR's bugs, I was archaeologizing asdf.lisp, to figure out the contents of the *defined-systems* table. Put what I came up with into a docstring. cheers, r ___ asdf-devel mailing list asdf-devel@common-lisp.net http://common-

Re: [asdf-devel] tab-blocking commit hook

On 1/11/10 Jan 11 -9:43 PM, Stelian Ionescu wrote: > On Wed, 2009-12-23 at 23:38 -0500, dherr...@tentpost.com wrote: >> The attached script should prevent tabs in *.asd, *.lisp, or *.script >> files from being committed to a git repository. Existing tabs will not be >> affected, unless they appear

Re: [asdf-devel] tab-blocking commit hook

On 1/14/10 Jan 14 -11:29 AM, dherr...@tentpost.com wrote: > Robert Goldman wrote: >> Is there some reason that this cannot be pushed into the repository >> itself (i.e., used like a blur/clean thing)? See the bottom of this >> page: http://progit.org/book/ch7-2.htm

Re: [asdf-devel] ASDF configuration through files

On 1/18/10 Jan 18 -11:34 AM, Faré wrote: > I updated the code in my ASDF repository, did a second pass on the > configuration code. > I included some documentation in README.source-registry that probably > should be integrated in the "normal" ASDF documentation and/or in web > pages. > Can you look

Re: [asdf-devel] dependency bug?

Oh, yes, and if you want to see what will happen, try (load "bug.asd") (pprint (asdf::traverse (make-instance 'asdf:load-op) (asdf:find-system :bug)) that should display the plan that ASDF has developed for your system without executing it. best, r _

Re: [asdf-devel] dependency bug?

On 1/23/10 Jan 23 -1:13 PM, Robert Brown wrote: > Thanks very much for the suggestions. > > My example code was a simplification of a more complicated system > definition, part of an project where I'm implementing Google's > protocol buffers in Lisp. > >http://github.com/brown/protobuf/blob/m

Re: [asdf-devel] dependency bug?

On 1/23/10 Jan 23 -5:38 PM, Robert Brown wrote: > LOAD-OP definitely compiles the Lisp source and then loads the resulting > fasl file. You use LOAD-SOURCE-OP when you only want to load the Lisp > source code without compiling it. For the record, LOAD-OP compiles the lisp source /if it determines

Re: [asdf-devel] [patch] markdown documentation tweak

For what it's worth, I'd prefer that the markdown documentation die a natural death in favor of the texinfo documentation. The markdown documentation requires a complex toolchain (cl-markdown + many dependencies) that the average ASDF user cannot be expected to have. It also works poorly when you

Re: [asdf-devel] [patch] markdown documentation tweak

On 1/24/10 Jan 24 -12:45 PM, Daniel Herring wrote: > On Sun, 24 Jan 2010, Robert Goldman wrote: > >> For what it's worth, I'd prefer that the markdown documentation die a >> natural death in favor of the texinfo documentation. > > I'm just trying to

Re: [asdf-devel] loading platform-dependent code

On 1/24/10 Jan 24 -2:02 PM, Tamas Papp wrote: > Hi, > > I am the author of the cl-cairo2 library. Cairo itself is a graphics > library, and my library provides a Lisp interface. > > Some of the features (eg drawing in X11, Windows or Quartz) are > platform dependent. Currently, the approach of

Re: [asdf-devel] possible clisp/win32 incompatibility

On 1/24/10 Jan 24 -2:32 PM, Daniel Herring wrote: > Hi all, > > I'm trying to get ABLE running on mswin and hit multiple issues at once... > > For one, it appears the a recent version of ASDF broke compatibility with > clisp on windows. If *enable-asdf-binary-locations* is t, I get "invalid >

Re: [asdf-devel] possible clisp/win32 incompatibility

On 1/24/10 Jan 24 -3:01 PM, Daniel Herring wrote: > On Sun, 24 Jan 2010, Robert Goldman wrote: > >> On 1/24/10 Jan 24 -2:32 PM, Daniel Herring wrote: >>> Hi all, >>> >>> I'm trying to get ABLE running on mswin and hit multiple issues at once... >>

Re: [asdf-devel] possible clisp/win32 incompatibility

On 1/24/10 Jan 24 -3:05 PM, Robert Goldman wrote: > On 1/24/10 Jan 24 -3:01 PM, Daniel Herring wrote: >> On Sun, 24 Jan 2010, Robert Goldman wrote: >> > Can you trace pathname-type inside the invocation of > output-files-using-mappings? This smells like a CLISP bug to me.

Re: [asdf-devel] possible clisp/win32 incompatibility

On 1/24/10 Jan 24 -9:39 PM, dherr...@tentpost.com wrote: > Robert Goldman wrote: >> On 1/24/10 Jan 24 -3:01 PM, Daniel Herring wrote: >>> Thanks for the ideas. Poking around a bit further, it appears that in >>> the following snippet from output-files-using-mappings >

Re: [asdf-devel] dependency bug?

On 1/25/10 Jan 25 -1:58 PM, Robert Brown wrote: > Thanks again for responding to my questions. I've interleaved > a few comments below. > > On 1/23/10, Robert Goldman wrote: >> On 1/23/10 Jan 23 -1:13 PM, Robert Brown wrote: >>> Protocol description files (suf

Re: [asdf-devel] possible clisp/win32 incompatibility

On 1/25/10 Jan 25 -4:46 PM, Sam Steingold wrote: > Daniel Herring wrote: >> Thanks for the ideas. Poking around a bit further, it appears that in the >> following snippet from output-files-using-mappings >> (*centralize-lisp-binaries* is false), (pathname-directory path) is nil. >> >>

[asdf-devel] Question about git

How are we supposed to be reasoning about the multiple git repositories out there? I have been pulling from the master/public one and then working locally. Fare works on his personal working copy. When I make a patch on mine, based on public, seems like I sometimes end up with patches that Fare

Re: [asdf-devel] Question about git

On 1/27/10 Jan 27 -9:34 AM, Samium Gromoff wrote: > From: Robert Goldman >> How are we supposed to be reasoning about the multiple git repositories >> out there? >> >> I have been pulling from the master/public one and then working locally. >> >>

Re: [asdf-devel] ASDF 1.501

On 1/27/10 Jan 27 -12:50 AM, Faré wrote: > I've just released ASDF 1.501 in the official repository, now with all > the source registry configuration that I previously discussed. It's > currently documented in its own file README.source-registry, rather > than in the general manual asdf.texinfo, as

Re: [asdf-devel] ASDF 1.501

ACL tests fail, but with different error: -#--- Using alisp -q -batch Ran 18 tests: 5 passing and 13 failing failing test(s): test-force.script test-module-pathnames.script test-retry-loading-component-1.script test-static-and-serial.script test-touch-system-

Re: [asdf-devel] ASDF 1.501

tweeting" onto IRC), but that seems... suboptimal Next time I want to synchronize with the user group, too! > > [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] > Death is only a milestone - albeit one that is dropped on you > from a very

Re: [asdf-devel] Question about git

On 1/27/10 Jan 27 -3:36 PM, Samium Gromoff wrote: > From: Robert Goldman >> On 1/27/10 Jan 27 -9:34 AM, Samium Gromoff wrote: >>> From: Robert Goldman >>>> How are we supposed to be reasoning about the multiple git repositories >>>> out there? >>&g

Re: [asdf-devel] Question about git

On 1/28/10 Jan 28 -6:53 AM, Pascal J. Bourguignon wrote: > > On 2010/01/27, at 22:47 , Robert Goldman wrote: > >> On 1/27/10 Jan 27 -3:36 PM, Samium Gromoff wrote: >>> From: Robert Goldman >>>> On 1/27/10 Jan 27 -9:34 AM, Samium Gromoff wrote: >>&

Re: [asdf-devel] Question about git

manage multiple remotes in my git repo Best, r > > [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] > There is joy in work. There is no happiness except in the realization that > we have accomplished something. — Henry Ford > > > 2010/1/

Re: [asdf-devel] Question about git

On 1/30/10 Jan 30 -7:08 PM, Samium Gromoff wrote: > From: dherr...@tentpost.com >> To me, a more interesting question is whether people might find a site >> like github or gitorious to be helpful. Such sites have systems for >> making and auto-tracking forks, submitting merge requests, administeri

Re: [asdf-devel] asdf output locations

On 2/1/10 Feb 1 -2:53 AM, Faré wrote: > Dear Tobias, > > thanks for your feedback. > >> a) You should give short reason why backwards incompatibility is not >> provided. In particular, what the problems are with status quo. > "" > These previous programs' API was not designed > for eas

Re: [asdf-devel] ASDF 1.501

On 2/1/10 Feb 1 -12:59 AM, Tobias C. Rittweiler wrote: > Faré writes: > >> I've just released ASDF 1.501 in the official repository, now with all >> the source registry configuration that I previously discussed. It's >> currently documented in its own file README.source-registry, rather >> than i

Re: [asdf-devel] asdf output locations

Having the documentation here is helpful, but a few examples would be even more helpful. For example, if I wanted to replicate Gary's A-B-L in the new configuration language, how would I do that? I don't see an opportunity in the language to grab info about the lisp implementation and compute a b

Re: [asdf-devel] asdf output locations

On 2/1/10 Feb 1 -9:48 AM, Faré wrote: > On 1 February 2010 10:34, Robert Goldman wrote: >> Having the documentation here is helpful, but a few examples would be >> even more helpful. >> >> For example, if I wanted to replicate Gary's A-B-L in the new >> confi

Re: [asdf-devel] ASDF 1.501

Thanks, Faré. I put a launchpad ticket in to add documentation about :asdf2 and *asdf-version*. Should we create a milestone for ASDF version 2? best, r ___ asdf-devel mailing list asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/list

Re: [asdf-devel] asdf output locations --- content files

> >> In the spirit of ASDF, we should be writing output-files methods and >> then allowing your code to shuffle them, but that use-case seems to >> break down a bit here. >> >> Consider providing an asdf system definition for a web site. You want >> to specify the relative location of the co

Re: [asdf-devel] Is this necessary in this form? Re: ASDF 1.501

Can we split out some issues here? I think there's a lot of good stuff in this message, but having it all grouped together may not be helpful: 1. Growth of asdf.lisp a. desirable? b. Should we be splitting the file up more? This seems likely to be helpful to diff, but would lead to one-t

Re: [asdf-devel] asdf output locations --- content files

On 2/2/10 Feb 2 -2:39 AM, Tobias C. Rittweiler wrote: > Robert Goldman writes: > ... > > Instead of *LOAD-TRUENAME* in the .asd file, you could probably get away > with using *COMPILE-FILE-PATHNAME*, say, in the your package.lisp? Which > would not be wrangled by ASDF-Bi

Re: [asdf-devel] Is this necessary in this form? Re: ASDF 1.501

On 2/2/10 Feb 2 -11:39 AM, james anderson wrote: > > On 2010-02-02, at 18:17 , Faré wrote: >>> (c) Asdf binary locations / asdf output locations >> ABL was already merged into ASDF by gwking. While I think it was a >> generally good move, it fails (b), and I think can and should be >> redone bet

Re: [asdf-devel] Is this necessary in this form? Re: ASDF 1.501

On 2/2/10 Feb 2 -4:13 PM, james anderson wrote: > > On 2010-02-02, at 22:48 , Robert Goldman wrote: > >> On 2/2/10 Feb 2 -11:39 AM, james anderson wrote: >>> >>> On 2010-02-02, at 18:17 , Faré wrote: >> >>>>> (c) Asdf binary locations /

Re: [asdf-devel] A dream for ASDF2

I must second Faré's response. We are free to modify ASDF, I believe, and to improve it, but with backward compatibility as a boundary condition. I encourage you to take these ideas --- which seem like good ones --- and invest them either in tool support or into a true ASDF /successor/, such as X

[asdf-devel] Bootstrapping asdf

"The best is the enemy of the good." --- Voltaire There seems to be a strong sentiment from at least part of this mailing list that ASDF loading should be reorganized so that some minimal core functionality is loaded, and more can be loaded on demand. I'd like to go on record as opposing this. I

Re: [asdf-devel] Dependency issues with module sub-class

On 2/3/10 Feb 3 -10:32 AM, Scott Bell wrote: > Hi folks, > > Recently, in order to increase the modularity of our project's ASDF > dependencies, I introduced a sub-class of MODULE called GROUP. > We wanted to keep all of our main .lisp files in the toplevel, so the > purpose of the class is simply

Re: [asdf-devel] Dependency issues with module sub-class

On 2/3/10 Feb 3 -11:53 AM, Faré wrote: > On 3 February 2010 11:32, Scott Bell wrote: >> (:group "x" >> :depends-on ("packages") > If you're not in a subdirectory #p"x/", here add a > :pathname #p"" >> :components >> ((:file "a") >>(:file "b" :depends-on

[asdf-devel] Two patches in passing

I found some cases where the tests could go bad. One where the tests could fail to find asdf.fasl (or equivalent) and one where a style-warning in SBCL could cause the tests to fail. Those are the two messages that should be coming through. I'm not fully sure how to use git send-email yet _

Re: [asdf-devel] [PATCH 2/2] More carefully look for compiled asdf.lisp.

On 2/3/10 Feb 3 -10:34 PM, Faré wrote: > I applied your two other patches, but this one won't apply, probably > because of redundant whitespace changes. > > Please merge it with the latest head on my repo. I'm afraid that is far beyond my git fu. However, I have an alternative soution: In the a

Re: [asdf-devel] asdf 1.600

On 2/4/10 Feb 4 -9:55 AM, Juan Jose Garcia-Ripoll wrote: > On Thu, Feb 4, 2010 at 4:04 PM, Faré > wrote: > > I still would recommend 1.601 as it is an "official" release (whatever > that means) whereas 1.596 isn't. > > > Thanks. That is all I was asking for. >

Re: [asdf-devel] asdf 1.600

On 2/4/10 Feb 4 -2:29 PM, Juan Jose Garcia-Ripoll wrote: > On Thu, Feb 4, 2010 at 7:50 PM, Faré > wrote: > > ASDF didn't use to support ECL for testing at all. I just added this > support and found about the warnings, so it counts as my having warned > you imm

[asdf-devel] Launchpad bug 502946

Wrt https://bugs.launchpad.net/asdf/+bug/502946, module is not recompiled if _intra_-system dependency changes, I have spent quite some time groveling over the source code to TRAVERSE, and I believe that this is going to be quite difficult to fix. There are a number of assumptions baked into TRAVE

[asdf-devel] A shot at fixing the module dependency bug

OK, I have committed a first shot at fixing this. However, there is no easy way to have a module update its components upon dependency change but not have a system update its components upon dependency change, because a system is a subclass of module. So my path may not be desirable, or at any ra

[asdf-devel] Looking for some help crafting a test case

I believe my first ASDF patch had a minor buglet that could cause over-compilation. Here's the deal: when new TRAVERSE detects that the components of a module need to have an operation performed on them, it binds a dynamic variable and calls itself on the components of the module. The dynamic va

[asdf-devel] Refined the module dependency fix

I have a series of patches I am about to push to the module-depends branch. Because I have had to rebase this onto master as new master changes have come in, this will not be a fast-forward update when you pull it into your local repo. So this is a head's up. I will push the update sometime afte

[asdf-devel] New module-depends branch contents pushed

Not a fast-forward push. But should be well worth it! Best, r ___ asdf-devel mailing list asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel

Re: [asdf-devel] launchpad bug-502946 [ Re: New module-depends branch contents pushed

On 2/10/10 Feb 10 -2:05 PM, james anderson wrote: > good evening; > > my usual question: is this necessary in this form? > i pose the question from the perspective that a change from a context > free interpreter to a context-sensitive one is rather more drastic > than just getting dynamic bind

[asdf-devel] Module dependencies still arguably wrong

Earlier I claimed that the new ASDF TRAVERSE computed a conservative approximation to what needed to be recompiled. In particular, if we have (defsystem X :depends-on (Y) ) With the new patch, if we do load-op on X, and Y has changed, X will be recompiled. In Classic ASDF, this would no

[asdf-devel] last note about the module dependencies for now...

I believe by adding a little bit more hair (a test that a component IS a module and IS NOT a system) to the TRAVERSE structure, I can salvage INTRA-system dependencies involving modules without trying to fix INTER-system dependencies, which seems like too big a bite to chew off. What would people

[asdf-devel] Trying again

OK, I have just pushed an alternative solution to the module dependency bug, this one (I believe) only triggered by INTRA-system dependencies. This one is also on the module-depends branch. This was achieved, as I said, at the cost of some hair, but I believe it does the right thing to the extent

Re: [asdf-devel] Trying again

On 2/10/10 Feb 10 -10:38 PM, Faré wrote: > On 10 February 2010 18:27, Robert Goldman wrote: >> OK, I have just pushed an alternative solution to the module dependency >> bug, this one (I believe) only triggered by INTRA-system dependencies. >> This one is also on the module-d

Re: [asdf-devel] Module dependencies still arguably wrong

On 2/10/10 Feb 10 -10:08 PM, dherr...@tentpost.com wrote: > [I don't expect the following to appear in ASDF. :)] > > Many build systems consider dependencies to be a solved problem. > Unfortunately, I don't know of any suitable for CL. > > There are two proven approaches to detecting changes >

Re: [asdf-devel] Trying again

On 2/11/10 Feb 11 -11:11 PM, Faré wrote: >> I think to be fair to James he's not saying that ASDF should DWIM, he >> was asking for a minimum perturbation fix. >> > No, he's rejecting an actual fix to actually broken behaviour, > in favor of something that's not specified and not specifiable, > whe

Re: [asdf-devel] Trying again

On 2/12/10 Feb 12 -4:48 AM, james anderson wrote: > good morning; > > On 2010-02-12, at 06:11 , Faré wrote: > >> [...] >>> The problem with doing the INTER-system dependencies is that I don't >>> believe that ASDF currently has the infrastructure to do The Right >>> Thing. In order to do the rig

Re: [asdf-devel] Trying again

On 2/12/10 Feb 12 -8:07 AM, Faré wrote: >>> : Faré >> : james anderson >> >>> Maybe the current timestamps in ASDF are somewhat lacking, but >>> that doesn't mean timestamps can't solve the issue. I think that >>> one timestamp per pair (op component) should do the trick, stored >>> as an alist (op

[asdf-devel] Module-depends patch is in place

OK, I have merged the module-depends branch into master and pushed the result. I suppose we should probably kill the module-depends branch on the public repo now Have a good weekend, all! r ___ asdf-devel mailing list asdf-devel@common-lisp.net htt

Re: [asdf-devel] minor suggestions

On 2/13/10 Feb 13 -12:31 PM, Tobias C. Rittweiler wrote: > > * How about adding a TEST-OP to ASDF's asd? I think there's a related launchpad ticket about this. We don't have an easy way to fire up subsidiary lisps from inside an ASDF job, and especially don't have a good way to harvest results.

Re: [asdf-devel] Module-depends patch is in place

On 2/12/10 Feb 12 -8:08 PM, Faré wrote: > Thanks! > > Shouldn't > (or *forcing* > (and >(not (typep c 'system))) > forced) > be instead > (or *forcing* > (and >(not (typep c 'system)) >forced) > ? Yes, you are quite right. Sorry about that. Looks like yo

Re: [asdf-devel] patch for component-relative-pathname

Would anyone object to augmenting the docstring for COMPONENT-RELATIVE-PATHNAME? Currently it's: "Extracts the relative pathname applicable for a particular component." How about something like: "Returns a pathname for the component argument relative to the pathname of that component's parent."

Re: [asdf-devel] patch for component-relative-pathname

On 2/19/10 Feb 19 -1:10 PM, Faré wrote: > On 19 February 2010 10:50, Robert Goldman wrote: >> Would anyone object to augmenting the docstring for >> COMPONENT-RELATIVE-PATHNAME? >> >> Currently it's: >> >> "Extracts the relative pathname applic

Re: [asdf-devel] patch for component-relative-pathname

On 2/19/10 Feb 19 -2:19 PM, Faré wrote: >> 2. SPLIT-PATH-STRING --- this is the one I think might need a ticket. >> I confess I'm bamboozled by this one. It's called on (component-name >> component), not on a pathname. Can you explain why the COMPONENT-NAME >> would end up being a string that lo

Re: [asdf-devel] patch for component-relative-pathname

On 2/19/10 Feb 19 -2:19 PM, Faré wrote: >> 2. SPLIT-PATH-STRING --- this is the one I think might need a ticket. >> I confess I'm bamboozled by this one. It's called on (component-name >> component), not on a pathname. Can you explain why the COMPONENT-NAME >> would end up being a string that lo

Re: [asdf-devel] patch for component-relative-pathname

On 2/21/10 Feb 21 -6:35 PM, james anderson wrote: > a question: > >> On 2/19/10 Feb 19 -2:19 PM, Faré wrote: 2. SPLIT-PATH-STRING --- this is the one I think might need a ticket. I confess I'm bamboozled by this one. It's called on (component- name component), not on

Re: [asdf-devel] patch for component-relative-pathname

On 2/21/10 Feb 21 -11:16 PM, Faré wrote: >> 1. SPLIT-PATH-STRING is not an ideal name. SPLIT-PATH-STRING is /not/ >> used on paths, it is used on /names/ (in the ASDF sense of these terms). >> An unwary reader of this code might try to apply it to a pathname (as I >> originally thought), where i

Re: [asdf-devel] patch for component-relative-pathname

On 2/22/10 Feb 22 -3:37 AM, james anderson wrote: > good morning; > > On 2010-02-22, at 01:41 , Robert Goldman wrote: > >> On 2/21/10 Feb 21 -6:35 PM, james anderson wrote: >>> a question: >>> >> >>>> [...] >>>> >> >

Re: [asdf-devel] patch for component-relative-pathname

On 2/22/10 Feb 22 -10:02 AM, Faré wrote: >> I am inclined to agree. I'd be happier if we could just say something like >> >> (:file "foo" :relative-directory "bar") >> >> instead of >> >> (:file "bar/foo") >> > Why? You're just moving the complexity around, > without simplifying the overall design

Re: [asdf-devel] default source registry...

On 2/22/10 Feb 22 -11:23 AM, Faré wrote: > Should we base our search path on the XDG Base Directory Specification? > http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html > To the point of actually using getenv to get these search paths? > > I say we should. Only to the extent t

Re: [asdf-devel] upgradability with ECL

On 2/24/10 Feb 24 -6:02 AM, Tobias C. Rittweiler wrote: > > Current ECL HEAD comes with asdf version "1.604", but trying to load > upstreams asdf.lisp won't work because of > > "A package with the name ASDF-EXTENSIONS already exists." > > Indeed, CLHS DEFPACKAGE says > > If one of the suppl

Re: [asdf-devel] [PATCH] add &allow-other-keys to LOAD-SYSTEM, COMPILE-SYSTEM, TEST-SYSTEM

On 2/24/10 Feb 24 -5:54 AM, Tobias C. Rittweiler wrote: > > Although the way to extend operations by additional initargs is somewhat > cumbersome, it's possible. Unfortunately, the sugar forms LOAD-SYSTEM, > COMPILE-SYSTEM, and TEST-SYSTEM do not take additional initargs. I see that the docstring

Re: [asdf-devel] [PATCH] add &allow-other-keys to LOAD-SYSTEM, COMPILE-SYSTEM, TEST-SYSTEM

On 2/24/10 Feb 24 -9:00 AM, Tobias C. Rittweiler wrote: > Robert Goldman writes: > >> On 2/24/10 Feb 24 -5:54 AM, Tobias C. Rittweiler wrote: >>> >>> Although the way to extend operations by additional initargs is somewhat >>> cumbersome, it's possible

Re: [asdf-devel] [PATCH] add &allow-other-keys to LOAD-SYSTEM, COMPILE-SYSTEM, TEST-SYSTEM

On 2/24/10 Feb 24 -9:09 AM, james anderson wrote: > > i wondered that. looks like markdown link-w/o-the-reference-id > syntax. (is supported by docudown?) > but then, it's not clear were it finds it's definition. (work-in- > progress?) > > which brings up larger questions. > as i was writing d

Re: [asdf-devel] [PATCH] add &allow-other-keys to LOAD-SYSTEM, COMPILE-SYSTEM, TEST-SYSTEM

On 2/24/10 Feb 24 -9:22 AM, Tobias C. Rittweiler wrote: > Robert Goldman > writes: > > Actually, &allow-other-keys would not be necessary if these weren't > normal functions but generic functions. Then methods can add valid > keywords. And there's a programma

Re: [asdf-devel] [PATCH] add &allow-other-keys to LOAD-SYSTEM, COMPILE-SYSTEM, TEST-SYSTEM

On 2/24/10 Feb 24 -9:35 AM, james anderson wrote: > > On 2010-02-24, at 16:19 , Robert Goldman wrote: > >> On 2/24/10 Feb 24 -9:09 AM, james anderson wrote: >>> >>> i wondered that. looks like markdown link-w/o-the-reference-id >>> syntax. (is supported

Re: [asdf-devel] Changes to ASDF for LW6

On 2/26/10 Feb 26 -9:00 AM, David McClain wrote: > No, I take a stock LW6 system and want to load up the ASDF package as soon as > possible, so that I can then use ASDF to load in systems. When I take a look > at the PACKAGE-USE-LIST of CL-USER, it shows COMMON-LISP, > HARLEQUIN-COMMON-LISP, and

Re: [asdf-devel] Changes to ASDF for LW6

ses the semantics is "-exactly" or "-only" rather than > "ensure-". > > On 2010-02-26, at 16:17 , Robert Goldman wrote: > >> On 2/26/10 Feb 26 -9:00 AM, David McClain wrote: >>> [...] >> >> [...] > ... > > > _

Re: [asdf-devel] Changes to ASDF for LW6

On 2/26/10 Feb 26 -10:52 AM, james anderson wrote: > hmmm... > > On 2010-02-26, at 17:42 , Robert Goldman wrote: > >> On 2/26/10 Feb 26 -10:17 AM, james anderson wrote: >>> good evening; >>> >>> as an aside, in light of these changes. >>>

Re: [asdf-devel] Changes to ASDF for LW6

m Lispworks. > > What can I say here? The LW6 system behaves the way it does, right or wrong, > and my changes seemed to be the least needed to get things rolling again. > > - DM > > On Feb 26, 2010, at 08:17 AM, Robert Goldman wrote: > >> On 2/26/10 Feb 26 -9:00 A

Re: [asdf-devel] Changes to ASDF for LW6

, lispworks site >>> installation, or the individual runtime has arranged package and >>> symbol visibility such that symbols from some lispworks extension >>> package are visible through the common-lisp package, as that is the >>> only package from which :asdf-extension

[asdf-devel] ASDF testing

Any chance you could run the ASDF tests (with run-tests.sh) on Lispworks? If you'd be willing to do this, feel free to call on me for any assistance. I can't figure out how to run this with my personal edition: as far as I can tell, one needs to use save-image to create an image that can be used

Re: [asdf-devel] ASDF testing

On 2/27/10 Feb 27 -8:16 AM, David McClain wrote: > Hello Robert, > > I took a look at your test shell script (run-tests.sh) and made the > adjustment for running my saved image named lwm64. > > After some tests I found that the Lisp image has its working directory > set to the same directory from

Re: [asdf-devel] ASDF testing

On 2/27/10 Feb 27 -5:13 PM, David McClain wrote: > Hi Robert, > >> E.g., in ACL, we start this up as something like >> >> alisp -e '(load "test/compile-asdf.lisp")' >> >> and for SBCL >> >> sbcl --eval '(load "test/compile-asdf.lisp")' >> >> Is there some equivalent to -e/--eval that works for lis

Re: [asdf-devel] never ending component relative pathnames

On 3/5/10 Mar 5 -12:06 PM, james anderson wrote: > good evening; > > on the occasion of pushing de.setf.graphics down the wire, when i > built it for ccl/sbcl i did an obligatory pull on asdf and observe > that something changed in the treatment of modules' component > relative pathnames. wi

<    1   2   3   4   5   6   7   8   9   10   >