public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: gentoo-core@gentoo.org
Cc: gentoo-dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-core] Creation of 'virtual/vi' to satisfy builds
Date: Thu, 10 Jul 2003 00:33:41 +0200	[thread overview]
Message-ID: <20030710003341.4f0e9a5c.spider@gentoo.org> (raw)
In-Reply-To: <20030709215856.GB19946@inventor.gentoo.org>

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

begin  quote
On Wed, 9 Jul 2003 15:58:56 -0600
Daniel Robbins <drobbins@gentoo.org> wrote:

> On Wed, Jul 09, 2003 at 01:00:16PM -0400, Brad Laue wrote:
> > Hi all,
> > 
> > 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?
> 
> Should we have a virtual/vi and a virtual/ex? Or should we require
> that anything providing virtual/vi includes an ex?

Anything that provides vi should out of compability reasons also provide
ex.

Now, why isnt this discussion on -dev?
//Spider

(not removing quotes due to crossposting)


-- 
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2003-07-09 22:33 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   ` Spider [this message]
2003-07-10  2:28 ` [gentoo-dev] Re: [gentoo-core] Creation of 'virtual/vi' to satisfy builds Aron Griffis
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=20030710003341.4f0e9a5c.spider@gentoo.org \
    --to=spider@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