From: Raghav Gururajan <rg@raghavgururajan.name>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: Help with copy-build-system
Date: Fri, 26 Mar 2021 05:55:49 -0400 [thread overview]
Message-ID: <13001cfd-29bd-2496-f7f7-b47c3cbaf360@raghavgururajan.name> (raw)
In-Reply-To: <87sg4imfuh.fsf@ambrevar.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 570 bytes --]
Hi Pierre!
> I haven't looked closely at your patch, but here is the rule for
> copy-build-system if I'm not mistaken: the files matching #:include
> preserve the path relative to the first argument.
>
> For instance with this rule
>
> ("/source/aaa/" "/target/bbb/" #:include ("foo"))
>
> the file
>
> /source/aaa/parent/foo
>
> is copied to
>
> /target/bbb/parent/foo
>
> (I haven't tested.)
>
> Does that help?
With the same example, I was looking for a way where foo gets copied to
as /target/bbb/foo.
Regards,
RG.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2021-03-26 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 11:23 Help with copy-build-system Raghav Gururajan
2021-03-26 9:20 ` Pierre Neidhardt
2021-03-26 9:55 ` Raghav Gururajan [this message]
2021-03-26 11:11 ` Pierre Neidhardt
2021-03-26 11:53 ` Raghav Gururajan
2021-03-26 12:12 ` Pierre Neidhardt
2021-03-26 12:28 ` Raghav Gururajan
-- strict thread matches above, loose matches on Subject: below --
2020-12-24 2:30 Cameron
2020-12-23 23:23 help " Cameron
2020-12-24 12:07 ` Julien Lepiller
2020-12-24 18:00 ` Cameron
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=13001cfd-29bd-2496-f7f7-b47c3cbaf360@raghavgururajan.name \
--to=rg@raghavgururajan.name \
--cc=help-guix@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.
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).