all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Tissevert <tissevert+guix@marvid.fr>
Cc: 48126@debbugs.gnu.org
Subject: [bug#48126] [PATCH] Add package for vim-solarized
Date: Sat, 01 May 2021 01:20:30 +0200	[thread overview]
Message-ID: <87im43qs01.fsf@nckx> (raw)
In-Reply-To: <20210430194235.1461cada@pine.local>

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

Tissevert 写道:
> I here's my first attempt at packaging something, I noticed that 
> vim-solarized
> was missing so I tried to write a package for it.

Thank you!

>
> The only warning I got was from the guix lint which told me it 
> couldn't find
> upstream releases. I believe this is due to vim-solarized 
> particular structure:
> it's a light «clone» of the main repository
> https://github.com/altercation/solarized containing only the 
> vim-files.

Hmm.  Could we install from this authoritative(?) source instead, 
even if the download's bigger?

> (https://github.com/vim-scripts/Solarized) which has made a tag 
> (the same
> version name that I chose) so we could be using either the full 
> repository
> (more unneeded data retrieved during the build) or this second 
> copy (they do
> provide a tag but isn't it better to remain as close as possible 
> to the
> original source ?).

Oh, I think we agree.  :-)

/tmp λ git clone --depth=1 
https://github.com/vim-scripts/Solarized
Cloning into 'Solarized' [...]
/tmp λ git clone --depth=1 
https://github.com/altercation/solarized
Cloning into 'solarized' [...]
/tmp λ du -hs [Ss]olarized
196K	Solarized
30M	solarized

The relative difference is huge but I think 30M is worth it.

Could you make this change, test, and send a V2?  I'm no adherent 
of the Vim.

> I hope my patch is correct and thank you everyone for being such 
> a welcoming
> community and having made my experience with Guix so far 
> absolutely great !

Thank you!  We try to do our best...

Your patch is great.  I'd make the following tweaks before 
committing.  You can incorporate them into your V2 if you want.

The description should explain what the package is to someone 
who's never heard of it.  We actually recommend ~10 lines (more is 
fine), although many existing packages don't meet that bar.  The 
synopsis should do the same in one line.

Don't be afraid to temper fawning upstream marketing-speak and 
empty taglines like this one.  That doesn't mean it can't be 
positive (like mine -- I hate Solarized).

C-M-q reindented the source field according to the same rules as 
etc/indent-code.el.  Better to do so before committing it, so 
future committers can just run C-M-q on the entire expression 
without creating unrelated whitespace noise.

diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
index 477c15b9aa..ad95724c41 100644
--- a/gnu/packages/vim.scm
+++ b/gnu/packages/vim.scm
@@ -585,24 +585,33 @@ are detected, the user is notified.")
     (name "vim-solarized")
     (version "v1.0.0beta1")
     (source
-      (origin
-        (method git-fetch)
-        (uri (git-reference
-               (url 
                "https://github.com/altercation/vim-colors-solarized")
-               (commit 
                "528a59f26d12278698bb946f8fb82a63711eec21")))
-        (file-name (git-file-name name version))
-        (sha256
-         (base32
- 
           "05d3lmd1shyagvr3jygqghxd3k8a4vp32723fvxdm57fdrlyzcm1"))))
+     (origin
+       (method git-fetch)
+       (uri (git-reference
+             (url 
"https://github.com/altercation/vim-colors-solarized")
+             (commit 
"528a59f26d12278698bb946f8fb82a63711eec21")))
+       (file-name (git-file-name name version))
+       (sha256
+        (base32 
"05d3lmd1shyagvr3jygqghxd3k8a4vp32723fvxdm57fdrlyzcm1"))))
     (build-system copy-build-system)
     (arguments
      '(#:install-plan
        '(("colors" "share/vim/vimfiles/")
          ("doc" "share/vim/vimfiles/"))))
     (home-page 
     "https://github.com/altercation/vim-colors-solarized")
-    (synopsis "Solarized Colorscheme for Vim")
-    (description "Precision colors for machines and people")
-    (license license:bsd-3)))
+    (synopsis "Solarized color scheme for Vim")
+    (description
+     "Solarized is a sixteen-color palette of eight monotones and 
eight accent
+colors.  It was designed for use with both terminal and GUI 
applications.
+
+Black text on white from a computer display is akin to reading a 
book in direct
+sunlight and can tire the eye.  Solarized reduces brightness 
contrast but,
+unlike many low-contrast color schemes, retains contrasting hues 
based on
+color wheel relations for syntax highlighting readability.
+
+Solarized retains the same selective contrast relationships and 
overall feel
+when switching between the light and dark background modes.")
+    (license license:expat)))

Kind regards,

T G-R

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

  parent reply	other threads:[~2021-04-30 23:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 17:42 [bug#48126] [PATCH] Add package for vim-solarized Tissevert
2021-04-30 20:44 ` Tissevert
2021-04-30 22:06   ` Tobias Geerinckx-Rice via Guix-patches via
2021-04-30 23:20 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-04-30 23:27   ` Tobias Geerinckx-Rice via Guix-patches via
2021-05-04 20:56     ` Tissevert
2021-05-14 17:10       ` Tissevert
2021-05-14 18:25         ` Thiago Jung Bauermann via Guix-patches via
2021-05-14 20:33           ` Tissevert
2021-05-15 13:04 ` bug#48126: " Tobias Geerinckx-Rice via Guix-patches via

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=87im43qs01.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=48126@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=tissevert+guix@marvid.fr \
    /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.