[MacPorts] #39602: New port: dibbler a DHCPv6 client/server/relay
MacPorts
noreply at macports.org
Fri Sep 6 21:46:43 PDT 2013
#39602: New port: dibbler a DHCPv6 client/server/relay
-------------------------+----------------------
Reporter: fclaire@… | Owner: larryv@…
Type: submission | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: fixed | Keywords:
Port: dibbler |
-------------------------+----------------------
Changes (by larryv@…):
* status: assigned => closed
* resolution: => fixed
Comment:
Committed in r110826:110828. A few things:
- I used the 1.0.0 release candidate instead of 0.8.4.
- I created the StartupItem using `startupitem.executable` instead of
`startupitem.start` and friends to take better advantage of launchd.
- I used notes instead of the [[PortfileRecipes#configfiles|configuration
file recipe]] because the example configuration files are useless as
defaults.
- The build succeeds on [https://build.macports.org/builders/buildports-
snowleopard-x86_64/builds/20464/steps/compile/logs/stdio Snow Leopard] and
[https://build.macports.org/builders/buildports-mtln-
x86_64/builds/7967/steps/compile/logs/stdio Mountain Lion] but not on
[https://build.macports.org/builders/buildports-lion-
x86_64/builds/14106/steps/compile/logs/stdio Lion]. I take it that
[[attachment:patch-Port-bsd-lowlevel-bsd.c.diff|this attachment]] was
supposed to “fix” that, but merely commenting out the check seems like a
very haphazard workaround. Do you have a Lion machine? I’d like to inspect
some of the system headers.
--
Ticket URL: <https://trac.macports.org/ticket/39602#comment:9>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list