reconnects not exported from deployment.lisp
Andreas Reuleaux
rx at a-rx.info
Fri Aug 5 22:04:49 BST 2022
Sean Whitton <spwhitton at spwhitton.name> writes:
> Sorry, you're right, you have to use DEFPROP if you are using
> get-connattr. But I don't think you need it. See "Properties" in the
> manual.
Well I need something here - and (get-connattr :remote-home) seems right
to me. If I don't use it all, then this link points in the wrong
direction:
(defproplist moc-config-symlinked :posix ()
(:desc #?"moc config symlinked")
(file:symlinked :from ".moc/config"
:to "cfg/moc/config"
)
)
...
rx at softland ~/.moc $ ls -lh config
lrwxrwxrwx 1 rx rx 14 Aug 5 21:56 config -> cfg/moc/config
rx at softland ~/.moc $
and config is even shown in red in my bash, as there is no
~/.moc/cfg/moc/config
it is ~/cfg/moc/config really - that's why I have this (get-connattr
:remote-home). This is correct (as shown earlier):
rx at softland ~/.moc $ ls -lh config
lrwxrwxrwx 1 rx rx 23 Aug 5 21:59 config -> /home/rx/cfg/moc/config
rx at softland ~/.moc $
>
>> ...So I stick with the defprop for now (as I want indeed the remote home in
>> my :to path: /home/rx/... - fine with (defprop moc-config-symlinked ...)
>>
>> (Is there a reason, why I cannot use (get-connattr :remote-home) in the
>> defproplist version ?)
>
> Yes, see the manual.
>
Yes, yes, yes - you pointed me there already - and I yet have to read it
more thoroughly.
>> If I don't use :sbcl, the error message was a little cryptic to me,
>> not really pointing me in the right direction
>>
>> (and maybe there is even some old cached stuff in there [?]: I have
>> commented all reconnects code)
>>
>>
>>
>>
>> (asdf:load-system "my.consfig") (in-package :my.consfig)
>> ;;; Computing Hangul syllable names
>> T
>> * #<PACKAGE "MY.CONSFIG">
>> (deploy-these ((:ssh :user "root")) softland (moc-combined))
>>
>> debugger invoked on a SB-INT:SIMPLE-PROGRAM-ERROR in thread
>> #<THREAD "main thread" RUNNING {1004E00073}>:
>> invalid keyword argument: :USER (valid keys are :TO).
>
> It's a bug, now fixed on master, thank you.
Thanks again.
-A
More information about the sgo-software-discuss
mailing list