5 ms·

I just raided the project git repo and there is definitely no common lisp in there. Unfortunate name clash! https://asdf.common-lisp.dev/ https://asdf.common-l

• chobytes 5y ago
  My first thought as well! From the title I was intrigued to see how CL was being used for this.
• omaranto 5y ago
  Renaming because of this name clash has been suggested but the suggestion wasn't taken up: - https://github.com/asdf-vm/asdf/issues/383 https://github.com/asdf-vm/asdf/issues/383 - https://github.com/asdf-vm/asdf/issues/547 https://github.com/asdf-vm/asdf/issues/547 They did do something to ameliate this though: now they refer to the proect as asdf-vm as much as possible, to distinguish it from Common Lisp asdf.
  • d110af5ccf 5y ago
    I actively dislike this project even though I've never used it because Common Lisp asdf is a de facto standard that's been around since forever. There's no way you fail to notice the name clash with even a cursory search. They're both software projects and they're both build tools it's scummy behavior in my view to say the least.
• peterhil 5y ago
  My first reaction was to see if the project is made with Commnon Lisp's ASDF, and cool now it has plugins for different languages. Common Lisp ASDF is very well thought out, but not the easiest package management system.
  • ravi-delia 5y ago
    Yeah I was really wondering who found it easier to hack ASDF to work with other languages than just use a few separate package management solutions. It's an incredible library, but man I would not want to push its limits or it would go from odd to unusable pretty quick.