Subject: bug#34865: closed (Re: [bug#34865] [PATCH] Add emacs-zones.)

From: [email-masked] (GNU bug Tracking System)
Date: Wed, 27 Mar 2019 19:28:02 +0000

Your bug report

#34865: [PATCH] Add emacs-zones.

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
34865: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34865
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: [bug#34865] [PATCH] Add emacs-zones.
From: Oleg Pykhalov <[email-masked]>
To: [email-masked]
Cc: Ricardo Wurmus <[email-masked]>, Brian Leung <[email-masked]>, Ludovic Courtès <[email-masked]>
Date: Wed, 27 Mar 2019 22:27:39 +0300
List-Id: <debbugs-submit.debbugs.gnu.org>

Hello,

Ludovic Courtès <[email-masked]> writes:

[…]

>>>>>> Could we use emacs-zones from Elpa? See
>>>>>> https://elpa.gnu.org/packages/zones.html . ‘guix import elpa
>>>>>> emacs-zones’ will produce a decent ‘origin’ record to pull a source.
>>>>>
>>>>> My understanding is that ELPA and MELPA tarballs are not necessarily
>>>>> persistent and immutable, and that we generally prefer referring
>>>>> directly to the upstream repo.
>>>>
>>>> Ouch, I thought ELPA is persistent.  That's a significant argument to
>>>> not use ELPA for our purposes :-( .
>>
>> I only know that MELPA isn’t immutable.  I assumed that ELPA is fine.
>
> [...]
>
>> git-fetch is the preferred way when there are no stable tarballs.
>
> So, Oleg, I think you can go either way, but fetching over Git is
> probably safer.
>
> Can you apply the patch?

OK, pushed as c881ed8698517a2c2007c2fdc3a7aeec52ff109c with a source
fetching over Git.

Thanks,
Oleg.

Subject: [PATCH] Add emacs-zones.
From: Brian Leung <[email-masked]>
To: [email-masked]
Date: Fri, 15 Mar 2019 01:24:08 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

See attached.
From 1d32be2a74fe747a6b52d6aae580e79969e960ff Mon Sep 17 00:00:00 2001
From: Brian Leung <[email-masked]>
Date: Fri, 15 Mar 2019 01:20:28 +0100
Subject: [PATCH] gnu: Add emacs-zones.

---
 gnu/packages/emacs-xyz.scm | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index 9fdb00efb9..51a647608f 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -5710,6 +5710,32 @@ interface and multiple, selectable \"styles\", whose use is fully
 customizable by the user.")
     (license license:gpl2+)))
 
+(define-public emacs-zones
+  (let ((commit "353fc38a6544eb59887bee045e373406f1d038a5")
+        (revision "1"))
+    (package
+      (name "emacs-zones")
+      (version (git-version "0" revision commit))
+      (source
+       (origin
+         (method git-fetch)
+         (uri (git-reference
+               (url "https://github.com/emacsmirror/zones.git")
+               (commit commit)))
+         (file-name (git-file-name name version))
+         (sha256
+          (base32
+           "0gwnw2giii2a14nlh62xp45f47cw6ikqphhzpmcw6c7mn9x5z2ar"))))
+      (build-system emacs-build-system)
+      (home-page "https://www.emacswiki.org/emacs/Zones")
+      (synopsis "Define and act on multiple zones of buffer text")
+      (description "Library @file{zones.el} lets you easily define and
+subsequently act on multiple zones of buffer text.  You can think of this as
+enlarging the notion of region.  In effect, it can remove the requirement of
+target text being a contiguous sequence of characters.  A set of buffer zones
+is, in effect, a (typically) noncontiguous set of text.")
+      (license license:gpl3+))))
+
 (define-public emacs-mu4e-alert
   (package
     (name "emacs-mu4e-alert")
-- 
2.21.0