Your right I guess I was just a bit intimidated since I know very little about installing anything for vectorlinux. Take milkytracker as an example. I downloaded the package built for vector and instead of installing the binaries (something I guess I still don't know how to do) I somehow compiled it from source, following what I thought was the install instructions for the vector package... DOH! - Hey but at least it worked!
Actually, what you downloaded was the source as well

. uelsk8s posted a link to the source, not to the package since it hadn't been moved to the repository yet. VL packages end in .tlz, and slackware .tgz packages usually work as well.
The rest of these I should try to work on myself before bugging everyone here. I'm sorry to admit I didn't even try myself before posting the requests. I guess I just figured so many people here know exactly how to get these going... But your right its rude to post so many so fast. I am just very excited when I look around at some of these things and I don't have the experience to get them going on my own.
Hey, no problem, just thought I should mention

.
Of course, I never will if I don't fiddle with them myself, so your right I'll try more stuff
on my own before coming here for help.
it's the best way to learn.
Someone should post a tutorial for newbies like me about how to install vector linux packages
There's one on your system, it should be here: /usr/doc/VLHelpCenter/manuals/vl5_slaptget_en.html
if you could take the milkytracker vector package as an example and tell me how to install that as a vector package properly, I'd appreciate it.
There's a
HOWTO about installing from source and a
HOWTO on packaging for VL 5.9.
I currently don't have much time to package anymore, but once you get the hang of it it isn't too hard if the package doesn't have build errors or insane amounts of dependencies. That being said, if you're happy building packages just for home use checkinstall and vpackager can do a great job making packages. Unfortunately, packages built that way can't be shared if you take GPL2 very literally, it says you have to provide the script that was used to create the package together with the sources and the package (well it uses other words than that).