From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: ASDF Builder (Common Lisp) & "package-inferred-system" Packages
Date: Fri, 11 Jan 2019 09:34:44 -0600 [thread overview]
Message-ID: <87wonb6wdn.fsf@gmail.com> (raw)
In-Reply-To: <87fttzd0uo.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Fri, 11 Jan 2019 10:01:35 +0100")
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> I've packaged a lot of Lisp packages, none of which seem to suffer
> from a naming issue.
This is a newer style of ASDF system. I don't think any of the things we
have packaged use this style (yet).
> Do you have an example in mind?
I have 41 packages almost ready to go, but the only one I'm currently
packaging that uses the "package-inferred-system" style is Ningle[1].
> Which string replacement are you referring to? NORMALIZE-STRING?
Yes. I'm wondering why we even need to call `normalize-string' here
since this is generating the string ASDF will use to search for a
package, and ASDF is capable of handling `/` characters in its package
names. I think we may be conflating the need for the store to remove `/`
characters with ASDF's needs, but I'm not completely sure.
> I'm not completely sure, but I think that in practice packages can
> always specify the right ASD-FILE or SYSTEM. There could be something
> missing though.
This is not about specifying the ASD file; it is regarding how a system
is defined within an ASD file. Please read this[2] link for more
information. A single ASD file will define a package (note, not system)
per file. The packages will all have the `/` character embedded in the
name since it is correlating files in the system's path with packages.
I cannot find a way to tell the runtime that the renamed package (in
this case "ningle-main") is an alias for the real package
("ningle/main"), but it is very possible I'm missing something obvious.
[1] - https://github.com/fukamachi/ningle/blob/master/ningle.asd
[2] - https://www.common-lisp.net/project/asdf/asdf.html#index-Package-inferred-systems
--
Katherine
next prev parent reply other threads:[~2019-01-11 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 0:25 ASDF Builder (Common Lisp) & "package-inferred-system" Packages Katherine Cox-Buday
2019-01-11 9:01 ` Pierre Neidhardt
2019-01-11 15:34 ` Katherine Cox-Buday [this message]
2019-01-12 20:24 ` Katherine Cox-Buday
2019-01-13 19:14 ` Andy Patterson
2019-01-14 0:20 ` Katherine Cox-Buday
2019-08-02 16:28 ` Pierre Neidhardt
2019-08-02 16:43 ` Pierre Neidhardt
2019-08-02 17:37 ` Pierre Neidhardt
2019-08-02 20:27 ` Katherine Cox-Buday
2019-08-03 8:04 ` Pierre Neidhardt
2019-08-03 8:44 ` Pierre Neidhardt
2019-08-03 14:14 ` Katherine Cox-Buday
2019-08-06 10:41 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wonb6wdn.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).