unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Andrew Tropin <andrew@trop.in>
To: phodina <phodina@protonmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: home-files-service-type file permissions
Date: Mon, 08 Nov 2021 11:42:22 +0300	[thread overview]
Message-ID: <87r1brghsh.fsf@trop.in> (raw)
In-Reply-To: <edkoLnq5-dfF1GUGdeLkYUceHmUpDwjGvunXKrzIuLg7xf91dafA8MECvCcb3P6XG__9IS_9n9x3D58dcTLQasnHUmdvjXcYo-wZeV0TQCI=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 2752 bytes --]

On 2021-11-08 06:44, phodina wrote:

> Hi Andrew,
>
> On Wednesday, November 3rd, 2021 at 8:24 AM, Andrew Tropin <andrew@trop.in> wrote:
>
>> On 2021-11-02 11:31, phodina@protonmail.com wrote:
>>
>> > Hi Andrew,
>> >
>> > Thanks for the development of Guix home. I've recently switch to it from my dotfiles.
>> >
>> > However, there is one thing that I do not know how to set.
>> >
>> > When using the service home-files-service-type I encountered a situation where I'm copying a script:
>> >
>> > (simple-service 'dotfiles
>> >
>> > home-files-service-type
>> >
>> > (list
>> >
>> > ...
>> >
>> > `("config/sway/wallpaper-change.sh" ,(local-file "config/sway/wallpaper-change.sh"))))
>> >
>> > However, after guix home reconfigure the file has only read flags set not execute. Even though the original file has execute flags.
>> >
>> > Is the home-files-service-type the correct service to use?
>> >
>> > Petr
>>
>> If there is no specific home service for your use case, which generates
>>
>> all necessary configs and executables for you the answer is probably
>>
>> yes, using home-files-service-type directly is a way to go.
>>
>> > Or do I have to patch it in order to keep the permissions?
>>
>> AFAIK, local-file, mixed-text-file create non-executable files in the
>>
>> store by design.
>
> Thanks, I've now looked more at the implementation and spend time understanding the differences between local-file, plain-file, computed-file, program-file.
>>
>> If you want to make an executable file you have at least a few options:
>>
>> 0. You can use recursive? flag to keep permissions.
>>
>> (local-file "blabla" #:recursive? #t)
>>
>
> Nice and simple solution.
>
>> The quote from documentation:
>>
>> > if file designates a flat file and recursive? is true, its contents
>> >
>> > are added, and its permission bits are kept.
>>
>> http://guix.gnu.org/en/manual/devel/en/guix.html#index-local_002dfile
>>
>> 1.  Use program-file
>>
>>     http://guix.gnu.org/en/manual/devel/en/guix.html#index-program_002dfile
>>
>>     For example I do it for generating screenshot scripts:
>>
>>     https://git.sr.ht/~abcdw/rde/tree/master/item/rde/features/wm.scm#L188
>
> Thanks for this example! This is what I've been looking for.
>
>> 2.  Use computed-file, which will call chmod with apropriate arguments
>>
>>     inside gexp. Take a look at "empty-tree" example in the manual, you can
>>
>>     create a file and set apropriate permissions in the same way.
>>
>>     --
>
> This is also super useful as it allows to do what's needed to the file.
>
>>
>>     Best regards,
>>
>>     Andrew Tropin

Sure, glad to help :)


-- 
Best regards,
Andrew Tropin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2021-11-08  8:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 11:31 home-files-service-type file permissions phodina via
2021-11-03  7:24 ` Andrew Tropin
2021-11-08  6:44   ` phodina
2021-11-08  8:42     ` Andrew Tropin [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=87r1brghsh.fsf@trop.in \
    --to=andrew@trop.in \
    --cc=help-guix@gnu.org \
    --cc=phodina@protonmail.com \
    /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).