unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: 60029@debbugs.gnu.org
Cc: paren@disroot.org, me@jonscoresby.com,
	Efraim Flashner <efraim@flashner.co.il>,
	Efraim Flashner <efraim@flashner.co.il>,
	Guillaume Le Vaillant <glv@posteo.net>,
	Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
	Munyoki Kilyungi <me@bonfacemunyoki.com>,
	jgart <jgart@dismail.de>
Subject: [bug#60029] [PATCH v3 0/3] Add vim-build-system.
Date: Mon, 16 Oct 2023 12:15:10 +0300	[thread overview]
Message-ID: <cover.1697446927.git.efraim@flashner.co.il> (raw)
In-Reply-To: <cover.1670891520.git.me@jonscoresby.com>

I dropped the first commit, adding the option of other outputs to the
copy-build-system, in the interest of getting this merged sooner.

On the first patch I fix some typos and added to the comment at the top
of the file.

On the second patch I added the entries to Makefile.am and added the
missing documentation. I added the plugin-name field (I want to run
:packadd fugitive, not :packadd vim-fugitive-3.7), moved the neovim
output into the main output, added to the exclude-regexp, and some
general code cleanup.

On the third patch I adjusted the plugin paths of some more files in
packages which came with vim plugins. I reworked vim-vlime to have the
installed packpath resemble the upstream repository, which is supposed
to work as-is.

I noticed that I need to fix vim-asyncrun, it still has the install-plan
from before. I'm unsure about setting packages like vim-rainbow to use
'opt' for mode since that seems to be upstream's default, but would be
surprising. I tried my best to come up with expected plugin-names for
all the packages.

Jonathan Scoresby (3):
  gnu: vim: Add vim packages to 'package-path' instead of
    'runtime-path'.
  build-system: Add vim-build-system.
  gnu: Have vim packages use vim-build-system.

 Makefile.am                     |   4 +-
 doc/guix.texi                   |  33 ++++
 gnu/packages/aux-files/guix.vim |  11 +-
 gnu/packages/code.scm           |   5 +-
 gnu/packages/lisp.scm           |   5 +-
 gnu/packages/mail.scm           |   3 +-
 gnu/packages/rust-apps.scm      |   3 +-
 gnu/packages/vim.scm            | 306 ++++++++++++--------------------
 gnu/packages/wm.scm             |   3 +-
 guix/build-system/vim.scm       | 157 ++++++++++++++++
 guix/build/vim-build-system.scm | 117 ++++++++++++
 11 files changed, 437 insertions(+), 210 deletions(-)
 create mode 100644 guix/build-system/vim.scm
 create mode 100644 guix/build/vim-build-system.scm


base-commit: a0d2ecde943bd1854ddbb7c0cad35a1fc64dc5ab
-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted





  parent reply	other threads:[~2023-10-16  9:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13  0:38 [bug#60029] [PATCH core-updates 0/4] vim-build-system Jonathan Scoresby
2022-12-13  8:34 ` [bug#60029] [PATCH 1/4] guix: copy-build-system: allow install plan directives to specify output Jonathan Scoresby
2022-12-13 19:05   ` ( via Guix-patches via
2022-12-13  8:34 ` [bug#60029] [PATCH 2/4] gnu: vim: add relevant locations to 'package-path' instead of 'runtime-path' Jonathan Scoresby
2022-12-13 19:06   ` ( via Guix-patches via
2022-12-13 22:10     ` Jonathan Scoresby
2022-12-14  6:56       ` ( via Guix-patches via
2022-12-13  8:34 ` [bug#60029] [PATCH 3/4] guix: add vim-build-system Jonathan Scoresby
2022-12-13  8:34 ` [bug#60029] [PATCH 4/4] gnu: have vim packages use vim-build-system Jonathan Scoresby
2022-12-14 21:01 ` [bug#60029] [PATCH v2 1/4] guix: copy-build-system: allow install plan directives to specify output Jonathan Scoresby
2022-12-14 21:02   ` [bug#60029] [PATCH v2 2/4] gnu: vim: add relevant locations to 'package-path' instead of 'runtime-path' Jonathan Scoresby
2022-12-14 21:14     ` ( via Guix-patches via
2022-12-14 21:02   ` [bug#60029] [PATCH v2 3/4] guix: add vim-build-system Jonathan Scoresby
2022-12-14 21:02   ` [bug#60029] [PATCH v2 4/4] gnu: have vim packages use vim-build-system Jonathan Scoresby
2023-10-16  9:15 ` Efraim Flashner [this message]
2023-10-16  9:15   ` [bug#60029] [PATCH v3 1/3] gnu: vim: Add vim packages to 'package-path' instead of 'runtime-path' Efraim Flashner
2023-10-16  9:15   ` [bug#60029] [PATCH v3 2/3] build-system: Add vim-build-system Efraim Flashner
2023-10-16  9:15   ` [bug#60029] [PATCH v3 3/3] gnu: Have vim packages use vim-build-system Efraim Flashner
2023-11-08 10:16   ` bug#60029: [PATCH v3 0/3] Add vim-build-system Efraim Flashner

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=cover.1697446927.git.efraim@flashner.co.il \
    --to=efraim@flashner.co.il \
    --cc=60029@debbugs.gnu.org \
    --cc=cox.katherine.e+guix@gmail.com \
    --cc=glv@posteo.net \
    --cc=jgart@dismail.de \
    --cc=me@bonfacemunyoki.com \
    --cc=me@jonscoresby.com \
    --cc=paren@disroot.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 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).