Re: Package Installation: Non-Standard X11 Path
Re: Package Installation: Non-Standard X11 Path
- Subject: Re: Package Installation: Non-Standard X11 Path
- From: "Nathaniel Gray" <email@hidden>
- Date: Thu, 6 Dec 2007 01:02:37 -0800
On Dec 5, 2007 10:54 PM, Ben Byer <email@hidden> wrote:
>
> On Dec 4, 2007, at 2:48 PM, Nathaniel Gray wrote:
>
> > You should *never* hardwire the path to an app bundle! You can always
> > find the path at runtime using CFBundle or NSBundle functions.
> > There's no way (I think) to get the installer to do the right thing,
> > but that doesn't mean it's OK to let the app do the wrong thing.
>
>
> Noted, but in this case the problem is that we have to write the exact
> path to the app bundle into the launchd plist. I guess a better way
> would be to have the postinstall script edit (or create) that plist
> once it knew the path.
Oh man. So launchd can't launch an app by bundle id? <sigh> I guess
I'm expecting too much.
In that case, I would recommend installing X11.app in /usr/X11/ and
putting a symlink in /Applications/Utilities. There shouldn't be
unexpected consequences to moving the app bundles in the /Applications
tree.
Cheers,
-n8
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden