Update Tab

This is a start of a patch. It adds some pages, links and statuses. It doesn't do the updates yet. This will need to be added before it all works.

Here is a reroll again the new head.

Did not have the time to test much of what was done in #2.

@randallknutson How would I actually go about testing the majority of this? Also hoping you could take a look and verify things work as you last knew them to be.

I never got things fully working in this patch. It is just as far as I got it which was providing a lot of the UI but the actual updating of the modules was never finished. I haven't had time to go back and finish it yet.

fixing a typo

An app is still enabled even if it's upgradable, which this changes -- don't think app status should be used for that

I have no idea why I clicked fixed for that

Current patch was mostly commited with the ability to go to an update tab and download the app's newest module (and any new uninstalled depdencies).

What remains to be done is well, how do we decide whether to update a dependency/libraries download? Some of them will have version strings, but don't have that verison on the manifest, etc.

Current patch was mostly commited with the ability to go to an update tab and download the app's newest module (and any new uninstalled depdencies).

What remains to be done is well, how do we decide whether to update a dependency/libraries download? Some of them will have version strings, but don't have that verison on the manifest, etc.

So now have a tiny bit more time to think of it

So, each app downloads a library/module if it's not installed already based on app manifesto. Some of those do have version checking as they'll need certian versions of a module/library (e.g. opic has two apps with conflicting password policy). Some of the modules will have their version string, unless they aren't from d.o's packaging script (github, random tarbal) or a library.

So, I suggest

1) Add a database table with fields 'type', 'name', 'version', 'source_app' where type is 'module', 'library', 'app', 'name' is the library/module/app name, version is the ...version..., and source app is the app that this item was added with. On install the table will be updated. Version will 2) check app manifesto entry, e.g. depedencies[password_policy (2.x)]="password_polic 2.0-alpha1" version will be 2.0-alpha1, 2) check the version in .info file 3) default to version of app

2) remove any modules from ^ from updates (drush up, etc.) if possible. or add warnings. cause no idea how to handle if they get updated otherwise.

Mike: my guess is that due to module load order, likely can have apps be overridden in the sites directory that are in the profile directory by default.

Anyone have better ideas?

That could work for modules (considered it first), but what about libraries?

Well, some basic library/app updating is in. needs testing.