On Aug 29, 2008, at 5:03 AM, Chris Forsythe wrote:
> Why is it that this is a problem? Maybe I'm not understanding, but
> we're just opening sys prefs, why does that cause problems for your
> application?
You have a problem in two areas here:
1) It is perfectly valid to be installing onto a volume that is not
the one you are booted from at the moment. You could be installing to
a recovery firewire drive, or as is in the case of InstaDMG be
installing a whole new OS onto a dmg to make a new system image. In
either case your assumption that it is advisable to then open System
Preference (on the booted HD) is wrong in either of those cases, and
can not do any good, but can do harm. In either case it is certainly
not going to get users what they want.
The change that I provided for your installer would address this
problem.
2) It is also possible that the person sitting at the console is not
the one doing the install, in fact it is possible that no one would be
sitting at the console at all. This is the case when the computers are
being managed using Apple Remote Desktop. In that scenario the pkg is
downloaded to the target computer from a 'task server' and then run
using the command-line tool 'installer'. No GUI is shown during the
process (unless the installer writer has messed up like in the case we
are talking about) and everything is run in the context of root's login.
This last bit is what really causes problems: If there is no user
logged in then GUI processes will be launched as root... over the
login window. And since root is an "admin" anyone walking by now has
the ability to change almost any system setting the are in System
Preferences. Obviously this is a big problem. 10.5 mitigates this by
not allowing most windows to appear in the loginwindow context, but
10.4 will happily allow you to shoot yourself in the foot like this.
> Why does your application not take into account situations like
> this? i.e. this is the only time I've heard of this problem, why is
> this something that we must fix and not you?
>
> Also, you need to provide this in a patch file, not inline in an
> email.
Do you have your installer in your repository? Most projects don't.
And you do realize that I am both doing your homework for you, and
that this is not really an issue for me, but for someone else who
wants to use your product on a large number of machines? Does making
me jump through hoops for 2 lines of shell code really sound like a
good response to you?
> Third, we've moved to use hg, was this a patch against the hg
> repository or the svn repository?
Neither. I downloaded the binary and looked inside the installer.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Growl Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en
-~----------~----~----~----~------~----~------~--~---
