asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

Issues with new testing scripts
by Robert Goldman 03 Jan '16

03 Jan '16

I'm having two issues with the new testing scripts: 1. The testing code is bleeding quicklisp into context: make test ./make.sh l='' L='' u='' U='' v='' s='' t='' test > Error: System "cl-scripting" not found > While executing: (:INTERNAL QUICKLISP-CLIENT::RECURSE QUICKLISP-CLIENT::COMPUTE-LOAD-STRATEGY), in process listener(1). > Type :GO to continue, :POP to abort, :R for a list of available restarts. > If continued: Try again > Type :? for other options. 1 > I *definitely* did not ask to be using quicklisp when testing. This error arises inside (LOAD-SYS "asdf-tools"), which is redirected to use quicklisp: (defun load-sys (system) (if (featurep :quicklisp) (let ((*standard-output* (make-broadcast-stream))) ;; be quiet (symbol-call :ql :quickload system)) (load-system system :verbose nil))) This is done by tools/load-asdf.lisp AFAICT, this is done UNCONDITIONALLY BY LOAD-AND-CONFIGURE-ASDF This should not be. The user should get quicklisp only upon request: we added the dependencies to ext/ in order to make the ASDF distribution free-standing and avoid the quicklisp requirement. In my case, I use quicklisp only sometimes, and never yet with CCL, so having the ASDF test script go poking around for a QL installation and firing it up without asking me was problematic. Particularly problematic was that there's no (apparent) way to STOP the ASDF scripts from doing this. For now I am going to push a modification that comments out TRY-LOAD-QUICKLISP from LOAD-AND-CONFIGURE-ASDF. I have no objection to a patch that provides an *explicit option* to load from QL, but it must be an option, and it must not be the default. Frankly, even then I'm not excited about it. I don't want to have bugreports to ASDF that are caused by issues in Quicklisp. I'd rather people stick to using the dependencies in our submodules. 2. This was just a nuisance: three new submodules have been added, and "git submodule init" must be re-run when that happens. I have no idea why the git maintainers thought that a call to git submodule update should quietly fail to update un-initialized submodules (fail to update yes, QUIETLY fail to update, no). But going forward we need to trumpet any changes to the submodules because of this attribute of git.... Cheers, r

4 17

Can no longer test on Windows: failure to build doc causes failure to build ASDF
by Robert Goldman 31 Dec '15

31 Dec '15

I was trying to run the tests on Windows, and this triggers make asdf.pdf. My windows box does not have texi2pdf. It seems inappropriate that in order to test ASDF you have to build the manual. Note that this seems to have changed from before minimakefile -- I used to be able to run the tests on Windows. Fare -- any idea what changed to break this? thanks, r

2 2

Regression in 9933b3078f35be0198dc37d1b0d914797c5802d7
by Stelian Ionescu 14 Dec '15

14 Dec '15

Commit "Avoid calling SUBTYPEP in ANSI-STREAM-{READ,WRITE}-SEQUENCE" causes the following error when compiling Quicklisp's package.lisp. I'm not sure what's happening, though, because if I start SBCL with --no-userinit and compile that file manually, I don't see the error. debugger invoked on a TYPE-ERROR in thread #<THREAD "main thread" RUNNING {10039ED6B3}>: The value NIL is not of type SB-C::COMPILER-ERROR-CONTEXT. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [RETRY ] Retry compiling #<CL-SOURCE-FILE "quicklisp" "package">. 1: [ACCEPT ] Continue, treating compiling #<CL-SOURCE-FILE "quicklisp" "package"> as having been successful. 2: Retry ASDF operation. 3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 4: [RETRY ] Retry EVAL of current toplevel form. 5: [CONTINUE ] Ignore error and continue loading file "/home/hechee/lisp/quicklisp/setup.lisp". 6: [ABORT ] Abort loading file "/home/hechee/lisp/quicklisp/setup.lisp". 7: Retry EVAL of current toplevel form. 8: Ignore error and continue loading file "/home/hechee/.cl-init/asdf-init.lisp". 9: Abort loading file "/home/hechee/.cl-init/asdf-init.lisp". 10: Retry EVAL of current toplevel form. 11: Ignore error and continue userinit file "/home/hechee/.sbclrc". 12: Abort userinit file "/home/hechee/.sbclrc". 13: Skip to toplevel READ/EVAL/PRINT loop. 14: [EXIT ] Exit SBCL (calling #'EXIT, killing the process). ((LAMBDA (UIOP/LISP-BUILD::FROB) :IN UIOP/LISP-BUILD::REIFY-UNDEFINED-WARNING) NIL) source: #S(SB-IMPL::COMMA :EXPR (SB-C::COMPILER-ERROR-CONTEXT-ENCLOSING-SOURCE FROB) :KIND 0) 0] backtrace Backtrace for: #<SB-THREAD:THREAD "main thread" RUNNING {10039ED6B3}> 0: ((LAMBDA (UIOP/LISP-BUILD::FROB) :IN UIOP/LISP-BUILD::REIFY-UNDEFINED-WARNING) NIL) 1: (UIOP/LISP-BUILD::REIFY-UNDEFINED-WARNING #<SB-C::UNDEFINED-WARNING :DEFAULT>) 2: (UIOP/LISP-BUILD:REIFY-DEFERRED-WARNINGS) 3: ((LAMBDA NIL :IN UIOP/LISP-BUILD:SAVE-DEFERRED-WARNINGS)) 4: ((LAMBDA NIL :IN UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX)) 5: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (LAMBDA NIL :IN UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX) {100FF5BB1B}>) 6: (UIOP/STREAM:CALL-WITH-SAFE-IO-SYNTAX #<CLOSURE (LAMBDA NIL :IN UIOP/LISP-BUILD:SAVE-DEFERRED-WARNINGS) {100FF5BAFB}> :PACKAGE :CL) 7: (UIOP/LISP-BUILD:SAVE-DEFERRED-WARNINGS #P"/home/hechee/.cache/common-lisp/sbcl-1.3.1.126-b8a086c89589-linux-x64/home/hechee/lisp/quicklisp/quicklisp/package.sbcl-warnings") 8: ((LAMBDA NIL :IN UIOP/LISP-BUILD::CALL-WITH-SAVED-DEFERRED-WARNINGS)) 9: ((FLET SB-C::WITH-IT :IN SB-C::%WITH-COMPILATION-UNIT)) 10: (UIOP/LISP-BUILD::CALL-WITH-SAVED-DEFERRED-WARNINGS #<CLOSURE (LAMBDA NIL :IN UIOP/LISP-BUILD:COMPILE-FILE*) {100FEDFDCB}> #P"/home/hechee/.cache/common-lisp/sbcl-1.3.1.126-b8a086c89589-linux-x64/home/hechee/lisp/quicklisp/quicklisp/package.sbcl-warnings" :SOURCE-NAMESTRING "/home/hechee/lisp/quicklisp/quicklisp/package.lisp") 11: ((LAMBDA (UIOP/LISP-BUILD::INPUT-FILE) :IN UIOP/LISP-BUILD:COMPILE-FILE*) #P"/home/hechee/lisp/quicklisp/quicklisp/package.lisp") 12: (UIOP/PATHNAME:CALL-WITH-ENOUGH-PATHNAME #P"/home/hechee/lisp/quicklisp/quicklisp/package.lisp" NIL #<CLOSURE (LAMBDA (UIOP/LISP-BUILD::INPUT-FILE) :IN UIOP/LISP-BUILD:COMPILE-FILE*) {100FEDFD8B}>) 13: (UIOP/LISP-BUILD:COMPILE-FILE* #P"/home/hechee/lisp/quicklisp/quicklisp/package.lisp" :OUTPUT-FILE #P"/home/hechee/.cache/common-lisp/sbcl-1.3.1.126-b8a086c89589-linux-x64/home/hechee/lisp/quicklisp/quicklisp/package.fasl" :EXTERNAL-FORMAT :UTF-8 :WARNINGS-FILE #P"/home/hechee/.cache/common-lisp/sbcl-1.3.1.126-b8a086c89589-linux-x64/home/hechee/lisp/quicklisp/quicklisp/package.sbcl-warnings") 14: ((LAMBDA (&REST ASDF/LISP-ACTION:FLAGS) :IN ASDF/LISP-ACTION:PERFORM-LISP-COMPILATION)) 15: (UIOP/UTILITY:CALL-FUNCTION FUNCALL #<CLOSURE (LAMBDA (&REST ASDF/LISP-ACTION:FLAGS) :IN ASDF/LISP-ACTION:PERFORM-LISP-COMPILATION) {100FEC7AEB}>) 16: (UIOP/LISP-BUILD:CALL-AROUND-HOOK NIL #<CLOSURE (LAMBDA (&REST ASDF/LISP-ACTION:FLAGS) :IN ASDF/LISP-ACTION:PERFORM-LISP-COMPILATION) {100FEC7AEB}>) 17: ((:METHOD ASDF/LISP-ACTION:CALL-WITH-AROUND-COMPILE-HOOK (ASDF/COMPONENT:COMPONENT T)) #<ASDF/LISP-ACTION:CL-SOURCE-FILE "quicklisp" "package"> #<CLOSURE (LAMBDA (&REST ASDF/LISP-ACTION:FLAGS) :IN ASDF/LISP-ACTION:PERFORM-LISP-COMPILATION) {100FEC7AEB}>) [fast-method] 18: (ASDF/LISP-ACTION:PERFORM-LISP-COMPILATION #<ASDF/LISP-ACTION:COMPILE-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "quicklisp" "package">) 19: ((:METHOD ASDF/ACTION:PERFORM (ASDF/LISP-ACTION:COMPILE-OP ASDF/LISP-ACTION:CL-SOURCE-FILE)) #<ASDF/LISP-ACTION:COMPILE-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "quicklisp" "package">) [fast-method] 20: ((SB-PCL::EMF ASDF/ACTION:PERFORM) #<unused argument> #<unused argument> #<ASDF/LISP-ACTION:COMPILE-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "quicklisp" "package">) 21: ((:METHOD ASDF/ACTION:PERFORM-WITH-RESTARTS (T T)) #<ASDF/LISP-ACTION:COMPILE-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "quicklisp" "package">) [fast-method] 22: ((FLET CALL-NEXT-METHOD :IN "/home/hechee/work/src/asdf/build/asdf.lisp")) 23: ((:METHOD ASDF/ACTION:PERFORM-WITH-RESTARTS :AROUND (T T)) #<ASDF/LISP-ACTION:COMPILE-OP > #<ASDF/LISP-ACTION:CL-SOURCE-FILE "quicklisp" "package">) [fast-method] 24: ((:METHOD ASDF/PLAN:PERFORM-PLAN (LIST)) ((#1=#<ASDF/LISP-ACTION:PREPARE-OP > . #<ASDF/SYSTEM:SYSTEM #2="quicklisp">) (#1# . #3=#<ASDF/LISP-ACTION:CL-SOURCE-FILE #2# "package">) (#4=#<ASDF/LISP-ACTION:COMPILE-OP > . #3#) (#5=#<ASDF/LISP-ACTION:LOAD-OP :VERBOSE NIL> . #3#) (#1# . #6=#<ASDF/LISP-ACTION:CL-SOURCE-FILE #2# "utils">) (#4# . #6#) (#5# . #6#) (#1# . #7=#<ASDF/LISP-ACTION:CL-SOURCE-FILE #2# "config">) (#4# . #7#) (#5# . #7#) (#1# . #8=#<ASDF/LISP-ACTION:CL-SOURCE-FILE #2# "impl">) (#4# . #8#) ...) :FORCE NIL) [fast-method] 25: ((FLET CALL-NEXT-METHOD :IN "/home/hechee/work/src/asdf/build/asdf.lisp")) 26: ((LAMBDA NIL :IN ASDF/PLAN:PERFORM-PLAN)) 27: ((FLET SB-C::WITH-IT :IN SB-C::%WITH-COMPILATION-UNIT)) 28: ((:METHOD ASDF/PLAN:PERFORM-PLAN :AROUND (T)) ((#1=#<ASDF/LISP-ACTION:PREPARE-OP > . #<ASDF/SYSTEM:SYSTEM #2="quicklisp">) (#1# . #3=#<ASDF/LISP-ACTION:CL-SOURCE-FILE #2# "package">) (#4=#<ASDF/LISP-ACTION:COMPILE-OP > . #3#) (#5=#<ASDF/LISP-ACTION:LOAD-OP :VERBOSE NIL> . #3#) (#1# . #6=#<ASDF/LISP-ACTION:CL-SOURCE-FILE #2# "utils">) (#4# . #6#) (#5# . #6#) (#1# . #7=#<ASDF/LISP-ACTION:CL-SOURCE-FILE #2# "config">) (#4# . #7#) (#5# . #7#) (#1# . #8=#<ASDF/LISP-ACTION:CL-SOURCE-FILE #2# "impl">) (#4# . #8#) ...) :VERBOSE NIL) [fast-method] 29: ((:METHOD ASDF/PLAN:PERFORM-PLAN (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {100FBEEC13}> :VERBOSE NIL) [fast-method] 30: ((FLET CALL-NEXT-METHOD :IN "/home/hechee/work/src/asdf/build/asdf.lisp")) 31: ((LAMBDA NIL :IN ASDF/PLAN:PERFORM-PLAN)) 32: ((FLET SB-C::WITH-IT :IN SB-C::%WITH-COMPILATION-UNIT)) 33: ((:METHOD ASDF/PLAN:PERFORM-PLAN :AROUND (T)) #<ASDF/PLAN:SEQUENTIAL-PLAN {100FBEEC13}> :VERBOSE NIL) [fast-method] 34: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION ASDF/COMPONENT:COMPONENT)) #<ASDF/LISP-ACTION:LOAD-OP :VERBOSE NIL> #<ASDF/SYSTEM:SYSTEM "quicklisp"> :VERBOSE NIL) [fast-method] 35: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> #<ASDF/LISP-ACTION:LOAD-OP :VERBOSE NIL> #<ASDF/SYSTEM:SYSTEM "quicklisp"> :VERBOSE NIL) 36: ((FLET CALL-NEXT-METHOD :IN "/home/hechee/work/src/asdf/build/asdf.lisp")) 37: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 38: (ASDF/CACHE:CALL-WITH-ASDF-CACHE #<CLOSURE (LAMBDA NIL :IN ASDF/OPERATE:OPERATE) {100FBEDF0B}> :OVERRIDE NIL :KEY NIL) 39: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) #<ASDF/LISP-ACTION:LOAD-OP :VERBOSE NIL> #<ASDF/SYSTEM:SYSTEM "quicklisp"> :VERBOSE NIL) [fast-method] 40: ((:METHOD ASDF/OPERATE:OPERATE (SYMBOL T)) ASDF/LISP-ACTION:LOAD-OP "quicklisp" :VERBOSE NIL) [fast-method] 41: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> ASDF/LISP-ACTION:LOAD-OP "quicklisp" :VERBOSE NIL) 42: ((FLET CALL-NEXT-METHOD :IN "/home/hechee/work/src/asdf/build/asdf.lisp")) 43: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 44: (ASDF/CACHE:CALL-WITH-ASDF-CACHE #<CLOSURE (LAMBDA NIL :IN ASDF/OPERATE:OPERATE) {100F6DEDCB}> :OVERRIDE NIL :KEY NIL) 45: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/LISP-ACTION:LOAD-OP "quicklisp" :VERBOSE NIL) [fast-method] 46: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/LISP-ACTION:LOAD-OP "quicklisp" :VERBOSE NIL) [fast-method] 47: (ASDF/OPERATE:OOS ASDF/LISP-ACTION:LOAD-OP "quicklisp" :VERBOSE NIL) 48: ((LAMBDA NIL :IN "/home/hechee/lisp/quicklisp/setup.lisp")) 49: (SB-INT:SIMPLE-EVAL-IN-LEXENV (LET ((*COMPILE-PRINT* NIL) (*COMPILE-VERBOSE* NIL) (*LOAD-VERBOSE* NIL) (*LOAD-PRINT* NIL)) (ASDF/OPERATE:OOS (QUOTE ASDF/LISP-ACTION:LOAD-OP) "quicklisp" :VERBOSE NIL)) #<NULL-LEXENV>) 50: (SB-EXT:EVAL-TLF (LET ((*COMPILE-PRINT* NIL) (*COMPILE-VERBOSE* NIL) (*LOAD-VERBOSE* NIL) (*LOAD-PRINT* NIL)) (ASDF/OPERATE:OOS (QUOTE ASDF/LISP-ACTION:LOAD-OP) "quicklisp" :VERBOSE NIL)) 14 NIL) 51: ((LABELS SB-FASL::EVAL-FORM :IN SB-INT:LOAD-AS-SOURCE) (LET ((*COMPILE-PRINT* NIL) (*COMPILE-VERBOSE* NIL) (*LOAD-VERBOSE* NIL) (*LOAD-PRINT* NIL)) (ASDF/OPERATE:OOS (QUOTE ASDF/LISP-ACTION:LOAD-OP) "quicklisp" :VERBOSE NIL)) 14) 52: ((LAMBDA (SB-KERNEL:FORM &KEY :CURRENT-INDEX &ALLOW-OTHER-KEYS) :IN SB-INT:LOAD-AS-SOURCE) (LET ((*COMPILE-PRINT* NIL) (*COMPILE-VERBOSE* NIL) (*LOAD-VERBOSE* NIL) (*LOAD-PRINT* NIL)) (ASDF/OPERATE:OOS (QUOTE ASDF/LISP-ACTION:LOAD-OP) "quicklisp" :VERBOSE NIL)) :CURRENT-INDEX 14) 53: (SB-C::%DO-FORMS-FROM-INFO #<CLOSURE (LAMBDA (SB-KERNEL:FORM &KEY :CURRENT-INDEX &ALLOW-OTHER-KEYS) :IN SB-INT:LOAD-AS-SOURCE) {100CD5E1AB}> #<SB-C::SOURCE-INFO {100CD5E163}> SB-C::INPUT-ERROR-IN-LOAD) 54: (SB-INT:LOAD-AS-SOURCE #<SB-INT:FORM-TRACKING-STREAM for "file /home/hechee/lisp/quicklisp/setup.lisp" {100CD5B903}> :VERBOSE NIL :PRINT NIL :CONTEXT "loading") 55: ((FLET SB-FASL::LOAD-STREAM :IN LOAD) #<SB-INT:FORM-TRACKING-STREAM for "file /home/hechee/lisp/quicklisp/setup.lisp" {100CD5B903}> NIL) 56: (LOAD #P"/home/hechee/lisp/quicklisp/setup.lisp" :VERBOSE NIL :PRINT NIL :IF-DOES-NOT-EXIST NIL :EXTERNAL-FORMAT :DEFAULT) 57: (SB-INT:SIMPLE-EVAL-IN-LEXENV (LOAD (MERGE-PATHNAMES "lisp/quicklisp/setup.lisp" (USER-HOMEDIR-PATHNAME)) :IF-DOES-NOT-EXIST NIL) #<NULL-LEXENV>) 58: (SB-EXT:EVAL-TLF (LOAD (MERGE-PATHNAMES "lisp/quicklisp/setup.lisp" (USER-HOMEDIR-PATHNAME)) :IF-DOES-NOT-EXIST NIL) 8 NIL) 59: ((LABELS SB-FASL::EVAL-FORM :IN SB-INT:LOAD-AS-SOURCE) (LOAD (MERGE-PATHNAMES "lisp/quicklisp/setup.lisp" (USER-HOMEDIR-PATHNAME)) :IF-DOES-NOT-EXIST NIL) 8) 60: ((LAMBDA (SB-KERNEL:FORM &KEY :CURRENT-INDEX &ALLOW-OTHER-KEYS) :IN SB-INT:LOAD-AS-SOURCE) (LOAD (MERGE-PATHNAMES "lisp/quicklisp/setup.lisp" (USER-HOMEDIR-PATHNAME)) :IF-DOES-NOT-EXIST NIL) :CURRENT-INDEX 8) 61: (SB-C::%DO-FORMS-FROM-INFO #<CLOSURE (LAMBDA (SB-KERNEL:FORM &KEY :CURRENT-INDEX &ALLOW-OTHER-KEYS) :IN SB-INT:LOAD-AS-SOURCE) {1003E003AB}> #<SB-C::SOURCE-INFO {1003E00363}> SB-C::INPUT-ERROR-IN-LOAD) 62: (SB-INT:LOAD-AS-SOURCE #<SB-INT:FORM-TRACKING-STREAM for "file /home/hechee/.cl-init/asdf-init.lisp" {1003DFDBD3}> :VERBOSE NIL :PRINT NIL :CONTEXT "loading") 63: ((FLET SB-FASL::LOAD-STREAM :IN LOAD) #<SB-INT:FORM-TRACKING-STREAM for "file /home/hechee/.cl-init/asdf-init.lisp" {1003DFDBD3}> NIL) 64: (LOAD #P"/home/hechee/.cl-init/asdf-init.lisp" :VERBOSE NIL :PRINT NIL :IF-DOES-NOT-EXIST T :EXTERNAL-FORMAT :DEFAULT) 65: (SB-INT:SIMPLE-EVAL-IN-LEXENV (FLET ((HECHEE-USER::LOAD-INIT-FILE (HECHEE-USER::FILE) (LOAD (ETYPECASE HECHEE-USER::FILE # #) :PRINT NIL :VERBOSE NIL))) (LET ((HECHEE-USER::IMPL-SPECIFIC-INIT (MAKE-PATHNAME :NAME # :TYPE "lisp" :DEFAULTS HECHEE-USER::*RCDIR*))) (WHEN (PROBE-FILE HECHEE-USER::IMPL-SPECIFIC-INIT) (HECHEE-USER::LOAD-INIT-FILE HECHEE-USER::IMPL-SPECIFIC-INIT)) (HECHEE-USER::LOAD-INIT-FILE "asdf-init"))) #<NULL-LEXENV>) 66: (SB-EXT:EVAL-TLF (FLET ((HECHEE-USER::LOAD-INIT-FILE (HECHEE-USER::FILE) (LOAD (ETYPECASE HECHEE-USER::FILE # #) :PRINT NIL :VERBOSE NIL))) (LET ((HECHEE-USER::IMPL-SPECIFIC-INIT (MAKE-PATHNAME :NAME # :TYPE "lisp" :DEFAULTS HECHEE-USER::*RCDIR*))) (WHEN (PROBE-FILE HECHEE-USER::IMPL-SPECIFIC-INIT) (HECHEE-USER::LOAD-INIT-FILE HECHEE-USER::IMPL-SPECIFIC-INIT)) (HECHEE-USER::LOAD-INIT-FILE "asdf-init"))) 10 NIL) 67: ((LABELS SB-FASL::EVAL-FORM :IN SB-INT:LOAD-AS-SOURCE) (FLET ((HECHEE-USER::LOAD-INIT-FILE (HECHEE-USER::FILE) (LOAD (ETYPECASE HECHEE-USER::FILE # #) :PRINT NIL :VERBOSE NIL))) (LET ((HECHEE-USER::IMPL-SPECIFIC-INIT (MAKE-PATHNAME :NAME # :TYPE "lisp" :DEFAULTS HECHEE-USER::*RCDIR*))) (WHEN (PROBE-FILE HECHEE-USER::IMPL-SPECIFIC-INIT) (HECHEE-USER::LOAD-INIT-FILE HECHEE-USER::IMPL-SPECIFIC-INIT)) (HECHEE-USER::LOAD-INIT-FILE "asdf-init"))) 10) 68: ((LAMBDA (SB-KERNEL:FORM &KEY :CURRENT-INDEX &ALLOW-OTHER-KEYS) :IN SB-INT:LOAD-AS-SOURCE) (FLET ((HECHEE-USER::LOAD-INIT-FILE (HECHEE-USER::FILE) (LOAD (ETYPECASE HECHEE-USER::FILE # #) :PRINT NIL :VERBOSE NIL))) (LET ((HECHEE-USER::IMPL-SPECIFIC-INIT (MAKE-PATHNAME :NAME # :TYPE "lisp" :DEFAULTS HECHEE-USER::*RCDIR*))) (WHEN (PROBE-FILE HECHEE-USER::IMPL-SPECIFIC-INIT) (HECHEE-USER::LOAD-INIT-FILE HECHEE-USER::IMPL-SPECIFIC-INIT)) (HECHEE-USER::LOAD-INIT-FILE "asdf-init"))) :CURRENT-INDEX 10) 69: (SB-C::%DO-FORMS-FROM-INFO #<CLOSURE (LAMBDA (SB-KERNEL:FORM &KEY :CURRENT-INDEX &ALLOW-OTHER-KEYS) :IN SB-INT:LOAD-AS-SOURCE) {1003A0C23B}> #<SB-C::SOURCE-INFO {1003A0C1F3}> SB-C::INPUT-ERROR-IN-LOAD) 70: (SB-INT:LOAD-AS-SOURCE #<SB-SYS:FD-STREAM for "file /home/hechee/.cl-init/init.lisp" {1003A0A673}> :VERBOSE NIL :PRINT NIL :CONTEXT "userinit") 71: (SB-IMPL::PROCESS-INIT-FILE NIL :USER) 72: (SB-IMPL::TOPLEVEL-INIT) 73: ((FLET #:WITHOUT-INTERRUPTS-BODY-82 :IN SB-EXT:SAVE-LISP-AND-DIE)) 74: ((LABELS SB-IMPL::RESTART-LISP :IN SB-EXT:SAVE-LISP-AND-DIE)) -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.

2 1

package-inferred-system and :around-compile
by Eric Timmons 05 Dec '15

05 Dec '15

I'd really like to use :around-compile (for use with local-package-aliases), but I can't seem to combine it with package-inferred-system as the inferred systems don't inherit the around-compile slot from the top level system. I'd happily supply a patch to enable it. But I'm not sure if it would make the most sense to just inherit around-compile from the top level system or add an additional initarg for the package-inferred-system class that gets passed to the inferred systems. -Eric

2 3

Removing load-sysdef
by Stelian Ionescu 29 Nov '15

29 Nov '15

... broke SLIME's contrib/swank-asdf.lisp -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur.

2 1

[Q] figuring out a system / source file
by Didier Verna 24 Nov '15

24 Nov '15

Hello, starting from a file currently being processed (as per either *compile-file-truename* or *load-truename*), how can I retrieve the ASDF system currently being processed, and ultimately, the corresponding source file component (when *load-truename* returns a fasl) ? Thanks. -- My new Jazz CD entitled "Roots and Leaves" is out! Check it out: http://didierverna.com/records/roots-and-leaves.php Lisp, Jazz, Aïkido: http://www.didierverna.info

3 3

UIOP feature idea...
by Robert Goldman 24 Nov '15

24 Nov '15

What about adding a better FILE-LENGTH function to UIOP? I was looking at Peter Seibel's discussion of FILE-LENGTH in PCL. PiTA, and certainly unsuitable for use if one wants to write scripts in CL. What about making UIOP:FILE-LENGTH be generic and take either strings (filenames), pathnames, or streams as argument? cheers, r

3 2

Re: Suggestions for procedure going forward
by Jason Miller 20 Nov '15

20 Nov '15

> Date: Wed, 18 Nov 2015 23:55:29 -0600 > From: Robert Goldman <rpgoldman(a)sift.net> > To: Steven N??ez <steven.nunez(a)illation.com> > Cc: ASDF-devel <asdf-devel(a)common-lisp.net> > Subject: Re: Suggestions for procedure going forward > Message-ID: <564D6451.1080106(a)sift.net> > Content-Type: text/plain; charset=utf-8 On Wed, 18 Nov 2015 23:55:29 -0600 Robert Goldman said... > On 11/18/15 Nov 18 -11:33 PM, Steven N??ez wrote: > > With git you can, and usually do, have many branches, including personal ones. The pull request will be against a specific branch. I only read this message of the thread, so hope I'm answering the right question. Github has some good tutorials. > > Well the question isn't really about having many branches. The question > is what happens when you have stable and development branches, and you > want to "jump" the stable branch to mark retiring an old stable version > and starting a new one? Doesn't that involve a nasty merge or rebase? > > I can do some research, but I was hoping someone knew the answer.... I know the answer. As long as all merges go in the same direction there are little to no merge issues when you jump master to be develop. There are two major schools of thought on this. One is documented with "man 7 gitworkflows" and the other is discussed here: http://nvie.com/posts/a-successful-git-branching-model/ Since they use slightly different terminology, I'll use a theoretical repository with two branches named "stable" and "testing" in this repository a release happens when "testing" is merged back to "stable" and, aside from that, only bug fixes go into "stable"; I'll also use the terms "newer" and "older" to mean release order, so if you had a "previous-release" "current-release" "next-release" and "unstable" or some-such way of branching, that's the order from oldest to newest. They both share a single common feature: All new commits are based off of the oldest branch they might be merged into (so new features start off of the test branch, and bug fixes start off of the stable branch). If you change your mind (e.g. "this change is too risky for stable" or: "this new feature fixes a serious bug, it should go into stable too") then you rebase to the correct branch before doing a PR. The most important part is that these changes somehow get merged into the branche it was based off of and every single newer branch that might ever get merged back. With the "stable" and "testing" example this means all changes to stable must also be merged into testing. This way when it's time to merge your testing branch to your stable branch, testing is a superset of stable and a merge is guaranteed to succeed with no conflicts. -Jason

1 0

Re: Suggestions for procedure going forward
by Robert Goldman 19 Nov '15

19 Nov '15

On 11/18/15 Nov 18 -11:33 PM, Steven Núñez wrote: > With git you can, and usually do, have many branches, including personal ones. The pull request will be against a specific branch. I only read this message of the thread, so hope I'm answering the right question. Github has some good tutorials. Well the question isn't really about having many branches. The question is what happens when you have stable and development branches, and you want to "jump" the stable branch to mark retiring an old stable version and starting a new one? Doesn't that involve a nasty merge or rebase? I can do some research, but I was hoping someone knew the answer.... > > -----Original Message----- > From: asdf-devel [mailto:asdf-devel-bounces@common-lisp.net] On Behalf Of Robert Goldman > Sent: 18 November, 2015 21:17 > To: asdf-devel(a)common-lisp.net > Subject: Re: Suggestions for procedure going forward > > On 11/18/15 Nov 18 -8:35 PM, Faré wrote: >> Yeah, there's an awkward merge or rebase happening when "stable" jumps >> from 3.1 to 3.2, whereas no such jump happens if old branches have >> numbered names and are forked off a master that keeps going forward. >> > > Surely git must have a solution to this problem? There must be a ton of projects that need to have a "stable" and a "development" branch. So this must arise all over the place.... > > Anyone know? >

4 4

Suggestions for procedure going forward
by Robert Goldman 19 Nov '15

19 Nov '15

We have had a number of ASDF 3 releases that have mostly been aimed at bug-fixing (although some new features have crept in). I'd like to declare ASDF 3 feature complete and done, but I don't want to close the door to future bug fix releases as needed, nor do I want to shove incomplete new features out in order to get bug fixes out. So I'd like to split ASDF development into stable and testing or something like that. Does anyone have experience doing that? If so, please post suggestions for process to ASDF-devel. Thanks! r

4 9

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel