Amiupdate

How it actually determines, which programs are installed?

AppDir: or AppPaths: or both.

Amiupdate website says, that Sketchblock is compatible. When I open AmiUpdate menu, Updates -> compatible applications. List is quite short.

At least Sketchblock is not there.

Sketchblock writes to Appdir but not to AppPaths.

I copied Sketchblock file from Appdir to AppPaths and no difference.

So, how AmiUpdate determines location on compatible apps ?

Sorry about typos, I really need to get new kbd...

@Mlehto

Ermm I've not been updating the database re sketchbock for a while, as I haven't written an proper autoupdate script. So that's why it doesn't show in AmiUpdate.

Just get it from os4depot.net, and install by hand, that all AmiUpdate would do anyway till I write a proper autoinstall.


To the more general question, I think Appdir: is the prefered for more recent apps that run on AmigaOS 4.1 and later AppPaths: works for older apps.

@broadblues

Ok, it wasnt amiupdate problem then :)

Actually Im installed it allready. I just dont understand why it wasnt in amiupdate supported list.

Actually, I copied Sketchblock from appdir to apppaths by hand, and now it materialised to list.

So, question remains,where on heck they have to be or is there some bugging somewhere ?-)

Have to check...

@Mlehto

What supported list?

@broadblues

Launch amiupdate.

RMB and from menu click update and pick compatible applications.

There opens list of them.

For test I copied everything (related) from appdir to apppath and suddenly I have over 700 amiupdate supported application...

It is easy to get all apps to automated update in amigaland :)

So, amiupdate scans supported applications from apppath. Not appdir

@Mlehto

I see the list you mean.

That must just scan ENV:AppPath/ but ENV:AppPath is not recomended for new apps so the listing tecnique must be out of date.

AmiUpdate scans for AppDir:SketchBlock

as this excerpt from the ram:au.log (with verbose enabled in the update prefs Gaeberal tab) shows

01:37:45 Now checking: SketchBlock...
01:37:45 Version string determined by $VER search method
01:37:45 local file: APPDIR:SketchBlock 2.5 (11.01.2014)
01:37:45 remote file: SketchBlock 1.9 (2013-02-06)

@broadblues

Tested it more.

I deleted Sketchblock from appdir and appath.

When I run Sketchblock, it materialised back to appdir but not apppath.

@Mlehto
Appdir: entries are created by a system handler every time you run an applcation.

so that next time you may simple do

AppDir:myapp

ENV:AppPath/myapp was a AmiUpdate thing that applications had to set but are no longer required to.

It seems they then don't show in the installed list but then neither do any of the system components and they all work fine.

@broadblues

Ok, so apppath is obsolete.

And compatible applications are maybe relic.

Anyway when I copied appdir to apppath, tunenet plugin update materialised to updates and installed. It was from 7.2.2010 so there is something in supported applications anyway.

I try to get this clear to myself. It is nice and beautifull idea, that updates just happen unexpectedly but Im better safe than sorry.

@bradblues
Quote:

I don't can you tell us ?

@broadblues

Ok, got it :)

I removed some FUD from my posts.

AppPaths is NOT obsolete at all. It was originally implemented due to AmigaOS not having any way to tell what applications are actually installed on the system. In order to try and find a way around it, certain "compliant" code needed to be added to the application, which writes its installed location into AppPaths.

With the advent of 4.1 Update 1, AppDir: was implemented as a system wide feature. This allowed the location of used programs to be tracked.

As a consequence, applications targeting Update 1 and beyond no longer need the "compliance" code, but apps designed to run under lesser OS versions still require it.

So AmiUpdate uses both AppPaths and AppDir to try and determine what's installed. Do NOT go copying variables around as this may have serious consequences.

Basically, under Update 1 and beyond, forget about "Compatible Applications". It will be removed in a later version anyway.

Simon

@Rigo

Thanks for clarification.

Yep, I reversed my variablecopies after test :)

@Rigo
So is there a way for me to have new versions of applications like sketchblock, cinnamon writer, or AmigaAmp get updated automatically as they become available through AmiUpdate?
If so, that would be awesome!

Thanks

AmiUpdate is grand.
You get the impression you are part of something professional and well-oiled

Is there a way to see directly which updates i am subscribed too ? (not all Appdir are created or followed with AmiUdate. )
It would be' handy to beable to call them up from the AmiUpdate window

As to the list of Amiupdate's application base
http://amiupdate.codebench.co.uk/index.php?page=dbcontents

I guess when you download a file from there AmiUpdate takes note of that.
A lot of applications are not known to me and i would not like to start a regular update on something i downloaded but after all was not interested in enough. I could want to keep it on my HD though and get back to it (much) later.

Is there a possibility to stop downloading updates, without using rollback?

I think it would be nice that the page mentions the date next to the version of an application, and that here too you could visit that page directly from AmiUpdate menu.

@JosDuchIt

Quote:

Yes, highlight the update and select "ignore update". (that might only ignore the current update and not future updates though)

@Rigo

Made today clean install.

After launch Amiupdate try to update itself, but fails because of update.librarary.

Allso codeset.library and libsdl failed.

I made them by hand, so no problem.

It was actually same with my A1G3-SE.

@ScottCabit

Amiupdate is very nice :) All system updates and registered apps.

@ScottCabit

Yes, of course. What you need to do is contact the authors and tell them to update the database at www.amiupdate.net and these applications will automagically been seen and updated for you.

Simon

For those that get a failed start after a clean install due to update.library, can find it in the "downloads" section of www.amiupdate.net.

Simon