From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-core@gentoo.org, gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-core] Creation of 'virtual/vi' to satisfy builds
Date: Wed, 9 Jul 2003 22:28:46 -0400 [thread overview]
Message-ID: <20030710022845.GA28875@time> (raw)
In-Reply-To: <3F0C4A20.9030704@gentoo.org>
Brad Laue wrote: [Wed Jul 09 2003, 01:00:16PM EDT]
> I'm running into builds requiring the 'ex' binary, which is provided
> by several vi clones.
>
> I'd like to suggest the creation of 'virtual/vi' to satisfy this
> problem. Are there any comments/objections?
In principle, I don't have a problem with this, but I have a couple
questions:
1. Does having a virtual require that only one of the options is
installed at a time? I recall this being the case with
ssmtp/postfix/etc, but maybe that's specific to those ebuilds.
I wouldn't want Gentoo to be restricted to a single vi-clone on a
system.
2. What are the builds that require ex? That's a pretty strange
requirement, to be honest. Most builds I've seen require ed for
non-interactive editing, not ex.
3. What about the case where you install vim, then install nvi, then
uninstall nvi? In that case /usr/bin/ex will disappear from the
system (because the files conflict between packages), but the virtual
will still be "satisfied".
4. What are the ebuilds that provide ex? At first glance, I only see
nvi and vim.
Aron
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-10 2:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F0C4A20.9030704@gentoo.org>
[not found] ` <20030709215856.GB19946@inventor.gentoo.org>
2003-07-09 22:33 ` [gentoo-dev] Re: [gentoo-core] Creation of 'virtual/vi' to satisfy builds Spider
2003-07-10 2:28 ` Aron Griffis [this message]
2003-07-10 3:17 ` Brad Laue
2003-07-10 8:32 ` Spider
2003-07-10 11:55 ` Aron Griffis
2003-07-10 16:18 ` Spider
[not found] ` <3F0CD23C.3010808@gentoo.org>
2003-07-10 11:51 ` Aron Griffis
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=20030710022845.GA28875@time \
--to=agriffis@gentoo.org \
--cc=gentoo-core@gentoo.org \
--cc=gentoo-dev@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