Why isn't everyone compiling wine

[Matt Bailey]

I don't think the dependency issue is the main thing keeping Linux from
mainstream, but I heartily agree it's a real issue. I really like Linux
(especially since getting Slackware) but chasing dependencies is the
single most annoying thing about it. Sometimes after finding and
installing a few packages then realizing I've run into a depedency trail
that seemingly has no end, I just give up in frustration. What's really
bad is when you have to think for a minute to remember what software you
were trying to install in the first place........

	-Matt Bailey

Julian Hall wrote:
> 
> I've been lurking on this mailing list for several months now as a new user
> to Linux and to Wine.  I agree completely with what Leo is saying.  Windows
> users in general will all have their favourite software they want to run, be
> that a game or a specific application they cannot do without.  Linux may
> well have a viable alternative, but some people just like to use what they
> already know and not waste time learning some new program to do the same
> thing.
> 
> So we turn to Wine.  I have to say I have had mixed results, largely I admit
> due to not spending enough time digging into the root causes and various
> other problems I have has with Linux in general.  For example the video
> editing program I use TMPEG Encoder worked first time in Wine with no
> messing about, largely I suspect because the programmers wrote it to be self
> contained.  The same is true of Hunter.  However Paintshop Pro 7 did not
> want to play, and to be honest I haven't had time to really look into why.
> 
> Having said that, to address the original point, Windows users will not move
> to Linux unless they are presented with a simple alternative to Windows.
> They will not "simply compile X Y or Z" for two reasons:
> 
> 1.  They will not know how, and regrettably there are those in the Linux
> community who assume knowledge and are unwilling to help other than "say
> "RTFM".  There are also those I am happy to say such as this list who WILL
> help and all credit and thanks to those of you who offer solutions to us
> poor ignorant Linux newbies :)
> 
> 2.  If dependencies are not satisfied TELL THE USER which ones they are, so
> they have a fighting chance of resolving the problem.  Not all Linux
> installs are that kind.  Dependencies not being satisfied smacks of "You
> need Internet Explorer 5 to install this program", only it is a much worse
> situation because at least with this message you are told One Program which
> will fix the problem.  Far preferable to Linux telling you to find half a
> dozen obscure packages and not having the kindness to tell you where to
> look.
> 
> Dependencies are the one thing preventing wholesale moves to Linux.  I
> recently installed a new Nvidia Geforce FX5600 and Nvidia were good enough
> to provide ONE program to run and idiot proof instructions (just as well,
> they're dealing with ME here ;)).  That was painless.  However, getting a
> reliable software DVD player is a nightmare due to dependencies.
> 
> Unless ex-Windows users are presented with "all in one" installers like the
> Nvidia one there will be no wholesale move to Linux.  We are used to
> "doubleclick Setup.exe" and it does its' stuff.  I have been using computers
> 20 years, 8 of them in Windows, so I am prepared to do a bit more than the
> average user.  But that's me, and the average button pushing user will look
> at a dependency demand and reinstall Windows.  All it needs is for an
> installer to include the necessary files *should they be needed*, or even if
> the package is on a website, at least include links to the pages for all the
> dependencies if they are not in the package.
> 
> Anyway I think I've wandered off topic here, so apologies if I have and I'll
> get off my soapbox :)
> 
> Kind regards,
> 
> Julian