unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Maintaining GNU Jami package for Guix
Date: Sat, 2 Nov 2019 00:16:30 +0100	[thread overview]
Message-ID: <20191102001630.7bcfe9d9@interia.pl> (raw)
In-Reply-To: <87v9s3775l.fsf@ambrevar.xyz>

Dnia 2019-11-01, o godz. 20:01:26
Pierre Neidhardt <mail@ambrevar.xyz> napisał(a):

> Git preserves permissions, so if upstream made it read-only (probably
> a mistake), then it will be read-only in the checkout.  No problem,
> you can make it writable with
> `make-file-writable'.
> 

Don't know why, but it doesn't work...
It still tells me files are read-only.
I do something like this:

(modify-phases %standard-phases
	 (add-after 'unpack 'make-git-checkout-writable
	   (lambda _
             (for-each make-file-writable (find-files "."))
             #t))
         (add-after 'unpack 'apply-patches
           (lambda* (#:key inputs #:allow-other-keys)
             (let ((savoir-faire-linux-patches-directory "Savoir-faire
Linux patches") ;; Comes from
                   ;;
"ring-project/daemon/contrib/src/pjproject/rules.mak". ;; WARNING:
These amount for huge changes in pjproject. ;; Particularly, they add
support for GnuTLS. (savoir-faire-linux-patches
                    '("add_dtls_transport"
		      "android"
		      "disable_local_resolution"
....................


Jan Wielkiewicz

  reply	other threads:[~2019-11-02 20:48 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 18:56 Maintaining GNU Jami package for Guix Jan
2019-10-18 19:28 ` Marius Bakke
2019-10-19  9:02   ` Pierre Neidhardt
2019-10-19 20:38     ` Jan Wielkiewicz
2019-10-19 20:52       ` Ricardo Wurmus
2019-10-19 22:37         ` Jan
2019-10-20 11:14           ` Ricardo Wurmus
2019-10-20 11:51           ` Pierre Neidhardt
2019-10-20 11:48       ` Pierre Neidhardt
2019-10-25 15:03         ` Pierre Neidhardt
2019-10-25 19:44           ` Jan Wielkiewicz
2019-10-26 10:12             ` Pierre Neidhardt
2019-10-26 23:24               ` Jan Wielkiewicz
2019-10-28  7:53                 ` Pierre Neidhardt
2019-10-27 18:13 ` Jan Wielkiewicz
2019-10-27 18:18   ` Pierre Neidhardt
2019-10-27 19:23     ` Jan Wielkiewicz
2019-10-27 21:52 ` Jan Wielkiewicz
2019-10-31 20:19 ` Jan Wielkiewicz
2019-10-31 21:37   ` Pierre Neidhardt
2019-10-31 22:26   ` Marius Bakke
2019-11-01 12:01     ` Jan Wielkiewicz
2019-11-01 19:02       ` Pierre Neidhardt
2019-11-01 20:42         ` Jan Wielkiewicz
2019-11-02  9:38           ` Pierre Neidhardt
2019-11-03 16:37       ` Marius Bakke
2019-11-03 17:43         ` Jan
2019-11-03 18:06           ` Marius Bakke
2019-11-01 12:29 ` Jan Wielkiewicz
2019-11-01 19:01   ` Pierre Neidhardt
2019-11-01 23:16     ` Jan Wielkiewicz [this message]
2019-11-03 10:15       ` Pierre Neidhardt
2019-11-03 10:54         ` Jan Wielkiewicz
2019-11-04 10:02           ` Gábor Boskovits
2019-11-03 10:59         ` Jan Wielkiewicz
2019-11-03 17:07   ` Marius Bakke
2019-11-03 17:47     ` Jan
2019-11-03 18:12   ` Marius Bakke
2019-11-03 18:27     ` Jan
2019-11-03 18:52       ` Marius Bakke

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=20191102001630.7bcfe9d9@interia.pl \
    --to=tona_kosmicznego_smiecia@interia.pl \
    --cc=guix-devel@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.
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).