public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tod M. Neidt <tneidt@fidnet.com>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] gentoo 1.0_rc6_r12 impressions from gentoo newbie (long)
Date: Sun Oct  7 23:56:01 2001	[thread overview]
Message-ID: <E15qTNz-0004L5-00@cvs.gentoo.org> (raw)

Hi!

> 6. When I did 'emerge system' I noticed that latest Linux kernel was being 
> downloaded somewhere.  So I was pretty puzzled when the docs asked me to 
> emerge it explicitely.  Indeed, there was nothing in /usr/src until I did 
> emerge the Linux kernel explicitely.  I wonder why?  Just curious.

'emerge system' downloads the linux sources because glibc depends on
linux-headers. The linux headers are installed in /usr/include/linux


> 8. Emerging vim installed XFree86 4.1.0?!!! Holy cow, man!  I just wanted an 
> editor.  I absolutely HATE e3.  I wish there was some kind of real vi clone.  
> I know e3 was chosen for its size, but still, I could not do any real editing 
> with it.  I couldn't even find how to do search and replace in vi mode.
> 
> Anyway, I was going to install XFree86 4.1.0 anyway, so it wasn't that big of 
> a deal.  But I think something needs to be done about being able to use vim 
> in console mode without X.

You would need to modify your USE variable in /etc/make.conf and remove X, gnome
and gtk. See the depends section of the vim ebuild.

tod

---------------------------------------------------------------------------
This message was sent using Fidelity Networks, Inc Mailman Professional.
http://www.fidnet.com/





             reply	other threads:[~2001-10-08  5:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-07 23:56 Tod M. Neidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-07 21:45 [gentoo-dev] gentoo 1.0_rc6_r12 impressions from gentoo newbie (long) Gold is Heavy

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=E15qTNz-0004L5-00@cvs.gentoo.org \
    --to=tneidt@fidnet.com \
    --cc=gentoo-dev@cvs.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