[MacPorts] #41540: fetch-crl @3.0.12: new submission
MacPorts
noreply at macports.org
Tue Nov 26 10:01:20 PST 2013
#41540: fetch-crl @3.0.12: new submission
------------------------------+--------------------------------
Reporter: Peter.Danecek@… | Owner: macports-tickets@…
Type: submission | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: fetch-crl |
------------------------------+--------------------------------
Comment (by Peter.Danecek@…):
Replying to [comment:6 ryandesign@…]:
> The `distfiles` line should be deleted since the default will work fine.
The plist shouldn't be listed there because it's going to be in the files
directory, not downloaded from a server at fetch time.
Right, this was a left-over. Already deleted.
> The relevant section of the guide for launchd questions is the
[http://guide.macports.org/chunked/reference.startupitems.html startupitem
section], but MacPorts doesn't give you a lot of control over what goes
into the plist; I see you're using `StartInterval` here which I don't
think MacPorts knows about. In that case, you can install the plist
manually like you're doing. Surprisingly, MacPorts doesn't check whether
`startupitem.create` is `yes` when using the `sudo port load` and `sudo
port unload` commands, so that works to your advantage in this case. Just
make sure a symlink to the plist exists in
/Library/LaunchDaemons/org.macports.${startupitem.name}.plist like you're
doing.
I renamed the plist file comply with the Macports naming scheme, but I
realise it is not always followed by other ports.
{{{
lrwxr-xr-x 1 root couchdb 57 Sep 4 18:01 org.apache.couchdb.plist
-> /opt/local/Library/LaunchDaemons/org.apache.couchdb.plist
lrwxr-xr-x 1 root admin 63 Nov 23 21:45 org.freedesktop.avahi-
daemon.plist -> /opt/local/etc/LaunchDaemons/org.freedesktop.avahi-
daemon.plist
lrwxr-xr-x 1 root admin 65 Nov 23 21:45 org.freedesktop.avahi-
dnsconfd.plist -> /opt/local/etc/LaunchDaemons/org.freedesktop.avahi-
dnsconfd.plist
lrwxr-xr-x 1 root admin 66 Jul 4 16:58 org.freedesktop.dbus-
system.plist -> /opt/local/Library/LaunchDaemons/org.freedesktop.dbus-
system.plist
lrwxr-xr-x 1 root admin 82 Aug 14 22:11
org.macports.VirtualBox.plist ->
/opt/local/etc/LaunchDaemons/org.macports.VirtualBox/org.macports.VirtualBox.plist
lrwxr-xr-x 1 root admin 76 Nov 12 17:06 org.macports.antinat.plist
->
/opt/local/etc/LaunchDaemons/org.macports.antinat/org.macports.antinat.plist
lrwxr-xr-x 1 root admin 76 Nov 20 19:12 org.macports.apache2.plist
->
/opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist
lrwxr-xr-x 1 root admin 80 Mar 23 2013
org.macports.cassandra.plist ->
/opt/local/etc/LaunchDaemons/org.macports.cassandra/org.macports.cassandra.plist
lrwxr-xr-x 1 root admin 76 Nov 7 13:06 org.macports.mongodb.plist
->
/opt/local/etc/LaunchDaemons/org.macports.mongodb/org.macports.mongodb.plist
-rw-r--r-- 1 root admin 645 Sep 19 18:35
org.macports.privileged_startx.plist
lrwxr-xr-x 1 root admin 74 Nov 18 2012 org.macports.rsyncd.plist
->
/opt/local/etc/LaunchDaemons/org.macports.rsyncd/org.macports.rsyncd.plist
}}}
So what is the background here, and why
`org.macports.privileged_startx.plist` installed directly? Another doubt
is about these subdirectories in
`/opt/local/etc/LaunchDaemons`:
{{{
petr% ls -la
total 8
drwxr-xr-x 10 root admin 340 Nov 26 15:36 .
drwxr-xr-x 51 root admin 1734 Nov 26 15:36 ..
-rwxr-xr-x 1 root admin 453 Nov 23 21:45 org.freedesktop.avahi-
daemon.plist
-rwxr-xr-x 1 root admin 457 Nov 23 21:45 org.freedesktop.avahi-
dnsconfd.plist
drwxr-xr-x 4 root wheel 136 Aug 14 22:11 org.macports.VirtualBox
drwxr-xr-x 3 root wheel 102 Nov 12 17:06 org.macports.antinat
drwxr-xr-x 4 root wheel 136 Nov 22 22:32 org.macports.apache2
drwxr-xr-x 3 root wheel 102 Nov 7 12:13 org.macports.cassandra
drwxr-xr-x 3 root wheel 102 Nov 7 13:07 org.macports.mongodb
drwxr-xr-x 4 root wheel 136 Oct 23 17:31 org.macports.rsyncd
}}}
I would have installed directly in `/opt/local/etc/LaunchDaemons`. Is
there anything wrong about this?
The guide does not mention `sudo port load ` and `sudo port unload`, but
from `port(1)` I would understand that it translates to the corresponding
`launchctl` commands. But the line
{{{
system "launchctl remove org.eugridpma.fetch-crl || true"
}}}
has no correspondence. Is it save to just leave this line away? Is there
some more magic involved with `port load / unload`?
Might it be possible and/or reasonable to use `startupitem.create yes`
instead and add the `StartInterval` in a later stage? Is there some hook,
e.g. something like `startupitem-append` to do this? Or at which stage
this could be done?
Thanks!
--
Ticket URL: <https://trac.macports.org/ticket/41540#comment:7>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list