From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>, "Ricardo Wurmus" <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: New build system: copy-build-system
Date: Tue, 28 Jan 2020 14:39:45 +0100 [thread overview]
Message-ID: <87v9ovbsym.fsf@ambrevar.xyz> (raw)
In-Reply-To: <874kwfj2hk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
Regarding the "install-plan", I suggest the following syntax:
(SOURCE TARGET [FILTERS])
In the above, FILTERS are optional.
- When SOURCE matches a file or directory without trailing slash, install it to
TARGET.
- If TARGET has a trailing slash, install SOURCE basename beneath TARGET.
- Otherwise install SOURCE as TARGET.
- When SOURCE is a directory with a trailing slash, or when FILTERS are used,
the trailing slash of TARGET is implied.
- Without FILTERS, install the full SOURCE _content_ to TARGET.
The paths relative to SOURCE are preserved within TARGET.
- With FILTERS among `#:include`, `#:include-regexp`, `#:exclude`,
`#:exclude-regexp`:
- With `#:include`, install only the exact subpaths in the list.
- With `#:include-regexp`, install subpaths matching the regexps in the list.
- The `#:exclude*` FILTERS work similarly. Without `#:include*` flags,
install every subpath but the files matching the `#:exlude*` filters.
If both `#:include*` and `#:exclude*` are specified, the exclusion is done
on the inclusion list.
Examples:
- `("foo/bar" "share/my-app/")`: Install bar to "share/my-app/bar".
- `("foo/bar" "share/my-app/baz")`: Install bar to "share/my-app/baz".
- `("foo/" "share/my-app")`: Install the content of foo inside "share/my-app",
e.g. install "foo/sub/file" to "share/my-app/sub/file".
- `("foo/" "share/my-app" #:include ("sub/file"))`: Install only "foo/sub/file" to "share/my-app/sub/file".
- `("foo/sub" "share/my-app" #:include ("file"))`: Install "foo/sub/file" to "share/my-app/file".
Maybe instead of having two #:include and #:include-regexp we could have just
one #:include in which the list elements have a "marker" that tells whether they
are regexps or not.
Clojure uses #"..." to mark regexps. Does Guile have something similar?
Any other suggestion?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-01-28 13:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 20:27 New build system: copy-build-system Pierre Neidhardt
2020-01-27 0:45 ` Jesse Gibbons
2020-01-27 4:14 ` Jack Hill
2020-01-27 14:27 ` zimoun
2020-01-27 14:44 ` Pierre Neidhardt
2020-01-27 15:03 ` zimoun
2020-01-27 15:18 ` Pierre Neidhardt
2020-01-27 15:36 ` zimoun
2020-01-27 15:51 ` Pierre Neidhardt
2020-01-27 16:17 ` zimoun
2020-01-27 18:18 ` Julien Lepiller
2020-01-27 16:45 ` How to deal with very large sources Ricardo Wurmus
2020-01-27 19:03 ` New build system: copy-build-system Ricardo Wurmus
2020-01-28 10:32 ` Ludovic Courtès
2020-01-28 13:39 ` Pierre Neidhardt [this message]
2020-01-28 23:04 ` Ludovic Courtès
2020-02-14 12:54 ` Pierre Neidhardt
2020-02-14 13:22 ` Julien Lepiller
2020-02-17 3:46 ` Jesse Gibbons
2020-02-17 7:56 ` Pierre Neidhardt
2020-02-17 16:52 ` Jesse Gibbons
2020-02-17 17:10 ` Pierre Neidhardt
2020-02-19 1:33 ` Alex Griffin
2020-02-19 14:01 ` 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=87v9ovbsym.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
/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).