Slashdot Mirror
How To install Neverwinter Nights on Linux
Joe Barr writes " As soon as I saw the news that BioWare released a beta of a Linux client for its popular and successful Neverwinter Nights title, I downloaded the beta (registration required) and went shopping for the prerequisite retail Windows version of the game. Before I proceed, let me offer this brief warning: Neverwinter Nights is the mother of all timesinks. Do not follow my path unless you have nothing important you want to get done for the next week or so."
If you think NWN is a huge timesink, then you've obviously never played the original Baldur's Gate. We're talking about a magnitude scale of at least 4 here.
At the end of Baldur's Gate, after having thuroughly explored every nook and cranny of the world, I'd accumilated 212 game days of play. That's approximately 2 hours per game day: 424 hours. (If I recall the conversion properly.) That's 17 and 2/3rd days, straight. Now, consider your average person sleeps 8 hours a night, it equals roughly 26.5 days of gameplay, not taking into account things like bathing, eating, and work.
And that statistic doesn't even begin to take into account the many hours spent saving, loading, and replaying sections of the game that are all but impossible to perform well. I'd say that, realistically, you can easily double or triple my figures.
In contrast, it took me less than a week to beat NWN while going about school, sleeping, eating, and other various activities.
~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
Read the EFF's Fair Use FAQ
*just in case you were wondering, portage already has an ebuild for NWN server, for all those people getting their nwn running in lin
.rpm, .deb, and .ebuild (gentoo) are AFAIK all script-based, or at least have scripting capabilities, so there's no such thing as an "application that can't be packaged". If the app couldn't be packaged, then you couldn't install it by hand, either. (Debian even supports asking the user for input as part of the install process.) .rpm and .deb, by convention more then anything else, are supposed to be binary-only packages. There's nothing technically stopping them from compiling source code (except perhaps that you aren't supposed to need a compiler on such systems).
.rpm and .deb, if not essentially impossible.
Ebuilds, on the other hand, embrace compiling source to the near exclusion of all else, so for those packages that can't be wrapped into a nice binary that will work for everyone, an ebuild can still be created. In fact it is common practice to make such wrappers, and ebuilds for other uncommon situations as well.
For instance, Sun no longer allows automatic downloads of its Java distribution, so Gentoo has an ebuild that asks you to download the Sun-provided tarball and put it in a particular place, then proceeds to open the tarball and put it in the correct place, also allowing you to have full packaging system support for uninstalling it. This is harder to do with
Ebuilds are a superset of binary packages, such that they can package anything you could install by hand, simply because they are a higher level. (This is where the sandbox support comes in real handy, since you don't have to specify what files were installed and what files to uninstall; the sandbox picks it up automatically and I expect all packaging systems to pick that up eventually.) Of course, there's a price to pay for that in compile time, since virtually by definition it's impossible to have this flexibility and still distribute binaries*, so it's not like it's a absolutely superior method in all cases. Tradeoffs just like anything else.
*: People keep talking about having a "package repository" for Gentoo which would function as a giant multi-person cache of Gentoo compiled packages, which you could then grab instead of compiling. Nobody AFAIK has made any progress beyond suggesting it, because even with just the obvious configurations (the four or five main processor types, the three or four good optimization settings from conservative to ultra-aggresive, the three or four obvious USE settings from conservative to everything) mulitplied by 10 or 20 gigabytes for a pure install means that nobody can afford to host it, and people would still find it too limiting.