I'm working on an AVP script that will download, build, and install AVP, and I am in need of a good icon...

Which one do you like the best?

3 and 4

4 & 7

Three

Four

Three

Okay. I used 2, because it was the smallest one, and easiest one to integrate into my script. On my desktop, I use 7 though.

So, here's the script: http://icculus.org/~dolson/files/avpmakeinstall.sh

If someone wants to test it, go for it. It does this:

- makes a tmp dir called avptemp in the directory from which you run it
- downloads the CVS source
- compiles it
- downloads a perl script for changing the case of filenames
- creates the icon
- creates the menu entry for Debian and Mandrake (or at least it should)
- installs the binaries to /usr/local/games/avp
- installs a symlink in /usr/local/bin
- (optional) copies data over from a Windows install of AVP

Tested on Debian Sid and Mandrake 9.1...

NO WARRANTY.

This script will likely replace my old RPMs and tutorial, if I ever decide to update that tutorial...

Please post and let me know if it works for you.

What icon do you think i should use?

various answers

Ok i will use one that no one picked :wink:

I guess that if all the icons were that same size 2 is the most easily recongnised.

4 is nice so is 1

4 Definitely takes the cake on this one

hehehehehehehehe. So far my installer for UT SF 1.80 is coming along pretty good. I wish I had of started doing this along time ago. Takes a lot of stress out of work related matters and give something to tinker with. DOlson do you need the store CD ?

Hi, Dolson!
Just a few things about your script



Instead of using the "$USER" != "root" one; for example:


Unles you run "su -" or start a console directly as root the $USER variable keeps untouched because you don't login as root; so it is better to check the UID number.

Whereever you are? wouldn't be better to define a full path to the temp directory, something like mkdir -p /tmp/avptmp

I have complaints about the rest of the script, mostly because there aren't checks at all (except in punctual user interactive points) to see if the previous command went right before executing the next one. Implementing some checks is as easy as check the return status of the previous command, or put things like "command || exit $?"

Oh! instead of thousands of echos, you can use a few here documents (<<-EOF [...] EOF) either for the stdout output or the script generators (would be easier to maintain later).

Despite what it seems, this is a friendly post

Brilliant idea :!: