RE: Installing and locating scripts

[Thijs Schreijer <thijs@...>]

> -----Original Message-----
> From: lua-l-bounces@lists.lua.org [mailto:lua-l-bounces@lists.lua.org] On
> Behalf Of Javier Guerra Giraldez
> Sent: dinsdag 5 maart 2013 0:01
> To: Lua mailing list
> Subject: Re: Installing and locating scripts
> 
> On Mon, Mar 4, 2013 at 4:56 PM, Steve Litt <slitt@troubleshooters.com>
> wrote:
> > Having computed in the DOS era, I'm a big fan of the "everything in
> > one tree" paradigm. An install is just an tar xzvf, and an uninstall
> > is just rm -rf. Your app needs to know about few other facilities, and
> > other facilities needn't know anything about your app.
> 
> 
> this is how MacOS X apps are supposed to work: the "Photoshop" icon is
> just a directory called "Photoshop.app" with a "is_bundle" flag that tells
> the Finder to show as a single icon.
> 
> internally, there are subdirectories for application code (for several
> CPUs), resources (icons, images, blobs, XML lists,etc) and any needed
> library.  could be quite a load, but nobody blinks at a multi-hundred-
> megabytes application anymore.
> 
> installation is supposed to be just: "drag this to your Applications
> folder"
> 

Though I like the convenience of this approach for my own apps, it must be noted that the big drawback here is security. Having shared libraries on a system makes it easy to upgrade them and have multiple applications share the latest fixed/patched version. Imagine a windows system where the user would have to install security .NET patches individually for each application installed. 
But in this case probably a non-issue.
Thijs