Even easier, you just check for symlinks at /usr/bin and ~/bin and if they're not there,
ask the user if they want to "install for all terminal users / just this terminal
user" on app launch and ask for creds if needed.
+ poppy
/me is searching cmake backlog...
Brandon Van Every wrote:
On De
On Dec 23, 2007 8:51 PM, Mike Jackson <[EMAIL PROTECTED]> wrote:
> I was only hoping for the "option" to install somewhere
> else than the default of /usr/bin.
Installers on MacOS generally allow the choice of installation
location, right? If they don't, I find that totally bizarre. In any
event
Well, since I started this whole fire storm I think I will post a
reply. I was trying to make the case for a possibly "better"
installation location based on running OS X for over 7 years. Some
options are good. The current OS X installer used by CMake is fine.
Bill is correct in the fact t
DING DING DING.. we have a winner.. Happy Holidays.
--
Mike Jackson Senior Research Engineer
Innovative Management & Technology Services
On Dec 22, 2007, at 9:44 PM, Bill Hoffman wrote:
But Xcode itself uses the same installer that CMake is currently
using! How much more native can you
Brandon Van Every wrote:
In that world view, you'd add "first run invokes path configuration"
because it gives native MacOS bigots a warm squishy feeling. Then
they're singing the praises of CMake instead of bitching and moaning
about it.
The first invocation doesn't have to be through a GUI
On Dec 22, 2007 4:24 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
> I still don't see the reason for the strong resistance to using an
> installer program. Many Apple products including Xcode use one.
Clearly a cultural issue. You're running afoul of "Mac native"
culture as opposed to cross-platf
