From: Alessandro DE LAURENZIS <just22.adl@gmail.com>
To: gentoo-dev@lists.gentoo.org, gentoo-user@lists.gentoo.org
Subject: [gentoo-dev] vim and gvim package split
Date: Thu, 31 Oct 2013 23:02:12 +0100 [thread overview]
Message-ID: <20131031230212.1ea303a9@egeo.atlantide.net> (raw)
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
--
Alessandro DE LAURENZIS
[mailto:just22.adl@gmail.com]
LinkedIn: http://it.linkedin.com/in/delaurenzis
next reply other threads:[~2013-10-31 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 22:02 Alessandro DE LAURENZIS [this message]
2013-11-01 0:45 ` [gentoo-dev] vim and gvim package split Kent Fredric
2013-11-01 16:52 ` [gentoo-dev] " Alessandro DE LAURENZIS
2013-11-01 17:45 ` Steev Klimaszewski
2013-11-01 18:23 ` [gentoo-dev] " Ciaran McCreesh
2013-11-01 19:50 ` Alessandro DE LAURENZIS
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=20131031230212.1ea303a9@egeo.atlantide.net \
--to=just22.adl@gmail.com \
--cc=gentoo-dev@lists.gentoo.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