[prev in list] [next in list] [prev in thread] [next in thread]
List: macports-dev
Subject: Re: GSoC 2018 Project: Improve startupitem code
From: Joshua Root <jmr () macports ! org>
Date: 2018-02-15 19:22:25
Message-ID: f4d2ef06-442d-7aea-0720-f101bd30daf9 () macports ! org
[Download RAW message or body]
On 2018-2-16 06:02 , Bradley Giesbrecht wrote:
> > On Feb 15, 2018, at 10:47 AM, Joshua Root <jmr@macports.org> wrote:
> >
> > On 2018-2-16 05:04 , Bradley Giesbrecht wrote:
> > > How to handle two launchd plists with "port load" command? Separate ports?
> >
> > This is <https://trac.macports.org/ticket/44295>.
>
> Is this one of the issues you are closing?
I have an approach in mind.
> > > The common locations where launchd plists need to be loaded from:
> > > ~/Library/LaunchAgents
> >
> > Installing into ~ is problematic in general. I don't think it's really
> > needed; per-user stuff can live in /Library/LaunchAgents.
>
> Of course, thanks for the point.
>
> So we might have "startupitem.directory /Library/LaunchDaemons", the default, but \
> can be set to "startupitem.directory /Library/LaunchAgents"?
It would be "startupitem.location LaunchAgents" under the current system.
- Josh
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic