public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] vim-syntax USE flag
Date: Sun, 23 Jul 2017 17:27:09 +0200	[thread overview]
Message-ID: <1500823629.6674.0.camel@gentoo.org> (raw)
In-Reply-To: <20170723174604.24212d4ad379cf2ec5917fc0@gentoo.org>

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

On nie, 2017-07-23 at 17:46 +0300, Andrew Savchenko wrote:
> On Sat, 22 Jul 2017 22:00:16 +0100 Sergei Trofimovich 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.
> > 
> > I'd say use flag is not needed as long as it does not slow vim startup
> > down by much and does not change editor behaviour for every single
> > edited file type.
> 
> The problem here is more complicated. What about 100 plugins from
> different packages which of them is fast enough, but together they
> are slowing vim down to unacceptable level? Such case is
> especially sensitive on slow hardware.
> 
> That's why fine control over vim files is mandatory. Yes, it
> requires to rebuild packages, but with ccache/distcc available this
> is not a huge issue. And if someone really want to avoid such
> rebuilds, vim files can always be put to a separated package;
> though I see no real reason to do this.
> 
> Using INSTALL_MASK here is not an option, because toggling of
> individual vim files using it will be a nightmare.
> 

The tool you're looking for is called eselect.

-- 
Best regards,
Michał Górny

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 988 bytes --]

  reply	other threads:[~2017-07-23 15:27 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 [this message]
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
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=1500823629.6674.0.camel@gentoo.org \
    --to=mgorny@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