Open GoogleCodeExporter opened 9 years ago
I don't quite understand how this relates to the current OS X installer. What
is the
difference? Can you give a few basic links for non-Mac people?
Original comment by didacty...@gmail.com
on 8 Nov 2009 at 2:06
Basically, installers are the exception rather than the norm in OS X territory,
and
even frowned upon by some people. Most applications will gather everything into
an
application bundle, which is just copied/moved into the Application folder, and
then
run. It extracts or creates other files in the filesystem as needed.
Original comment by michaels...@gmail.com
on 8 Nov 2009 at 4:37
Maybe we should have both.
- An installer that sets up synecd to start on boot as a daemon, maybe under
its own
account (sandboxing), and which you can control with the manager in
/Applications.
Maybe add a graphical way to choose what users are allowed to control the
client.
Installs screensaver system-wide. Maybe even sets up client logs to be readable
by
Console.app!
- A self-contained application that can be just dragged to /Applications. Single
app, launches manager which launches client (like now). Client never running if
user-visible app isn't running. No screensaver (or to be installed by manually
dragging into the right place too). Ability to be installed and used by
non-admin
users, putting it in ~/Applications or anywhere else.
Maybe some Windows users would like such a "portable app" too :) (although
carrying
it in a USB drive and crunching on different hardware from the same data
directory
is usually a very bad idea)
Original comment by nicolas....@gmail.com
on 8 Nov 2009 at 7:02
The Windows installer has a separate issue 65, since installers are such
platform-
specific animals.
Original comment by didacty...@gmail.com
on 8 Nov 2009 at 7:38
Original issue reported on code.google.com by
michaels...@gmail.com
on 26 Jun 2009 at 11:52