asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] maintaining the ASDF web site
by Robert Goldman 23 Mar '10

23 Mar '10

OK, I've looked at this, and I'm afraid I am not going to take this on in its current form. If someone else would be so kind as to wrangle the markdown and grok the scripts, that's fine. If after some time, no one else expresses a willingness to do this, then I will try to do some of it, but I hereby put the community on notice: I don't know markdown, and I'm not going to learn markdown. If this is left to me, the markdown will go away, and HTML will gradually take its place. HTML is ugly, annoying, difficult, etc., but it has the immense advantage, to me, that I know it, and I know the toolchain (which is basically emacs + my browser). So there it is --- anyone interested in taking this over? Best, r

2 1

[asdf-devel] Please hands off the manual...
by Robert Goldman 23 Mar '10

23 Mar '10

I would like to move the manual into a newly-created subdirectory per tcr's suggestion. I want to minimize merging issues, so please commit any changes you might have; I will do the directory juggling this afternoon. Thanks! r

1 0

[asdf-devel] Package manipulation [ was ASDF traverse changed behavior? ]
by Juan Jose Garcia-Ripoll 23 Mar '10

23 Mar '10

On Thu, Mar 18, 2010 at 1:36 AM, Robert Goldman <rpgoldman(a)sift.info> wrote: > Is it possible that somehow the compilation of asdf-ecl is recording > some information about the package that is somehow damaged by the > package surgery? > I will dig into that later during the weekend. I think the point is something we discussed long at the ECL mailing list, namely that symbols are NOT created as a compiled file is run. Symbols are constants and as such a compiler is allowed to coalesce all references to symbols in the same compiled file. The problem would thus be the following. The compiler loads the file, it resolves all references to symbols, storing them in the array of constants, including PERFORM. The code is executed. PERFORM is uninterned and a new symbol is created. We reach the DEFMETHOD forms, which now are executed but since they reference the *old* version of the symbol, the method is installed with the wrong name in the wrong generic function. In other words, one can not expect the side effects that operations have in packages work the same for a compiled and a source file. It is just as if you expect that the side effects that aare caused by changing the readtable would also affect the way a cmpiled file behave. Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

4 9

[asdf-devel] something in recent commit causes ACL testing to go into an infinite loop
by Robert Goldman 23 Mar '10

23 Mar '10

Now when I run the tests on allegro I get a FILE-INCOMPATIBLE-FASL-ERROR on file3.fasl. ASDF then tries to invoke the ASDF:RETRY restart. Then it gets the FILE-INCOMPATIBLE-FASL-ERROR on file3.fasl. ASDF then tries to invoke the ASDF:RETRY restart. Then .... This happened when I tested with 8.2 after testing on 8.1. When I run this interactively, with the -d option on the command line, I can invoke a restart which recompiles the file in question, and the tests complete successfully (21 of 21 successful). So this suggests that there is a bug in the ASDF:RETRY restart.

2 6

[asdf-devel] How is the website maintained?
by Robert Goldman 23 Mar '10

23 Mar '10

How does one change the website? Is the stuff in the repository still live? Can we just change git contents and have it automagically updated on the website? I have posted some tickets about this because I don't know how the website is updated. I'd knock some of them off if someone would hand me a clue on a silver platter... thanks, r

2 1

[asdf-devel] ASDF works again with ECL (also a question)
by Juan Jose Garcia-Ripoll 23 Mar '10

23 Mar '10

Thansk for the latest changes, they work like a charm now. I have done something which I do not know whether it is a desired protocol. Namely I have submitted patches for asdf-ecl.lisp using launchpad. I did this because I always found it more convenient to have a look at the ECL bug/patch tracker thank keeping track of the emails with patches and remember whether they were committed. Is it ok? Should I continue doing so with the following patches, such as test cases, etc? Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

2 4

[asdf-devel] Minor comments regarding manual on HEAD
by Tobias C. Rittweiler 21 Mar '10

21 Mar '10

* README should say how to build the manual * That said, how is the user supposed to build the manual? There does not seem to be any rule for it in the Makefile. * texipdf asdf.texinfo resulted in an error; an asdf.pdf was produced nontheless. See PS for transcript. * the manual should perhaps start with a "What's new" section which mostly contains links to the appropriate pages. -T. PS. tcr@thaleron:~/src/from-upstream/asdf$ texi2pdf asdf.texinfo This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) file:line:error style messages enabled. %&-line parsing enabled. entering extended mode (./asdf.texinfo (/usr/share/texmf/tex/texinfo/texinfo.tex Loading texinfo [version 2008-04-18.10]: pdf, fonts, page headings, tables, conditionals, indexing, sectioning, toc, environments, defuns, macros, cross references, insertions, (/usr/share/texmf-texlive/tex/generic/epsf/epsf.tex This is `epsf.tex' v2.7.3 <23 July 2005> ) localization, formatting, and turning on texinfo input format.) (./asdf.aux) [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2] (./asdf.toc) [-1] (./asdf.toc) (./asdf.toc) Chapter 1 l.149: Undefined cross reference `The object model of ASDF-pg'. Chapter 2 [1] [2] l.288: Undefined cross reference `Getting the latest version-snt'. l.288: Undefined cross reference `Getting the latest version-snt'. l.288: Undefined cross reference `Getting the latest version-pg'. Chapter 3 [3] l.309: Undefined cross reference `Controlling where ASDF searches for systems-s nt'. l.309: Undefined cross reference `Controlling where ASDF searches for systems-s nt'. l.309: Undefined cross reference `Controlling where ASDF searches for systems-p g'. Underfull \hbox (badness 3271) in paragraph at lines 311--318 []@textrm The de-fault lo-ca-tion for a user to in-stall Com-mon Lisp soft-ware is un-der [4] l.458: Undefined cross reference `Controlling where ASDF saves compiled files-s nt'. l.458: Undefined cross reference `Controlling where ASDF saves compiled files-s nt'. l.458: Undefined cross reference `Controlling where ASDF saves compiled files-p g'. Underfull \hbox (badness 6641) in paragraph at lines 460--468 []@textrm The sim-plest way to add a trans-la-tion to your search path, say fro m Underfull \hbox (badness 4846) in paragraph at lines 460--468 @textrm `@texttt /foo/bar/baz/quux/[]@textrm '[] to `@texttt /where/i/want/my/f asls/[]@textrm '[] is to cre-ate the di-rec-tory [5] Underfull \hbox (badness 3492) in paragraph at lines 484--490 []@textrm Note that your Op-er-at-ing Sys-tem dis-tri-bu-tion or your sys-tem a d-min-is-tra-tor Underfull \hbox (badness 2229) in paragraph at lines 484--490 @textrm may al-ready have con-fig-ured trans-la-tions for you. In ab-sence of a ny con-fig-u- Underfull \hbox (badness 2662) in paragraph at lines 484--490 @textrm ra-tion, the de-fault is to redi-rect ev-ery-thing un-der an implementa tion-dependent Underfull \hbox (badness 10000) in paragraph at lines 484--490 @textrm sub-di-rec-tory of `@texttt ~/.cache/common-lisp/[]@textrm '[]. Once ag ain, see the doc-u-ment Chapter 4 [6] Chapter 5 [7] [8] Overfull \hbox (32.02371pt too wide) in paragraph at lines 766--766 [][] | [9] [10] Underfull \hbox (badness 2951) in paragraph at lines 843--847 []@textrm To use log-i-cal path-names, you will have to pro-vide a path-name ob -ject as a [11] Chapter 6 [12] ./asdf.texinfo:1006: Argument of & has an extra }. <inserted text> @par <to be read again> } @tclose ...n @rawbackslash @plainfrenchspacing #1} @null @codex #1->@tclose {#1} @endgroup <argument> ...eration} @var {system} @code {&rest} @var {initargs} @unskip @defunargs ...ar @font =0 @let @var =@ttslanted #1 @sl @hyphenchar @font =45 ... l.1006 ...@var{system} @code{&rest} @var{initargs} ?

4 6

[asdf-devel] ASDF and source file extensions
by Juan Jose Garcia-Ripoll 19 Mar '10

19 Mar '10

In a system such as (defsystem :foo :component ((:file "foo"))) where foo.lsp exists and is recognized by the lisp implementation as a valid source file (ECL), ASDF imposes the file extension "lisp". Furthermore, adding our own extension (defsystem :foo :component ((:file "foo.lsp"))) does not work and one has to resort to an EQL-specialized method (ugly!) I have submitted a small patch that adds a new option :type that can be used with components of the type source-file https://bugs.launchpad.net/asdf/+bug/542222 -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://tream.dreamhosters.com

1 0

[asdf-devel] quick launchpad question
by Robert Goldman 19 Mar '10

19 Mar '10

would it be possible to also add a "version 3" milestone so that we could explicitly push stuff /out/ of version 2? Right now it seems like there's no way of telling the difference between "unmilestoned" and "milestoned out of version 2". But my ignorance of launchpad is near complete, so it is possible I am missing something. thanks, r

2 1

[asdf-devel] Preparation for ASDF 2: launchpad
by Robert Goldman 19 Mar '10

19 Mar '10

Would it be possible for someone to add an "ASDF 2 release" (or something equivalent) milestone to launchpad? As we get close to this point, it would be nice to triage the launchpad tickets either into our out of ASDF 2. thanks, r

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel