François-René ÐVB Rideau écrivait:
> What are the methods defined by asdf-flv?
In order to support file local variables, ASDF-FLV does this:
(defmethod asdf:perform :around
((operation asdf:load-op) (file asdf:cl-source-file))
"Establish new dynamic bindings for file-local variables."
François-René ÐVB Rideau écrivait:
> What are the methods defined by asdf-flv?
In order to support file local variables, ASDF-FLV does this:
(defmethod asdf:perform :around
((operation asdf:load-op) (file asdf:cl-source-file))
"Establish new dynamic bindings for file-local variables."
Wilfredo Velazquez wrote:
> Sorry in advance for not exactly answering your question, but out of
> curiosity, what would 'conditionally included' entail exactly?
Conditional in the ASDF sense, that is...
> BTW See ASDF's `:if-feature` option.
... exactly that, or :feature, etc.
--
Resist
Hi there,
until now, I had a tendency to split a library into several systems
(more or less without thinking much) as soon as such or such feature was
conditional (e.g. depending on CFFI availability, thread support, etc.).
Now I realize that in many cases, a conditionally included module or
Eric Timmons wrote:
> So to prevent misinterpretation of 3.4.0-1, ASDF could either promise
> to always use something like alpha/beta/etc,
Then I suggest to also allow a, b, rc, and maybe p (for pre;
equivalent of release candidate). That should cover a lot of ground.
--
Resistance is futi
Stelian Ionescu wrote:
>> Mostly sounds good to me. Assuming you're still interested in more
>> expressive version numbers and constraints for 3.4, I'll work on moving
>> that off the back burner.
>
> Adding fine-grained version constraints would be a big mistake.
I do not have the time to ch
François-René ÐVB Rideau écrivait:
> Your manual (asdf:load-system ...) from the .asd file is equivalent to
> a :defsystem-depends-on dependency. It creates a dependency at
> system-definition-time, but not at runtime. Not at runtime, ergo, not
> to be included in the executable.
No, this is wr
Daniel Kochmański wrote:
> If the setup is indirect dependency of a dumped system, then it is
> most likely asdf bug
Yes, it's an indirect dependency via a chain of :depends-on:
:simple
-> :net.didierverna.clon
-> :net.didierverna.clon.core
-> :net.didierverna.clon.setup
--
¡En Seguida! --
Hello,
I'm cross-posting because I don't know if the issue is related to ASDF
or ECL. I'm using the most recent repos of both.
When dumping a very simple system defined like this:
(asdf:defsystem :simple
:depends-on (:net.didierverna.clon)
:components ((:file "simple"))
:entry-point "s
Hi,
sorry for asking, I can't test it locally (I only have the personal
edition here).
--
¡En Seguida! -- New album: https://www.didierverna.com/records/en-seguida.php
Available on all digital platforms now!
Lisp, Jazz, Aïkido: http://www.didierverna.info
"Robert Goldman" écrivait:
> Didier, would you mind posting a GitLab issue for this? It's feasible,
> but I'm so overloaded right now that there's no chance I will get to
> it before I forget.
Sure!
--
¡En Seguida! -- New album: https://www.didierverna.com/records/en-seguida.php
Available on
François-René ÐVB Rideau écrivait:
> Before it can be ignored, it must be defined. And so as to define it,
> its class must be defined. I suppose we could have some error class
> that it used when the class it not defined, that would only trigger an
> error at runtime if the feature is true. I'm s
François-René ÐVB Rideau écrivait:
> Using git log test/test-defsystem-depends-on.script it looks like this
> is https://bugs.launchpad.net/asdf/+bug/1445638 Looking for that bug
> in git log, it was fixed in 3.1.4.5 on 2015-04-23.
I'm proceeding with the second issue in my system, and it seems
"Robert Goldman" wrote:
> This one seems complex enough -- and so much trouble to make a MWE --
> that maybe you want to just change it and see if it breaks.
Yup, that's what I did locally, with recent versions of all compilers
I have. Those shipping with ASDF seem to all have 3.2.0 at least
François-René ÐVB Rideau écrivait:
> What more, even Xach seems to have miraculously seen the light: one
> months and one week ago, he updated the fallback ASDF in Quicklisp
> from 2.26 to 3.2.1!
That's also what made me think I could perhaps do some clean up!
> That was the first update of A
Hi,
I would like to remove some old workaround code from a couple of
systems, wrt to ASDF 3.1.4 bugs (see below). Is it safe to do so now, or
are these "bugs" still lurking around?
The relevant parts are as follows:
:defsystem-depends-on
(:net.didierverna.clon.setup/termio
#+sbcl ;; B
Eric Timmons wrote:
> This should give you what you want:
>
> (asdf:output-files 'asdf:program-op "my-system")
Cool! Thank you (both)!
--
¡En Seguida! -- New album: https://www.didierverna.com/records/en-seguida.php
Available on all digital platforms now!
Lisp, Jazz, Aïkido: http://www.didi
Hi,
what's the proper way to find out where a dumped executable (resulting
from a program-op) has landed? I would like to it to literally
:move-here #p"./", to speak in MAKE-BUILD terms... Note that *I* know
where it is in the cache; what I want is programmatic access to its
location.
Thanks!
"Robert Goldman" wrote:
> On 15 Aug 2018, at 8:59, Hugo Ishimaru wrote:
>
> Hi all,
>
> I have extracted a UIOP's manual from docstrings:
> https://privet-kitty.github.io/etc/uiop.html It's not perfect in any
> means as docstring isn't written in a markup langugage, but will be
> at least a
Eitaro Fukamachi écrivait:
> To be honest, I'm not a big fan of it anymore and I don't follow it in
> my recent products. I'm willing to delete the code from CL-Project,
> though I have nothing I can do for existing projects.
Not a big fan either. What I usually do is use the description slot
"Robert Goldman" écrivait:
> This is yet another problem that comes from the fact that the build
> plans are linear, instead of hierarchical -- for example there's no
> subsequence that is identifiable as being the set of operations for a
> particular module.
>
> Logically speaking, there's a tre
"Robert Goldman" écrivait:
> Depending on the host lisp you are using, couldn't you wrap the calls
> to COMPILE-FILE and LOAD in code that times those operation?
I could, but since I want per-library numbers, I would need to
reconstruct that information afterwards...
--
Resistance is futil
François-René ÐVB Rideau écrivait:
> Simplest method:
> 1- load the dependencies, possibly using (asdf:operate :prepare-op s)
> 2- (time (asdf:make s))
Nice, thank you. If I want to time separately the compilation and
loading phases of several libraries (which may depend on each other)
how
Hello,
I would like to collect information about the time it takes to compile
an ASDF system (possibly also load it), dependencies excluded. I'm
thinking there's probably a way to do this by :around'ing compile-op, or
something like that, but if someone already has a clear view on how to
make
I wrote:
> I would like to find the source directory of an installed ASDF system
> even if it's not loaded and even if some of its dependencies are not
> installed (so it couldn't be loaded anyway). It seems that I can't use
> SYSTEM-SOURCE-DIRECTORY in such a case. What should I do?
Replying t
Hello,
I would like to find the source directory of an installed ASDF system
even if it's not loaded and even if some of its dependencies are not
installed (so it couldn't be loaded anyway). It seems that I can't use
SYSTEM-SOURCE-DIRECTORY in such a case. What should I do?
Thanks!
--
Resis
Robert Goldman wrote:
> I just looked over that README, and realized that it was not
> maintained. I quickly concluded that I do not have the resources to
> maintain both this file and the HTML file at
> https://common-lisp.net/project/asdf/, and the latter is what I have
> been updating with ne
François-René ÐVB Rideau wrote:
> The traditional solution is to load a file that fails. i.e. create a
> file unsupported-implementation.lisp that has an (error ...) form and
> in your asd file, use a component (:file "unsupported-implementation"
> :if-feature (:not :sbcl))
Hmmm, ok but then,
Stelian Ionescu wrote:
> #-feature
> (error "FEATURE missing")
>
> at toplevel, so you get an error on reading the .asd file.
Of course. I said a "declarative way" within the system itself tho ;-)
--
Resistance is futile. You will be jazzimilated.
Lisp, Jazz, Aïkido: http://www.didierverna.i
Robert Goldman écrivait:
> I stubbed my toe on this absent-mindedly compiling Didier's decLt
> system on Allegro Common Lisp. That system doesn't, and cannot,
> function on ACL, but ASDF tells us it has compiled successfully.
Following up to our private conversation on this...
I think there'
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 Ja
François-René ÐVB Rideau écrivait:
> I was considering just a string for now
FWIW, I'm also in favor of strings. Using symbols is risky for
case-sensitiveness.
--
My new Jazz CD entitled "Roots and Leaves" is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php
Lisp, Jazz
J'écrivais:
> Good idea, although it seems to be missing the GNU All Permissive
> license (the submission process looks quite cumbersome).
Ended up doing it anyway.
--
My new Jazz CD entitled "Roots and Leaves" is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php
Lis
François-René ÐVB Rideau écrivait:
> I propose we document that the license field should if possible
> contain an identifier from
> http://spdx.org/licenses/
> http://esr.ibiblio.org/?p=6867
Good idea, although it seems to be missing the GNU All Permissive
license (the submission process
Robert Goldman wrote:
> According to the manual REQUIRE-SYSTEM is "... a version of
> @code{load-system} that skips trying to update systems that are
> already loaded."
>
> There is no REQUIRE-OP.
>
> There is a REQUIRE-SYSTEM which is a system whose loading is handled
> by REQUIRE instead of nat
Hello,
can somebody explain to me what is the :require dependency specification,
and how it compares to just a simple-component-name ?
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://w
Robert Goldman wrote:
> Why would that be a win over just calling FORMATTED-VERSION on demand?
>
> I.e., we could just provide something like
>
> (defgeneric FORMATTED-VERSION (C &optional version)
> (:method ((COMPONENT C) &optional version)
> (or version (component-version c)))
>
> and t
Robert Goldman wrote:
> Just to clarify: I am NOT saying Pascal is wrong to want these things
> or to do them himself. And I AM saying that ASDF should make it
> possible for him to do so.
ASDF could call FORMATTED-VERSION itself to initialize the
corresponding slot (if any), and refrain fr
Robert Goldman wrote:
> So what happens when the programmer updates the human readable version
> and not the canonical version, or vice versa? Wouldn't it be better
> to functionally derive one of these two forms from the other? E.g.,
> (defgeneric formatted-version (component version-spec))
Robert Goldman wrote:
> Now: a request for management purposes: Didier, would you be so kind
> as to describe the proposal (I think cut and paste out of your earlier
> emails would do admirably) in a ticket on launchpad.net?
OK. I will also add Pascal's suggestion to have both a canonical and
Faré wrote:
> I kind of like the general idea of Pascal's proposal: separate a
> human-readable-version-string from an asdf-comparable-version-string.
> The exact names are to be determined. Maybe, by analogy with name and
> long-name, description and long-description, we could make that
> versio
"Pascal J. Bourguignon" wrote:
> Alternatively, we could have:
>
> (defsystem :foo
>:version-major 1
>:version-minor 0
>:version-release 42
>:human-readable-version-string "1.0.gamma.XLII/pescadero:whasa")
>
> or:
>
> (defsystem :foo
>:version (1 0 42)
>:human-readable
Drake Wilson wrote:
> Curiosity: what _are_ your version numbers like, and how do you
> compare them? It was a little too hard to find this readily from your
> website. Maybe seeing a good example would help.
A version specifier has a major and a minor number, a status (alpha,
beta, release
I wrote:
> Thoughts ? Will this be enough to satisfy ASDF ?
Not quite. I missed NORMALIZE-VERSION (ASDF attempting to be clever
and doing all sorts of nasty DWIM stuff on version numbers).
Attached patch would solve the problem, it seems. But then again, I
don't really know what I'm doin
Hi,
in general, I don't like the way ASDF tries to force you to comply with
its own design choices and policy. This is especially true for component
versioning. ASDF complains that it doesn't like my version numbers
(which, in fact, are not only numbers ;-), but I'm not ready to give up
on them
Pascal Costanza wrote:
> Just to chime in in the middle: There is no known solution to the
> so-called "DLL hell" problem.
You're right of course, but in practice, I think we have a lot to learn
from guix/nixos. Ultimately, I would like to see quicklisp and asdf melt
into a beast like that...
-
Robert Goldman wrote:
> The advantage of having the pair, of course, is that a simple URL does
> not necessarily identify the form of VCS.
But what would be the use for this information? I mean, having this
information as part of the system desciption.
--
Resistance is futile. You will be
Faré wrote:
> Although, it isn't clear yet how source-control may or may not specify
> the VCS used: should we prefix the URL with a git: or svn: or darcs:
> or some such? ASDF uses: :source-control (:git
> "git://common-lisp.net/projects/asdf/asdf.git")
Personally, I would not complicate this
Hello,
what's the purpose of the LONG-NAME slot in ASDF 3's system class?
Also, can I assume that HOMEPAGE, SOURCE-CONTROL and BUG-TRACKER are
meant to be URL strings ?
Thanks.
--
Resistance is futile. You will be jazzimilated.
Lisp, Jazz, Aïkido: http://www.didierverna.info
Faré wrote:
> since you provide no justification for what you are trying to do,
> anything can be "reasonable" or not.
I'm not sure what I need to justify, since my original question was
actually quite precise.
> My bet is that this isn't what you really want in the end,
> Usually, one w
I wrote:
> All of this is way beyond me.
But by looking at the code, it seems that the dependency names I'm
looking for are in the SIDEWAY-DEPENDENCIES slot of the
components. From there, it seems that I can use
RESOLVE-DEPENDENCY-NAME to finally get a component object.
Does this sound
Faré wrote:
> what are you *really* trying to do?
Really, trying to get the same thing that component-load-dependencies
gives me, but as component objects instead of names.
> Usually, one wants to get a list of components within a system.
> Then, one typically uses required-components, e.g
Hello,
currently Declt advertises component dependencies by using
COMPONENT-LOAD-DEPENDENCIES. This function however only returns a list
of symbols naming the components.
What would be the best way to retrieve a list of component objects
instead ?
Thanks!
--
Resistance is futile. You will b
Yothere,
I upgraded ECL this morning to the latest repo version and I cannot use
it anymore with my usual setup (-norc works). My local versions of
Quicklisp and ASDF are also the lastest. I have this in my init file:
;; Do ASDF first (when a compiler provides it directly, I think it is bette
Robert Goldman wrote:
> Thanks. If I get some downtime, I'll try to either split these
> subsections into nodes (if anyone has an emacs command that will do
> that automagically, please LMK), or add anchors.
You may want to start with C-x h C-u M-x texinfo-insert-node-lines.
This will create
Robert Goldman wrote:
> It would be nice if texinfo offered links to more specific locations
> than nodes, but it sounds like that's not available.
It is. You can do that manually with anchors. Cf. @anchor{} and
@ref{} (@xref, @pxref etc.)..
--
Resistance is futile. You will be jazzimilate
rpgold...@sift.info wrote:
> As far as I can tell, this is a misfeature of texinfo. The links only
> work to the node level (at least in the info browser). So we would
> need to reactor the document into smaller nodes to fix that.
That's not really a misfeature. That fact is that Texinfo uses n
Faré wrote:
> I had no idea that anyone was still using Corman Lisp. With the author
> not replying to any of my emails for years, and the most active users
> long gone, I have classified the platform as "dead until further
> notice". I understand you too are trying to port your software to it,
>
Hello,
I'm trying to use ASDF (git repo) with Corman Lisp 3.0 natively on
Windows. I managed to have Corman Lisp load ASDF, but now I have a
configuration problem.
I have a file C:\Users\Didier\.config\common-lisp\source-registry.conf
which contains this:
(:source-registry
(:tree "C:\Progra
Faré wrote:
> Speaking of which, some time ago, I started to collect asdf
> extensions, and I just added a listing of them on the asdf webpage.
> Please suggest more extensions that I may list on the page.
ASDF-FLV, related to CDR #9.
--
Resistance is futile. You will be jazzimilated.
Scie
Hello,
what is the current status of :feature in a list of dependencies? I
mean, is it safe to replace #+ reader conditionals in the asd file with
it?
Thanks.
--
Resistance is futile. You will be jazzimilated.
Scientific site: http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www
Faré wrote:
> That said, whatever you're doing that is hitting that bug is probably
> itself a mistake. There is no reason for you to ever use
> (component-pathname (find-system ...)) Instead, you should be using
> (system-relative-pathname ...) or some such thing.
Yup. In fact, I never used "
Faré wrote:
>> 5/ Finally, I would like confirmation that ASDF now handles outdated
>> fasl's correctly, and we don't need to do the black magick
>> ourselves.
>>
> I'm not sure what you mean, so I'd say probably not. If you have
> "black magick" that you think should be part of ASDF, please su
[ Please, Cc: me as I'm not on the mailing list ]
Hi,
I'm trying to upgrade my CL configuration to ASDF 2, and I have several
questions:
1/ why isn't "source-registry.conf" named "asdf-source-registry.conf" ?
2/ Should we understand that the convention of having a "systems"
directory w
I wrote:
> [ Please, Cc: me as I'm not on the mailing list ]
here's another one:
In ASDF 1, (component-pathname (find-system ...)) returned the system's
*directory*, which was coherent because the system is a module, so its
pathname is a directory just like for any other sub-module.
In ASDF 2,
65 matches
Mail list logo
