On Jun 21, 2014, at 3:07 PM, [email protected] wrote:
> Revision
> 121265
> Author
> [email protected]
> Date
> 2014-06-21 13:07:36 -0700 (Sat, 21 Jun 2014)
> Log Message
>
> devans/dports: libvisio, rename to libvisio-0.1, installs in parallel with
> existing libvisio.
> Modified: users/devans/dports/graphics/libvisio-0.1/Portfile (120970 =>
> 121265)
> +# delete binaries that conflict with libvisio
> +
> +post-destroot {
> + file delete -force ${destroot}${prefix}/bin
> +}
There's probably no reason not to use "delete" instead of "file delete -force",
now that MacPorts 2.3.0 has been released which fixes the one bug that was in
"delete" (which wouldn't have applied in this case anyway because you're
deleting a directory and not a file).
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
