Prev: I'll add more RAM to my MacBook
Next: It needs to never be forgotten about Intego that... [Re: OSX/OpinionSpy]
From: Doug Anderson on 5 Jun 2010 15:46
Priam <priam(a)notsosure.com> writes:

> On 06/04/2010 07:01 PM, Tom Harrington wrote:
>
> > The situation is also described as PEBKAC, "problem exists between
> > keyboard and chair".
>
> That's definitely a problem, but I wonder how come OS X permits a
> program to call another one for installation. I don't believe Linux
> would permit this.

I don't know what you mean by "permit."

All kinds of linux installers call other programs.

For example, the standard installer for tex is a perl script (so it
starts by calling perl, which can do just about anything).

It removes files, it calls some version of ftp, it makes some
symlinks, etc.

Have you never used the debian linux package manager? It does all kinds of
things, depending on what the instructions are in the package. This
includes some sort of scary things - you install a piece of software,
debian may try to update some libraries that this software uses (which
are also typically used by other software).

From: Steven Fisher on 6 Jun 2010 19:20
In article <huh9l5$bg1$2(a)news.eternal-september.org>,
Mark Swellman <swellman(a)dopple_remove_syncracy.com> wrote:

> How come OS X permits a program to call another one for installation?

Why wouldn't it? A basic application that can launch a privileged
installer (requiring a password) is a great model for software
distribution. Look at Transmit, for instance.


Steve
First  |  Prev  | 
Pages: 1 2 3 4
Prev: I'll add more RAM to my MacBook
Next: It needs to never be forgotten about Intego that... [Re: OSX/OpinionSpy]