public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] vim-syntax USE flag
Date: Mon, 24 Jul 2017 13:42:16 -0400	[thread overview]
Message-ID: <CAJ0EP41XHFquQgRUyqg4v99N_Lp=cGgCCU9=NxwDV=pQ6JHuXw@mail.gmail.com> (raw)
In-Reply-To: <20170723164631.020dc120@snowblower>

On Sun, Jul 23, 2017 at 11:46 AM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Sat, 22 Jul 2017 16:27:39 -0400
> Mike Gilbert <floppym@gentoo.org> wrote:
>> Packages currently handle installation of vim syntax support files
>> inconsistently. Some builds install the files if the "vim-syntax" USE
>> flag is enabled, while others install them unconditionally.
>>
>> Do these files fall into the "small text files" category for
>> unconditional installation? If so, we should probably phase out the
>> vim-syntax USE flag.
>>
>> If we want to keep the USE flag, I would suggest documenting a global
>> policy regarding its use. Should that live in the devmanual? Or maybe
>> the Vim project page?
>
> One potential issue is help files: any Vim plugin that comes with
> documentation needs a little script (which requires Vim to be installed)
> to be run in pkg_postinst.

Thanks for pointing that out. Sounds like we need some documentation
on how to properly install vim-related files.


  reply	other threads:[~2017-07-24 17:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-22 20:27 [gentoo-dev] vim-syntax USE flag Mike Gilbert
2017-07-22 21:00 ` Sergei Trofimovich
2017-07-23 14:46   ` Andrew Savchenko
2017-07-23 15:27     ` Michał Górny
2017-07-23 21:20     ` Walter Dnes
2017-07-22 21:44 ` Daniel Campbell
2017-07-23 14:20 ` Patrice Clement
2017-07-23 15:40   ` Mike Gilbert
2017-07-23 15:46 ` Ciaran McCreesh
2017-07-24 17:42   ` Mike Gilbert [this message]
2017-07-24 10:10 ` Ulrich Mueller
2017-07-24 14:11   ` Mike Gilbert
2017-07-24 15:59     ` Ulrich Mueller
2017-07-25  6:13   ` Hans de Graaff

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='CAJ0EP41XHFquQgRUyqg4v99N_Lp=cGgCCU9=NxwDV=pQ6JHuXw@mail.gmail.com' \
    --to=floppym@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox