Linked by Jordan Spencer Cunningham on Mon 11th Jan 2010 15:57 UTC
Original OSNews Interviews A few weeks ago, we asked for the OSNews community to help with some questions we were going to ask Aaron Griffin from the Arch Linux team, and the response was glorious and somewhat phenomenal. We added those questions to our own and sent them on over, and then we were surprised by receiving not only Aaron Griffin's responses but answers from various individuals from the team.
Thread beginning with comment 403711
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Only problem sometimes is that one application could require 10+ dependencies or more, with many times those dependencies branching out. For example I will use wine since it is the most recent example I can think of.

The problem with your example above is that wine is a 32-bit app. and it requires a couple of 32-bit dependency packages. Since Arch 64-bit implementation is very lean, there are few (if any) 32-bit packages on it.

But like all of Arch, if you read the forums, you will get easy instructions, complete with community repos that allow you to install it in no time.

Wine32 dependencies are the same no matter the distribution (package name may differ, but same deps). Check on a Ubuntu, or Fedora and compare. But more important, why you want a 64-bit OS, to run a 32-bit wine, whith the extra 32-bit libraries, running side by side, taking double the memory?

Do you have more than 4 GB? Otherwise is a waste. Maybe a 32-bit OS is better for you.

Edit: typo

Edited 2010-01-12 15:41 UTC

Reply Parent Score: 2

cerbie Member since:

0. bin32-wine is 64-bit; wine is 32-bit.
1. 64-bit WINE will not run 32-bit Windows apps.
2. If you have more than 3.5GB, or more than 2.5GB, with a good video card, 64-bit is very handy, even before its other performance benefits come in.
3. Why should anyone be dictated what OS they should run, to use multiple layers of 3rd-party unsupported software?

Reply Parent Score: 2

molnarcs Member since:

0. bin32-wine is 64-bit; wine is 32-bit.
1. 64-bit WINE will not run 32-bit Windows apps.

Wrong. Bin32-wine is NOT 64 bit of course (why would it be called bin32 then?) - it's 32 bit with a wrapper for x86_64 Arch. As to your second point, I have bin32-wine installed:

[molinari@Helios ~]$ pacman -Q | grep wine
bin32-wine 1.1.36-1

and I'm happily playing Morrowind on it ;)

Reply Parent Score: 2