asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] ASDF configuration
by Faré 19 Jan '10

19 Jan '10

Dear ASDF-interested hackers, I've cleaned up my code for ASDF configuration and committed it to my repo. http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git Documentation is currently in README.source-registry there. While discussing with Peter Van Eynde and James Knight regarding debian common-lisp-controller bug 560781 I came to the conclusion that we probably want something similar for ASDF-BINARY-LOCATIONS. If someone who has hacked ABL more than I understands the issues, I'd be grateful to discuss with him and flesh out an implementation of such a configuration (maybe refactoring the code to share stuff with the current parser). Are there any other parts of ASDF that require similar configuration? In any case, in my repository, I bumped the version to 1.500 to signal the significance of recent changes. I will merge and release next week if no one sees any objection. When all the configuration we need is ready and debugged, I'd like to release a version 2.0 and start peddling ASDF upgrades to all Lisp implementation vendors. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The probability of the people in power being individuals who would dislike the possession and exercise of power is on a level with the probability that an extremely tender-hearted person would get the job of whipping-master on a slave plantation. — Frank H. Knight

1 0

[asdf-devel] asdf.texinfo version 1.375 has errors
by Peter Van Eynde 19 Jan '10

19 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, While trying to build a new Debian package I get the following errors: > $ makeinfo --verbose asdf.texinfo > makeinfo (GNU texinfo) 4.13 > Making info file `asdf.info' from `asdf.texinfo'. > Formatting node Top... > Formatting node Introduction... > Formatting node Using asdf to load systems... > Formatting node Defining systems with defsystem... > Formatting node The defsystem form... > Formatting node A more involved example... > Formatting node The defsystem grammar... > Formatting node Other code in .asd files... > Formatting node The object model of asdf... > Formatting node Operations... > Formatting node Predefined operations of asdf... > Formatting node Creating new operations... > Formatting node Components... > Formatting node Common attributes of components... > Formatting node Pre-defined subclasses of component... > Formatting node Creating new component types... > Formatting node Controlling where ASDF saves compiled files... > Formatting node Error handling... > Formatting node Compilation error and warning handling... > Formatting node Miscellaneous additional functionality... > Formatting node Getting the latest version... > Formatting node FAQ... > Formatting node TODO list... > Formatting node missing bits in implementation... > Formatting node Inspiration... > Formatting node Concept Index... > Formatting node Function and Class Index... > Formatting node Variable Index... > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1301: Prev field of node `FAQ' not pointed to. > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1451: This node (missing bits in implementation) has the bad Next. > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1281: Node `Getting the latest version' lacks menu item for `FAQ' despite being its Up target. > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1281: Next field of node `Getting the latest version' not pointed to (perhaps incorrect sectioning?). > /home/pvaneynd/fakeroot/clean/git/cl-asdf//asdf.texinfo:1301: This node (FAQ) has the bad Prev. This is fixed with the trivial patch: > diff --git a/asdf.texinfo b/asdf.texinfo > index 3d379e4..ddefe01 100644 > --- a/asdf.texinfo > +++ b/asdf.texinfo > @@ -1298,7 +1298,7 @@ You will find the above referenced tags in this repository. > Discussion of ASDF development is conducted on the mailing list > @kbd{asdf-devel@@common-lisp.net}. > > -@node FAQ, TODO list, missing bits in implementation, Getting the latest version, Top > +@node FAQ, TODO list, Getting the latest version, Top > @comment node-name, next, previous, up > @chapter FAQ See also http://git.debian.org/?p=pkg-common-lisp/cl-asdf.git;a=commit;h=ea3aa53b623… Groetjes, Peter - -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson| -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJLVVNrAAoJEB4VNT76eIlawy4QAKUEa/QOLfuKZCvCthVmPj0p 6PuLzfmpGM7jJ+7fsx0WQEAHgE/9RkFL9emC8diAPRiAXCBdB1ypZ9uciniYtc1Y x7/5QL2vpJH9NYmMlK6xKE2l0doYAe2sgSSt6BzvFpvXdnv7mt1Il5CmN93RtJQI 9RUm7aei+uqN1n+tojNw37OMa0YC2x/hSdjPdqTyDqm3gDa0kUYXDfTHomlcBBRP tavFqwLvqfZ3LlbIiObJqCu6eh35gpCW6O1AmdG/dXAGfzjoKV7tlR8nvfIoCBsu P6XUi32P0K0H2fGfJ55ETjszJSwb735aWvAlaNHuZV6Z7xa5uLKJ9FTraY+4K2i6 j7swacO/NJla3m8eOVaZF+6wZEuiWZpODSH0u6eo0JSlCX6OpGO41q4uQ6iJA7Pz nj5e0kEejnamk9IfLVAFPL8kpz7HfxreEVGr83iP4/At6JKOAO3YbOfwcL0/po51 2b+eqkZNsZqmolrJK0hQqIN5A0LhuyQ4CVr/o9xulx08MZkHCnNYC7t2cLBMWBjG hYx5exF2iqlnOlF7IZ74qdjRye9ykZ8aOs24zvSX6gWwzfyniLZoEYuH8sNrEWD1 queXBogs4Wqmda50gICYw6ADmplcCpQfnI2/f+DfjH6JSnxv4dbYcCD7hqwrlkS3 KDuVd4nSxQ3BhfQ2NSi3 =0l7y -----END PGP SIGNATURE-----

1 0

[asdf-devel] ASDF configuration through files
by Faré 18 Jan '10

18 Jan '10

Dear ASDF hackers, my experimental repository at http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git contains some (fugly) code to address the configurability issue: https://bugs.launchpad.net/asdf/+bug/485918 I won't release the code until I clean it up somewhat, but I'm already requesting comments. The idea is that you should configure your paths through user and system files, more or less as described in a previous mailing-list post: http://common-lisp.net/pipermail/asdf-devel/2009-December/000580.html This hooks into the asdf sysdef search mechanism in a way that takes precedence over the current *central-registry* but falls back to it when systems are not found. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The difference between a programmer and a user, is that the programmer knows there is no difference between using and programming. — Faré

2 3

[asdf-devel] git resources
by Daniel Herring 17 Jan '10

17 Jan '10

Hi all, I just found this list of resources. http://techbase.kde.org/Getting_Started/Sources/Amarok_Git_Tutorial#Recomme… It might be good to add some of them to ASDF's resource list. - Daniel

1 0

[asdf-devel] tab-blocking commit hook
by dherring＠tentpost.com 15 Jan '10

15 Jan '10

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 in (the context of) another modification. Here's an example stopped commit. "" Error: This git repository disallows the #\Tab character in lisp files. Only spaces should be used for indenting lisp code. In emacs, 'M-x untabify' and (setq indent-tabs-mode nil) may help. First offending file and lines: test.asd + this is a tab "" To install, simply copy this script to .git/hooks/pre-commit and set the executable bit. It might also be good to put a copy somewhere permanent so others can install it to their local repositories. Later, Daniel

4 5

[asdf-devel] Released ASDF 1.375
by Faré 14 Jan '10

14 Jan '10

Seeing that ASDF hasn't changed much in the last few weeks, I released 1.375, which contains some documentation changes by Robert Goldman, and a patch by Samium Gromoff. Note once again that while willing to accept patches and release promptly (or not so promptly, it seems, if you don't consider it released when in my non-official repository), I am not interested in actually fixing most of the bugs reported on the site. Don't wait for me to fix them. I am however still working to make sure that ASDF can be self-upgraded and automatically configured. http://common-lisp.net/project/asdf/ http://common-lisp.net/gitweb?p=projects/asdf/asdf.git [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] If normative judgments cannot be rational, then science is actually useless. — François Guillaumat

1 0

[asdf-devel] SRFI 103
by Daniel Herring 10 Jan '10

10 Jan '10

SRFI 103 is defines a library system for R6RS scheme. http://srfi.schemers.org/srfi-103/ It only covers a subset of ASDF's functionality, but some of the design decisions may still apply. - Daniel

1 0

[asdf-devel] PERFORM COMPILE-OP diagnostics
by Tobias C. Rittweiler 04 Jan '10

04 Jan '10

The code in question is (multiple-value-bind (output warnings-p failure-p) (apply #'compile-file source-file :output-file output-file (compile-op-flags operation)) (when warnings-p (case (operation-on-warnings operation) (:warn (warn "~@<COMPILE-FILE warned while performing ~A on ~A.~:>" operation c)) (:error (error 'compile-warned :component c :operation operation)) (:ignore nil))) (when failure-p (case (operation-on-failure operation) (:warn (warn "~@<COMPILE-FILE failed while performing ~A on ~A.~:>" operation c)) (:error (error 'compile-failed :component c :operation operation)) (:ignore nil))) (unless output (error 'compile-error :component c :operation operation))) I don't like that behaviour at all for the following reasons: a) WARNINGS-P is T even if only a style-warning is signaled. OPERATION-ON-WARNINGS is :WARN by default, so a style-warning results in a gratuitous "COMPILE-FILE warned" message. b) If COMPILE-FILE warned, FAILURE-P is T. This means if a warning during compilation is signaled, ASDF will display a "COMPILE-FILE failed" message -- which is technically correct, but only for some obtusive meaning of "failed". I'd rather have something like Slime's compilation statistics: The operation #<COMPILE-OP ...> on #<CL-SOURCE-FILE ...> resulted in N1 style-warnings, N2 warnings, N3 non-fatal errors and 1 fatal error. # iff OUTPUT == NIL The operation failed at creating a fasl file. Aborting.. <..entering debuger..> Or The operation #<COMPILE-OP ...> on #<CL-SOURCE-FILE ...> resulted in N1 style-warnings, N2 warnings, N3 non-fatal errors The operation succeeded at creating a fasl file. Suggestions? -T.

2 3

Re: [asdf-devel] 1.374
by Samium Gromoff 22 Dec '09

22 Dec '09

Fare, Please consider the patch in the 'missing-definition' branch in git://git.feelingofgreen.ru/asdf regards, Samium Gromoff -- _deepfire-at-feelingofgreen.ru O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

3 5

[asdf-devel] website
by Tobias C. Rittweiler 21 Dec '09

21 Dec '09

Hi Gary, What are the required steps to change the Website? -T.

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