Although I was reassured (after hideous problems with dropline) that freerock would not completely take over my computer and bugger it u if I ever attempted to remove it, the jammy little sod stole gtk and all the other required libraries, so I'm currently trying to patch up the holes in dependancies and getting horrible errors whilst having gaim, firefox and the like entirely unavailable.

Is there anywhere I can get hold of a package which will update the whole lot in one go and fill in all the holes, or alternatively, somewhere that has all the packages.

I've been doing a pretty patchy job at installing via the tarballs, and a couple of packages, but I'd really like to do this properly (and get back on firefox as soon as possible)

Nope, I've sorted it

I went back to the frg site and downloaded the packages from there.

Although I still think that its fairly stupid to use a grep command looking for the text frg which pipes to a removepkg command, when you're upgrading essential libraries and putting frg in the name!

I've emailed frrerock to tell them exactly what I thought of their package labelling!

I don't use Freerock but did you notice on their website they note, "When uninstalling, you will have to reinstall some packages from the l disk set on your slackware cdrom. Please see replaced slack packs text for more information."

When I removed FRG I used swaret to fix the missing dependencies. Just run 'swaret --dep' and that should reinstall what is missing.

Kent

I'd be interested to know if Swaret installed only those pkgs listed as being replaced. It can get a little aggressive on what it considers a dependency at times. If someone does this again in the future it would be something worth looking at just for the information.

I'm a bit curious. How else do you expect that Freerock and company should do this? I think that their method is perfectly appropriate. Several libraries (like your missing GTK+2 that got removed when *you* initiated the removal) must indeed be replaced in order for GNOME to work properly. There is no way around it. Adding a tag "frg" to the end of the filename, simply indicates that it is a Freerock GNOME component. Upgradepkg has no problems with this, so it's perfectly acceptable (in fact, it's a standardway that most "unofficial" packages get tagged).

A better solution might be in order, instead of a simple complaint. I don't expect that you'll be able to come up with much though, due to the limitations of Slackware's package management system.

I'm not sure what they are on about. The file naming method is definitely appropriate. It even lists specifically at their website what packages (only a handful) should be replaced if FRG is uninstalled. Reading is fundamental.

I agree. We'll have a similar list (with only a few different packages at that) on the Dropline site very soon.

Just a bit of an update... Some of the points you complained at me about just then were pointed out to me by the FRG team... I apologised... A lot...