[gentoo-dev] updated vim eclass and ebuilds

[gentoo-dev] updated vim eclass and ebuilds

[Aron Griffis]

Just wanted to mention the following vim changes committed today:

- 6.2-r1 is now available, including patches 1-57.
  It's marked ~arch for now since there are no particular bugs
  driving it to be unmasked yet.

- vim.eclass now sets IUSE correctly for the different ebuilds
  (vim-core/vim/gvim).  Thanks to Wayne Davison for the patch.

- The cscope dependency is now optional based on USE=cscope (which
  is not in the default profiles).  This is to break the
  vim->cscope->emacs chain (or at least make it optional).

Enjoy!

Aron

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] updated vim eclass and ebuilds

[Phil Richards]

In article <20030729210355.GA18211@zk3.dec.com>, Aron Griffis wrote:
[...]
>  - The cscope dependency is now optional based on USE=cscope (which
>    is not in the default profiles).  This is to break the
>    vim->cscope->emacs chain (or at least make it optional).
[...]

As far as I can see, cscope-15.3.ebuild isn't dependent on emacs.

cscope-15.4.ebuild *is*, but there is a "emacs" USE flag controlling
that dependency (and I have -emacs in my USE flags :-).

Isn't that sufficient to break the vim->cscope->emacs chain?

phil
-- 
change Reply-To: username to "phil" to email me


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] updated vim eclass and ebuilds

[Aron Griffis]

Phil Richards wrote:	[Wed Jul 30 2003, 03:13:27AM EDT]
> As far as I can see, cscope-15.3.ebuild isn't dependent on emacs.
> 
> cscope-15.4.ebuild *is*, but there is a "emacs" USE flag controlling
> that dependency (and I have -emacs in my USE flags :-).

Right, that breaks the dependency chain too.  Considering how many
people don't know or care what cscope is, there's no reason for vim to
depend on it by default.  A USE flag is the appropriate solution.

Aron

--
gentoo-dev@gentoo.org mailing list