From: "Tomás Ortín Fernández" <tomasortin@mailbox.org>
To: help-guix@gnu.org
Subject: Making file writable
Date: Fri, 27 Nov 2020 19:53:31 +0100 [thread overview]
Message-ID: <0dc1dbd8-91c6-6f95-7e60-e1ed4514f255@mailbox.org> (raw)
I'm trying to pack the updated version of rubocop (1.4.2). The problem is that a patch must be applied, and it affects two files that aren't writable, .rubocop.yml and .rubocop_todo.yml. I've tried making it writable after unpacking:
(arguments ...
...
(add-after 'unpack 'make-yml-files-writable
(lambda _
(let ((yml-files (find-files "\\.yml$")))
(for-each make-file-writable yml-files))
#t))
...)
I've tried as well doing it with a snippet:
(source ...
...
(modules '((guix build utils)))
(snippet
'(begin
(for-each (make-file-writable (find-files "\\.yml$")))
#t))
...)
However, I haven't been successful and the files remain non-writable when the patch is applied. What am I doing wrong?
Tomás
next reply other threads:[~2020-11-27 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 18:53 Tomás Ortín Fernández [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-27 20:19 Making file writable John Soo
2020-11-27 21:12 ` Tomás Ortín Fernández
2020-11-27 23:22 ` John Soo
2020-11-27 18:18 Tomás Ortín Fernández
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=0dc1dbd8-91c6-6f95-7e60-e1ed4514f255@mailbox.org \
--to=tomasortin@mailbox.org \
--cc=help-guix@gnu.org \
/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).