[tlbuild] potential TeX Live issue for Mac OS X 10.8

[Mojca Miklavec]

On Tue, May 22, 2012 at 8:46 AM, Alan BRASLAU wrote:
> On Mon, 21 May 2012 15:14:00 -0700
> Richard Koch wrote:
>
>> This does not affect programs installed from a CD, or obtained by
>> transferring from another machine over wireless, or transferred
>> by a memory stick. And it certainly does not affect programs compiled
>> from scratch on the machine.
>
> Just curious, what is the difference between a program obtained by
> transferring from another machine over wireless and a program
> downloaded over the internet? Is rsync, for example, flagged as
> transferring over the internet?
>
> Those using the ConTeXt distribution will see as to what I am alluding.

Dick, please correct me if I'm wrong, but I'm lead to believe that as
little as using wget instead of the web browser to fetch a file might
be enough to circumvent the problem.

You are already faced with a warning now:
    “first-setup.sh” is a script application downloaded from the
Internet. Are you sure you want to open it?
However, even when you click cancel, nothing prevents you from using
    chmod +x first-setup.sh
    ./first-setup.sh
If you fetch that same file with rsync, Mac OS X doesn't complain at all.

I also realized one thing (in 10.7). I can have first-setup.sh that
Mac OS X refuses to open. It is sufficient to use
    rsync -av first-setup.sh second-setup.sh
and the second-setup.sh will open without problems. "mv" or "cp" on
the other hand aren't sufficient.

My next business plan: write an AppUnlocker that lets you run unsigned
applications and sell it for 1$ on AppStore ;)

I'm guessing that 10.8 will only refuse to open first-setup.sh
downloaded via a web browser - this is already a bad choice now since
all the executable bits are dropped, but I doubt that it will prevent
manual execution of the script in shell. Also fetching via rsync
should already do the trick. You also don't need signed tlmgr packages
to have a working MacTeX.

Mac OS X is made for dumb users ;), so as long as you don't require
fancy GUI, command line tools should probably be fine.

(I would really like to figure out what exactly it is that Mac
attaches to files downloaded via browsers.)

Mojca