Yes, but what do you do when you have a brand new
Linux user with the following criteria:
1. They are on a distro with no Wine RPMs
2. They haven't the slightest idea what configure/
make/ make install means or does
Besides, on the wine-users alias, new users who
install RPMs have no idea there is a config file
because the RPMs don't create it for them.
Wineinstall does everything... Am I understanding
right that "make install" will create the fake c drive
and install the config file? :)
Anyhow, the criteria above... That was me when I
first tried Linux. Again, without wineinstall, I
probably wouldn't be on Linux today.
It may be a redundant feature, but "configure/ make/
make install" is definately not a replacement for
"ease of use." ;)
Hiji
> And this is the problem: having wineinstall around
> makes
> it a self-fulfiling profecy: in theory, you should
> get
> the *same* result (and working version) if you run
> wineinstall
> or configure/make/make install. But because we have
> wineinstall
> people don't bother to fix the standard process, and
> instead
> patch wineinstall.
>
> So, if RPM's don't work, or configure/make/make
> install doesn't
> it's a bug. It needs fixing. As Dan put it,
> wineinstall should
> just be:
> configure && make && make depend && make install
>
> --
> Dimi.
>
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
