Handling updates
MisterX
b.xavier at internet.lu
Fri Apr 15 14:51:30 EDT 2005
Hi Oak,
I add the option in the preferences to check at startup for network updates.
Then it's one of three ways...
1) send the use to download
2) download for the user
3) patch for the user.
Depends if you are also delivering a stack, a compiled stack or a compiled
stack with accompagning stacks/files...
All options are possible, some require a bit more scriptign though ;)
Cheers
Xavier
> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com
> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of
> Oak Norton
> Sent: Friday, April 15, 2005 20:15
> To: 'How to use Revolution'
> Subject: Handling updates
>
> OK, another newbie question. Once you install a program on
> someone's local machine for win/linux/mac that uses mysql or
> PG, do you typically notify them of patches to the engine or
> expect end users to be smart enough to go out and get the
> patches themselves? It doesn't seem likely that most end
> users would have any clue how to do this. So if I have a
> robust application that uses one of these databases, are
> people required to patch, or since it's a local install can
> you just toss a database file out there that will respond to
> sql queries like an access database where it's essentially
> just a file? (I don't suppose there's a hack to let access
> databases run on
> Mac/Linux???)
>
> Thanks,
>
> Oak
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
More information about the use-livecode
mailing list