From: Ewan Mac Mahon <ecm103@york.ac.uk>
To: Gentoo-User <gentoo-user@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-user] splitted ebuilds for vim and gvim
Date: Sat, 14 Sep 2002 15:10:22 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0209141505570.24517-100000@kitt.york.ac.uk> (raw)
In-Reply-To: <20020913091917.GA7958@mehnert.org>
On Fri, 13 Sep 2002, Hannes Mehnert wrote:
> Hi everyone,
>
> I just commited seperate ebuilds for gvim and vim.
>
I seem to be a lone dissenting voice here, so I'm proably missing
something, but is this really a good idea? I've always regarded the
split packaging of vim in other distros as an unfortunate consequence of
their not being able to handle compile time options. Since one of gentoos
strengths is that it can this seems an odd decision - what's the advantage
over using the X and gtk USE settings like before?
Ewan
next prev parent reply other threads:[~2002-09-14 14:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 9:19 [gentoo-dev] splitted ebuilds for vim and gvim Hannes Mehnert
2002-09-13 9:45 ` [gentoo-dev] Re: [gentoo-user] " Laurent
2002-09-13 10:09 ` [gentoo-dev] " Christian Axelsson
2002-09-13 11:29 ` Hannes Mehnert
2002-09-13 11:08 ` [gentoo-dev] Re: [gentoo-user] " William Kenworthy
2002-09-13 11:21 ` Hannes Mehnert
2002-09-13 15:41 ` [gentoo-dev] " Scott Lampert
2002-09-13 18:03 ` Hannes Mehnert
2002-09-13 18:43 ` Scott Lampert
2002-09-14 14:10 ` Ewan Mac Mahon [this message]
2002-09-14 23:15 ` [gentoo-dev] Re: [gentoo-user] " William Kenworthy
2002-09-15 9:48 ` Dan Armak
2002-09-15 15:24 ` Magnus Therning
2002-09-15 20:00 ` Scott Lampert
2002-09-16 2:15 ` Tom von Schwerdtner
2002-09-16 2:26 ` Tom von Schwerdtner
2002-09-16 5:54 ` Fredrik Jagenheim
2002-09-16 6:31 ` Magnus Therning
2002-09-16 8:38 ` Fredrik Jagenheim
2002-09-16 17:59 ` Magnus Therning
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=Pine.LNX.4.44.0209141505570.24517-100000@kitt.york.ac.uk \
--to=ecm103@york.ac.uk \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-user@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