Hi there,

So a while ago I hacked together a script to do the legwork of downloading/building/installing. To date, I've been using it w/o any real grief (yet), so I thought I'd clean it up and send it out there on the tubes.. who knows, maybe someone else will find it handy (or wants to adapt it to a real package manager or something). Sorry, I'm not savvy on creating RPMs, DEBs, or what-have-you, so yeah.. I can't help with that just yet.

At any rate, here's the useage (pretty simple):

# first time build from SVN (no source yet) update-inkscape

# catch up your build to the latest from SVN update-inkscape

# build a specific SVN version (in this case, -r20036) update-inkscape 20036

Btw, some notes about the script:

1 - This script doesn't take care of Inkscape's build dependencies.. sorry, but the package names differ by distro, so unfortunately I have to leave that up to the user to take care of first 2 - Putting it to work is the usual deal.. put it in ~/bin and 'chmod u+x ~/bin/update-inkscape' 3 - I prefer to keep my source in ~/install/apps/inkscape/trunk (you can change this by editing the ${BUILD_DIR} variable) 4 - when it installs - it installs to /opt/inkscape/${revnum} (I keep a couple revs handy in case the latest doesn't work out) - if you ever want to uninstall/remove an old build, simply 'sudo rm -rf /opt/inkscape/${revnum}' (also don't forget to rm the symlinks in ~/bin) - if you ever want to switch your default 'inkscape' command to an older version, simply run 'ln -sf /opt/inkscape/${revum}/bin/* ~/bin' 5 - it uses 'sudo' for the root privilege stuff (which isn't setup by default on Fedora, but it's pretty easy to, let me know if you got q's) 6 - I did away w/ the normal output flood, and instead replaced them with 'busy dots'... sorry, I didn't implement a toggle switch for this - however, output is by default saved to: ~/install/apps/inkscape/trunk/${cmdname}.log ~/install/apps/inkscape/trunk/${cmdname}-error.log - the one downside to this is that 'sudo make install' is unfortunately saved to the unhelpfully named 'sudo.log' and 'sudo-error.log'

Let me know if you folks have any questions/run into any problems. Hopefully the script source is clear enough to grok, but my bash-fu is still pretty grasshopper.. so if you've got any suggestions for improvement, feel free to let me know.

Cheers.

--Mike