On Thu, 01 Oct 2009 23:12:36 +0300, "Arthur D." <spinal...@mail.ru> wrote: > James Ausmus <james.aus...@gmail.com> писал(а) в своём письме Thu, 01 Oct > > 2009 22:04:38 +0300: > > VI. > Maybe it's called VIsudo because VIM is better alternative for VANILLA,
> hah? Maybe we should stick to the old devfs stuff instead of udev, because the names matches. Maybe we should use fam as our file alteration monitor instead of the newest gaim, because the names matches. Maybe we should continue using xfree86 because a lot of tools are still named the xf* way. Let's assume it: each distro has its defaults and times change. The origin of the name of visudo is at best an extremely poor argument. > I think it's most reasonably to omit that hardcoding line from ebuild. > I'm sure visudo will notice the user about what should be done to make it > work > as expected and that's better behaviour than complaining about missing > /bin/nano, > don't u think so? No, Gentoo assumes nano as a safe default. If you are ripping something that's part of the base installation (in fact, it's part of the system package set) then you should be prepared to handle it yourself. There's a default editor just like there's a default syslogger, a default cron daemon and a default package manager. Maybe we should also start debating about there. Maybe, and following your logic, it would be better to set as default something that might not even be installed because the first two letter of "vim" and "visudo" are the same. If you truly want to find a "solution", you will have to dig much deeper than that, and not just put your preferred editor instead of the one that comes in the gentoo stage files in the ebuild, because that's simply not acceptable. Oh, and your ebuild patch doesn't even bother to check the vim dependency. Oh, and to set a default is not the same than "hardcoding". They are very different concepts. All the programs have defaults on their config files. Assume it, your vim zealotry is getting in the middle. Try to look at it from a distant perspective. Then let the ideas rest a couple of days and come back if you have a proper suggestion other than "set my beloved vim as default". -- Jesús Guerrero
