Re: luau and 0export

On Thu, Jan 15, 2009 at 11:11 PM, Justin Karneges <[email protected]> wrote:
> On Thursday 15 January 2009 13:48:33 Chris Giles wrote:
>>
>> Yes, please keep Luau in place.  I released Quamachi v0.4.0 yesterday,
>> which uses it to download and install the Hamachi dependency.
>
> Sorry for barging into the middle of a conversation, but isn't Luau a central
> repository?  This should not be needed, and you should be able to host
> Hamachi on your own website for auto-download, right?

No, luau is not centralized. At least not in the sense of
distributions as we know them. Luau is a simple mechanism to allow
what you just suggested.

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 and
http://plan99.net/~curtis/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)

-Isak

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]