At the moment, users can upgrade installed apps from antiX-M7 to antiX-M7.5-test, but you won't get the antiX changes ie changes in wallpaper, fluxbox and icewm configuration, controlcentre, scripts etc.

I'm looking at a way to automate this process, but don't know the best way to go about it. Here is what I would like to happen.

Either via the smxi script, or another one, download a tarball or .deb with all the new changes and extract all of it to the correct places so the user does nothing, or very little.

This still will not make an upgraded M7.2 (even less antiX-M7) exactly the same as antiX-M7.5 as some apps have changed.

Any ideas, helpers welcome.

An xdelta patch will work for those that keep the CD image. Most of us I would think.

By the way I love the test1 wallpaper. It relly draws me in....

True, but the idea is so that people wouldn't have to install the newest version, but simply apt-get the newer antiX stuff.

If you look carefully, antiX has very little from MEPIS (except the engine LOL), a few antiX scripts and config apps, and the rest is Debian (probably 98-99%)

anticapitalista wrote:True, but the idea is so that people wouldn't have to install the newest version, but simply apt-get the newer antiX stuff.

If you look carefully, antiX has very little from MEPIS (except the engine LOL), a few antiX scripts and config apps, and the rest is Debian (probably 98-99%)

I noticed that. MEPIS has been a great platform, but I was wondering if you were hedging your bets so that antiX would continue to have a solid base platform, or do you just like to have something slightly"hot and spicy"? __{{emoticon}}__

Would it be possible to alter some of UnicornRider's scripts for this purpose. It had some stuff that would d/l to a directory and install, painless.

Create a list of all new apps, and all apps to be removed.

Then, if there are other files to be installed make a list of those, full paths etc.

After that, scripting it is usually trivial, as long as no config stuff needs to be updated, or only a few simple configs need updating.

h2 wrote:Create a list of all new apps, and all apps to be removed.

Then, if there are other files to be installed make a list of those, full paths etc.

After that, scripting it is usually trivial, as long as no config stuff needs to be updated, or only a few simple configs need updating.

Say, h2! So far smxi is working REAL well with AntiX. I am going to go a bit further with SimplyMEPIS. I am going to switch it from Etch to Sid. I already switched it to Lenny, but the Iceape browser and the Iceweasel browser both became VERY unstable - I assume that is due to plugins, Flash, Java, or something along those lines. I have seen none of that behavior before in ages, so I am suspecting Lenny has some dirt in it. I am going all the way to Sid with that old MEPIS install and see how smxi does. I suspect it will do much better with tools that work,

Will let you know later. As far as interaction on the AntiX stuff, it has been flawless as far as I can tell, have not run into a single issue.

re iceweasel etc, I lost my iceweasel on my oldest install, and can now only run swiftfox on it. I cannot figure out why that install failed, it's always been sid, from kanotix to sidux. It has nothing to do with profiles or plugins, I tested all possible things, and it's something else in the system, of older systems, but I don't know what.

the iceweasel 3 upgrade was a huge one, and it requires a bit of preparation.

Best is to remove / purge all iceweasel, seamonkey stuff prior to the upgrade I think. I believe it may be a lib xul runner issue, but i"m not sure.

h2 wrote:re iceweasel etc, I lost my iceweasel on my oldest install, and can now only run swiftfox on it. I cannot figure out why that install failed, it's always been sid, from kanotix to sidux. It has nothing to do with profiles or plugins, I tested all possible things, and it's something else in the system, of older systems, but I don't know what.

the iceweasel 3 upgrade was a huge one, and it requires a bit of preparation.

Best is to remove / purge all iceweasel, seamonkey stuff prior to the upgrade I think. I believe it may be a lib xul runner issue, but i"m not sure.

For what it's worth, Iceweasel and Iceape both work for me on sidux and antiX, plus now that I took my SimplyMEPIS to Sid - and spent the better part of the night working on it, Iceape and Iceweasel seem to be behaving once again.

But you are right, if they act up, torch 'em, get rid of configurations and start over. If I see any repeated instability again, that is what I will do. Right now I only saw it on one distro and I only saw it when I went from Stable to Testing, went away when I went to Sid. That was on my SimplyMEPIS setup. Seems to be fine now.

BTW, antiX and sid work together nicely with smxi. I have it looking like a sidux system with a antiX appearance. Still have all the lightweight antiX stuff, so it makes for a nice system. I call it my antiX-sidux hybrid! __{{emoticon}}__
Debian on Steroids and Mood Stabilizers plus lean and mean! What a combination! __{{emoticon}}__

Last night's new xul-runner in sid fixed, finally, my iceweasel. I have to admit, although swiftfox was ok, it has some annoying things which I don't like, so I'm glad to be back with iceweasel.

Again, the instability, if you are running a fresh profile ( iceweasel -profilemanager) is now fixed. If it's a corrupted profile, start fresh after copying your user data.

h2 wrote:Last night's new xul-runner in sid fixed, finally, my iceweasel. I have to admit, although swiftfox was ok, it has some annoying things which I don't like, so I'm glad to be back with iceweasel.

Again, the instability, if you are running a fresh profile ( iceweasel -profilemanager) is now fixed. If it's a corrupted profile, start fresh after copying your user data.

You ought to try iceape sometime, h2, unless you are absolutely set on some Firefox - iceweasel plugins. Some plugins work with iceape - a.k.a. Seamonkey. You may know that Seamonkey is the carry on of the original Mozilla suite. What you may not know is that many of the performance improvements in the core engine are worked out first in Seamonkey. I find it to be, in general, more stable and more conservative with memory usage, even though it is a suite, than the stand alone Firefox code. My guess is that part of it is quality control and that part of it is that the XUL stuff used by Firefox and Thunderbird consumes additional memory resources. Whatever the reason, I really like the original suite, now called iceape in the Debian DFSG world! Give it a try some time!

BTW, as I believe you pointed out, Iceweasel released version 3.0.1 into Sid Thursday and I grabbed it, and at the same time Iceape released version 1.1.11, both of which implement a few more security related fixes.