From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] vim and gvim package split
Date: Thu, 31 Oct 2013 22:03:23 -0400 [thread overview]
Message-ID: <20131101020323.GA14264@waltdnes.org> (raw)
In-Reply-To: <20131031230212.1ea303a9@egeo.atlantide.net>
On Thu, Oct 31, 2013 at 11:02:12PM +0100, Alessandro DE LAURENZIS wrote
> I guess this is an already debated topic, but I only found this very
> old thread on the subject:
>
> http://article.gmane.org/gmane.linux.gentoo.devel/4328
>
> which contains the original communication of the ebuild split and some
> discussions and observations that probably are no more applicable.
>
> I'm absolutely convinced that one of the gentoo strengths is the USE
> variable handling compile time options, so I do not see any points to
> split packages when not absolutely needed.
>
> In case of vim-core/vim/gvim (and vim-qt?), I cannot understand
> the reason... Are still there advantages in doing so?
>
> Thanks for your time
While you're at it, can you ***PLEASE*** get rid of the ewarn message
> WARN: postinst
> Note that the English word lists are no longer installed by
> default.
It's been in there for what seems like forever. I just checked
/var/log/portage/elog on the PC hooked up to my TV set. I installed
Gentoo on it June 22nd, 2010. The message was in there back then.
That's over 3 years!!! Enough already. I go through the messages in
/var/portage/elog after every update. It's annoying to have that same
old message polluting the logs.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
prev parent reply other threads:[~2013-11-01 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 22:02 [gentoo-user] vim and gvim package split Alessandro DE LAURENZIS
2013-11-01 2:03 ` Walter Dnes [this message]
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=20131101020323.GA14264@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@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