From: Saku Laesvuori <saku@laesvuori.fi>
To: Nils Landt <nils@landt.email>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Store file names / how to intern files in subdirectory?
Date: Thu, 5 Oct 2023 12:08:02 +0300 [thread overview]
Message-ID: <g33f3wxjosslxyyf32k55jpk2nyowrgfkt6ibup4hrt3qm7fdv@mgdmy5bjspx2> (raw)
In-Reply-To: <1933252523.353103.1696488563874@office.mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
> [...]
> I understand it makes no sense to try to get
> /gnu/store/greenclip.service, but would it be possible to achieve
> /gnu/store/pznbc8xxhfkwxjbaff9h982cy4df1y1a-greenclip.service/some-directory/greenclip.service?
> Or are files always saved at the "top level" of the store?
It is possible with file-union. See the G-expressions section in the
manual.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-10-05 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 6:49 Store file names / how to intern files in subdirectory? Nils Landt
2023-10-05 9:08 ` Saku Laesvuori [this message]
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=g33f3wxjosslxyyf32k55jpk2nyowrgfkt6ibup4hrt3qm7fdv@mgdmy5bjspx2 \
--to=saku@laesvuori.fi \
--cc=help-guix@gnu.org \
--cc=nils@landt.email \
/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).