[gentoo-dev] fcron ebuild

[gentoo-dev] fcron ebuild

[Adam Mercer]

Hi

I've noticed that the fcron ebuild has recently been modifed, it now
uses vim as it's default editor. This causes problems when building a
new system - as xfree is a default requirement of vim and therefore
emergeing fcron also installs X.

I don't think that is a good idea in the chrooted environment, the
default editor should be set to nano, that is gentoo's default editor.

Cheers

Adam

-- 
You cannot avoid the interplay of politics within an orthodox religion.
This power struggle permeates the training, educating and disciplining
of the orthodox community. Because of this pressure, the leaders of such
a community inevitably must face that ultimate internal question: to
succumb to complete opportunism as the price of maintaining their rule,
or risk sacrificing themselves for the sake of the orthodox ethic.
- from "Muad'Dib: The Religious Issues" by the Princess Irulan

Re: [gentoo-dev] fcron ebuild

[Chad M. Huneycutt]

Adam Mercer wrote:
> Hi
> 
> I've noticed that the fcron ebuild has recently been modifed, it now
> uses vim as it's default editor. This causes problems when building a
> new system - as xfree is a default requirement of vim and therefore
> emergeing fcron also installs X.
> 
> I don't think that is a good idea in the chrooted environment, the
> default editor should be set to nano, that is gentoo's default editor.

Sounds like a great candidate for a bug at bugs.gentoo.org.

Although, maybe we should just make the emerge system line be
# USE="-gtk -X" emerge system

or somesuch to avert these kinds of problems in the future.

Also, once we get vim in the build image, then we might be able to meet 
this dependence without actually having to rebuild vim.

-- 
Chad Huneycutt

Re: [gentoo-dev] fcron ebuild

[Alex Holden]

Chad M. Huneycutt wrote:
> Adam Mercer wrote:
>> I've noticed that the fcron ebuild has recently been modifed, it now
>> uses vim as it's default editor. This causes problems when building a
>> new system - as xfree is a default requirement of vim and therefore
>> emergeing fcron also installs X.
> Also, once we get vim in the build image, then we might be able to meet 
> this dependence without actually having to rebuild vim.

Why not use nvi instead, it's much smaller and doesn't depend on X. I 
vote for having a vi clone of some sort but vim is OTT for an installer 
image.

-- 
------------ Alex Holden - http://www.linuxhacker.org ------------
If it doesn't work, you're not hitting it with a big enough hammer

Re: [gentoo-dev] fcron ebuild

[Alex Holden]

Alex Holden wrote:
> Why not use nvi instead, it's much smaller and doesn't depend on X. I 

Oops, I actually meant the "vi" package not the "nvi" package (I thought 
they were the same thing until I looked closer and realised that vi had 
installed itself on top of nvi). How come vi installs to /usr/bin 
instead of /bin - many systems I've seen have a small standalone vi 
installed in /bin so that an editor is available for disaster recovery 
purposes if the /usr partition can't be mounted for some reason.

-- 
------------ Alex Holden - http://www.linuxhacker.org ------------
If it doesn't work, you're not hitting it with a big enough hammer