> On Oct 17, 2014, at 12:04 PM, ctrelea...@macports.org wrote:
>
> Revision
> 126918
> Author
> ctrelea...@macports.org
> Date
> 2014-10-17 10:04:38 -0700 (Fri, 17 Oct 2014)
> Log Message
>
> MacPorts_daemondo: New port to allow including daemondo in mpkg's
> Added Paths
>
> • trunk/dports/sysutils/macports_daemondo/
> • trunk/dports/sysutils/macports_daemondo/Portfile
> Diff
>
> Added: trunk/dports/sysutils/macports_daemondo/Portfile (0 => 126918)
>
> --- trunk/dports/sysutils/macports_daemondo/Portfile
> (rev 0)
> +++ trunk/dports/sysutils/macports_daemondo/Portfile 2014-10-17 17:04:38 UTC
> (rev 126918)
>
> @@ -0,0 +1,35 @@
>
> +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil;
> c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
> +
> +PortSystem 1.0
> +
> +name MacPorts_daemondo
> +version 1.1
> +revision 20141017
> +categories sysutils
> +platforms darwin
> +supported_archs x86_64
> +license BSD
> +maintainers cogeco.ca:ctreleaven openmaintainer
> +
> +description HACK to get daemondo into mpkg
> +long_description Nasty ${description}. \
> + When using MacPorts to create an mpkg, any daemons
> requiring daemondo \
> + would fail. Adding this port as dependency permits them
> to work.
> +
> +homepage
> http://www.macports.org/
>
> +master_sites
> +
> +universal_variant no
> +
> +fetch {}
> +checksum {}
> +extract {}
> +use_configure no
> +build {}
> +
> +destroot {
> + file copy ${prefix}/bin/daemondo ${destroot}${prefix}/bin/
> +}
> +
> +# We'll force the install and overwrite daemondo...with itself!
> +# But now we can add this as a dependency to the mpkg
Uhhhhh I agree, this is very nasty.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
