public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: VIM: No tags file
Date: Sun, 4 Mar 2007 09:41:07 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.03.04.09.41.07@cox.net> (raw)
In-Reply-To: a4a9bfcb0703040004i6ac795d8u51f9ea3619d6f1c4@mail.gmail.com

"Daiajo Tibdixious" <daiajo@gmail.com> posted
a4a9bfcb0703040004i6ac795d8u51f9ea3619d6f1c4@mail.gmail.com, excerpted
below, on  Sun, 04 Mar 2007 19:04:24 +1100:

> I eventually found (from the VIM FAQ) that there should be a
> $RUNTIME/doc directory, which isn't present, despite putting "doc"
> in package.use for VIM, and upgrading it TODAY.
> 
> I 'fixed' it by
> # ebuild /usr/portage/app-editors/vim/vim-7.0.174.ebuild unpack 
> # cd /var/tmp/portage/app-editors/vim-7.0.174/work
> (after some stuffing around with the Makefile and grep)
> # mv -v runtime/doc /usr/share/vim/vim70
> 
> and :help now works.
> 
> So, why isn't emerge putting the doc directory in place?

I'm not a vim user, but that sounds very much like an ebuild bug to me.  
I'd suggest filing it as such, after checking to see if there's a already 
one filed on that (as it may be), of course.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



      reply	other threads:[~2007-03-04  9:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04  8:04 [gentoo-amd64] VIM: No tags file Daiajo Tibdixious
2007-03-04  9:41 ` Duncan [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=pan.2007.03.04.09.41.07@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@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