Achieve easy inclusion & auto-update capability

[vadi2]

This is a pretty subjective title but mpkg should the scripter wants - getting autoupdates to work with minimal fuss. Thus, how about something like this workflow

• user adds mpkg .xml into their .mpackage
• user goes to mpkg central repo on github and hopefully, easily, is able to add their package and file or file location to the configuration

At this point they should be able to deploy, make a change to their code, submit a pr to update the version number on github and... all users should magically receive some sort of a pop-up notifying them an upgrade is available, do you want to install it, yadda yadda.

Having a github login and making PRs, even just through the web interface and without a git client, does seem quite technical to me still - ideally we should have a stand-alone website where people can use delegated credentials to log in, see all their packages, upload a new one and etc. Advanced users should be able to deploy straight from Travis via REST, but that's ideas for the future.

Some things needed for this to work:

• in this reality people could have many mpkg .xml's installed as part of other packages, so the script needs to be adapted for this
• script needs to set itself up to check for updates in a regular basis (for an idea of defaults that seem to work, check svof autoupdater
• script needs to pop-up a dialog when package(s) are ready to be installed (allow people to de-select packages in case one has an update that is certainly buggy) (feel free to re-use svof's dialog for this, that workflow seemed to work...)
• allow people to update packages. Packages should be able to mark whenever they require a Mudlet restart or not (some might have simple state that doesn't require a restart, some might have an advanced state that does require a restart to initialise properly)

[vadi2]

Oh and a dialog over a line in the game is important because people could be in the middle of spam and miss the line easily, while a dialog like svof's hangs around, let's the user cancel an update for now if they don't want to and etc.

[vadi2]

Think I would like to see something easier than the github login + PRs for adding a package, maybe something like copy/pasting a few files into Dropbox and having everything "just work" from there. This might or might not be necessary depending on how the users go with this.

[vadi2]

Yeah, I don't think can have the central repo be the main source of truth for a while, because that would mean any package updates would have to come through the central repository... and we can't give people direct write rights to the packages listing, they could stuff it up.

Until we have a web UI with the right permissions and all for this, I think the central repo should just contain information on all the known repositories people have and delegate everything to them. There, people could create an update without neeing anyone's permission, the only bottleneck would be getting the repo approved once by a human, and they wouldn't be able to stuff anyone else up.