Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 5522 - fcron-2.0.0-r1 dependancy on VIM causes large dependancy install on fresh system install with default USE flags
Summary: fcron-2.0.0-r1 dependancy on VIM causes large dependancy install on fresh sys...
Status: RESOLVED DUPLICATE of bug 4242
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Ryan Phillips (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-24 16:57 UTC by Richard C
Modified: 2005-07-17 13:06 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard C 2002-07-24 16:57:54 UTC
Following the Gentoo install guide, when you get to the section on installing a
cron agent, if you happen to pick fcron, your in for a bunch of extra packages
you probably don't want.

Since vim is a required dependancy, and vim grabs X because of the default USE
settings, and X grabs a bunch of other things, and poof this fcron build is
pretty heavy..

With default use flags, I get :
opengl-update
xfree-4.2
gpm-1.2
intltool-0.22
gtk+-1.2.10
cscope-15.3
vim-6.1
mailbase-0.00
ssmtp-2.38.14
fcron-2.0.0-r1

Poor newbie doing his first install is going to be waiting a long time for this
fcron package to build :)

Previous bug on fcron suggests killing vim and using nano, but doesn't mention
the critical effect of vim req. on a fresh install.
Comment 1 SpanKY gentoo-dev 2002-07-24 20:49:19 UTC
the default USE variable is setup to install X and stuff, so they would have 
installed those packages anyways ;)
Comment 2 Seemant Kulleen (RETIRED) gentoo-dev 2002-07-24 21:02:18 UTC
on the other hand this is such a recurring issue, that we might benefit by
thinning vim out -- may be vim and gvim should be separate ebuilds?

I dunno. Ryan, thoughts?
Comment 3 Ryan Phillips (RETIRED) gentoo-dev 2002-07-25 03:14:19 UTC
It is actually not a bad idea.  I'll look into it. 
Comment 4 Ryan Phillips (RETIRED) gentoo-dev 2002-07-30 02:40:55 UTC
After thinking on this for awhile I was thinking that having two ebuilds would
be sort of pointless.  We have USE variables for specifically this reason to
enable and disable compile options.  Granted, some people may only want the
console version, they could check the mailing lists, the forums, or the ebuild
itself to figure which flags need to be disabled.

What is everyone else's thoughts?
Comment 5 Richard C 2002-07-30 13:56:30 UTC
Well even if you take "X" out of the equation, there is still a mess of baggage
that comes with VIM..  Fcron only needs a very simple editor, and Gentoo
supplies nano..

A VIM use variable perhaps ?

I don't use vim, don't need vim, and don't want vim.  I have to "fix" the fcron
ebuild to make it so..  

-Richard C
vivivi.. the editor of beast..
Comment 6 Ryan Phillips (RETIRED) gentoo-dev 2002-07-30 14:37:15 UTC
Maybe a better idea would be to remove the vim dependency from fcron and
add app-editors/vi ???
Comment 7 Olivier Crete (RETIRED) gentoo-dev 2002-08-01 14:23:45 UTC
This is linked to bug 4242... But fcron should not depend on "vim" but.. on any
text editor.. nano should do the job.... or nvi or any other editor... 

Editors should provide a virtual/editor that could be required (like debian does)
Comment 8 Ryan Phillips (RETIRED) gentoo-dev 2002-08-07 03:17:11 UTC
How about if I change the ebuild to not point to vim, but rather ${EDITOR}
It is set in /etc/profile
Comment 9 Ryan Phillips (RETIRED) gentoo-dev 2002-08-09 03:19:18 UTC
comments?
Comment 10 Ryan Phillips (RETIRED) gentoo-dev 2002-08-10 22:12:05 UTC

*** This bug has been marked as a duplicate of 4242 ***