Re: luau and 0export

>
> Luau repository files are to be hosted by the same team that hosts the
> packages. As I understand Luau, there are two major use cases for
> this:
> a) the software itself can use luau to update itself whenever a new
> version is available. Very similar to how many programs in the windows
> world does this (although not necessarily as annoyingly)
> b) autopackage can hook into this functionality to provide a 'package
> update foo' command to automatically update an installed package. The
> package (optionally) contains the information already. autopackage
> could also use this to implement 'package get foo' for programs that
> aren't even installed or downloaded - this would require
> centralization though, since the package command need to have a
> central server (autopackage.org) to fetch a list of luau repositories
> from. (the packages would still be hosted, updated and maintained
> upstream though! the centralization is basically just a flat db with
> rootname<-->luau repository mappings)
>
> Curtis actually did some work on b) earlier (see
> http://plan99.net/~curtis/blog/?p=2<http://plan99.net/%7Ecurtis/blog/?p=2>and
> http://plan99.net/~curtis/blog/?p=3<http://plan99.net/%7Ecurtis/blog/?p=3>)
> but I don't know how far he went.
>
> At least this is my understanding of luau (David, if you're still on
> the list, feel free to comment)


These features would be quite useful and perhaps they should be moved up the
list.  It'll also be worth taking a closer look at how Zero Install handles
the upgrading process.