Review: SAngband

[TJA]

PART I.
Compilation

unrar x sang100src.rar
mv sang100src tmp
mv tmp/sang100src/ .
rmdir tmp
cd sang100src
cd src
make -f Makefile.std
make -f Makefile.std install
cd ..
./sangband

Works!
Great!

Has no configure Skript, but a working Makefile.std - the base of what we can wish for

Note: sang100src.rar contains the structure sang100src\sang100src\...

[andrewdoull]

PART I.
Compilation

Do we get a preview of what parts II, III and so on consist of?

[TJA]

Now, it´s called "Review" - i am trying to write down my adventures and impressions while evaluating those variants
As a service to other who may be interested in them ....

Also, of course i hope that the respective maintainers have a look at this and potentially fix the problems.
I know enough people who can and do say "./configure ; make ; make install" - but not one step more!
The more easy a variant can be compiled, the more people may try to have a look at it

[pav]

Hmm, never noticed S source come as a RAR archive. That's just plain wrong...

[TJA]

Got that from here http://angband.oook.cz/variants.php?variant=sangband
(as a rar) and also from the download-part of the homepage: http://runegold.org/sangband/files/sang100src.rar

[andrewdoull]

Hmm, never noticed S source come as a RAR archive. That's just plain wrong...

Its even more wrong when I realised the easiest way to unrar it on a Mac is to run the windows version of 7zip in Cross Over Office...

[Magnate]

What on earth is wrong with rar? www.rarlabs.com - there's a free trial download for OSX, among all the others.

What stuns me is how easily the OP compiled it. I had to spend ages working out which -dev libs I needed and installing them. I can only presume he has some kind of kitchen-sink installation.

CC

[TJA]

What´s kitchen-sink installation?!?
:-O

[Magnate]

"Everything but the kitchen sink" is an old expression used in the UK, I think it originally comes from an advert about how much space there was in a certain car.

I meant where you put in the install CD (or rather DVD nowadays) and just click "install everything", so you get Gnome and KDE, half a dozen different window managers, all the development libraries that most people never use, etc. etc.

Don't get me wrong, there's nothing wrong with doing that, it makes installation very simple. Hard disks are big enough nowadays that there's no longer any problem with installing unnecessary packages. Personally I can't shake off the habit of conserving disk space (from when 40 megabytes was a huge drive), so I only install one window manager, one mail client, one browser, and only the libraries I actually need. This is fine with Debian, because anything I want to install automatically tells me what else it needs to install to work (its "dependencies"). The problem only arises when I try to compile something outside the package system, like a new *band. The requirements were clear in the docs, but I had no way of translating them into which packages I needed to install. So it took ages.

Ho hum.

[TJA]

I also only install what is realy needed - and i want to know what is needed