From: Alex Kost <alezost@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 30434@debbugs.gnu.org
Subject: bug#30434: magit won’t work over TRAMP
Date: Fri, 16 Feb 2018 19:56:36 +0300 [thread overview]
Message-ID: <874lmg6fgb.fsf@gmail.com> (raw)
In-Reply-To: <873721mhbh.fsf@netris.org> (Mark H. Weaver's message of "Fri, 16 Feb 2018 04:09:38 -0500")
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
Mark H Weaver (2018-02-16 04:09 -0500) wrote:
> Alex Kost <alezost@gmail.com> writes:
>
>> Mark H Weaver (2018-02-14 13:17 -0500) wrote:
>>
>>> Alex Kost <alezost@gmail.com> writes:
>>>
>>>> You didn't remove "git" from the inputs. I think it is not needed now.
>>>
>>> I removed it on my first attempt, but the build failed. See below.
>>
>> Oh, right, sorry. I use my own package for magit and it dosn't require
>> git input, so I thought that the original guix package also doesn't need
>> it. Sorry for the confusion :-)
>
> How does your own magit package avoid requiring git as an input? I'd be
> curious to see the diff between your package definition and ours.
My version of magit is attached. Actually this problem (requiring git
during compilation) was introduced occasionally in Magit 2.11.0 and was
fixed soon after that, so "git" input will not be needed in the next
release.
If you want more details, tarsius (the maintainer of Magit) added some
code to bring attention for his fundraising campaign:
https://github.com/magit/magit/commit/bf71241122e1a0bf707913c87493214ceb12f588
Then he made a release (2.11.0), but that commit introduced the
compilation fail if git wasn't available at compile-time. This was
fixed right after the release (at the same day):
https://github.com/magit/magit/commit/20ebb99a1dda085dfde99bf26d4d8a52fba51bcf
Finally the campaign code was removed 2 weeks later:
https://github.com/magit/magit/commit/4a9d9e59806735100b5d20a8be32defefb659a33
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: my-magit.scm --]
[-- Type: text/x-scheme, Size: 1703 bytes --]
(define-public my-emacs-magit
(package
(inherit magit)
(name "my-emacs-magit")
(arguments
(substitute-keyword-arguments (package-arguments magit)
((#:phases phases)
`(modify-phases ,phases
(replace 'patch-exec-paths
(lambda _
(with-directory-excursion "lisp"
;; "magit.el" calls 'magit-startup-asserts' and
;; 'magit-version' functions in the top level. I don't
;; need it at all.
(emacs-batch-edit-file "magit.el"
`(progn (goto-char (point-min))
(re-search-forward "(if after-init-time")
(up-list -1)
(kill-sexp)
(basic-save-buffer)))
(emacs-substitute-variables "magit-git.el"
("magit-git-executable" "git"))
;; XXX Campaign header was introduced in Magit 2.11.0
;; and will be removed in the next release:
;;
;; https://github.com/magit/magit/commit/bf71241122e1a0bf707913c87493214ceb12f588
;; https://github.com/magit/magit/commit/4a9d9e59806735100b5d20a8be32defefb659a33
;;
;; Change the value of 'magit-hide-campaign-header'
;; variable since it calls 'git' during initializing.
(emacs-substitute-variables "magit-status.el"
("magit-hide-campaign-header" 't))
#t)))))))
(inputs '())
(synopsis (string-append (package-synopsis magit)
" (without git dependency)"))))
next prev parent reply other threads:[~2018-02-16 16:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <365299e60040c03a84cbb7770adb3f94349dd2ed.camel@telenet.be>
2018-02-12 12:53 ` bug#30434: magit won’t work over TRAMP Ricardo Wurmus
2018-02-12 17:33 ` Alex Kost
2018-02-12 19:11 ` Ricardo Wurmus
2018-02-14 8:51 ` Mark H Weaver
2018-02-14 17:00 ` Alex Kost
2018-02-14 18:17 ` Mark H Weaver
2018-02-15 19:38 ` Alex Kost
2018-02-16 9:09 ` Mark H Weaver
2018-02-16 16:56 ` Alex Kost [this message]
2018-02-16 19:00 ` Mark H Weaver
2018-02-12 19:51 ` Mark H Weaver
[not found] ` <handler.x.B30434.165288084625349.unknown@debbugs.gnu.org>
[not found] ` <77826704875d168a2f7c608e146d9d5b09e7588c.camel@telenet.be>
2022-07-13 12:53 ` Maxim Cournoyer
2022-07-20 15:42 ` Maxime Devos
2022-07-21 4:04 ` Maxim Cournoyer
2023-09-21 7:34 ` Simon Tournier
2023-09-23 10:17 ` Maxime Devos
2023-09-23 10:19 ` Maxime Devos
2023-09-23 11:47 ` Simon Tournier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lmg6fgb.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=30434@debbugs.gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.