On 10/28/16 7:19 AM, Ryan Schmidt wrote:
>
>> On Oct 28, 2016, at 3:28 AM, dev...@macports.org wrote:
>>
>> Revision
>> 154337
>> Author
>> dev...@macports.org
>> Date
>> 2016-10-28 10:28:30 +0200 (Fri, 28 Oct 2016)
>> Log Message
>>
>> GNOME-3/stable: libhttpseverywhere, new port, leverage the power of
>> HTTPSEverywhere to any desktop-application.
>> Added Paths
>>
>> • users/devans/GNOME-3/stable/dports/www/libhttpseverywhere/
>> • users/devans/GNOME-3/stable/dports/www/libhttpseverywhere/Portfile
>> Diff
>>
>> Added: users/devans/GNOME-3/stable/dports/www/libhttpseverywhere/Portfile (0
>> => 154337)
>>
>> --- users/devans/GNOME-3/stable/dports/www/libhttpseverywhere/Portfile
>> (rev 0)
>> +++ users/devans/GNOME-3/stable/dports/www/libhttpseverywhere/Portfile
>> 2016-10-28 08:28:30 UTC (rev 154337)
>>
>> @@ -0,0 +1,51 @@
>>
>> +# -*- 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
>> +# $Id$
>> +
>> +PortSystem 1.0
>> +PortGroup github 1.0
>> +
>> +github.setup grindhold libhttpseverywhere 0.2.3
>> +license LGPL-3
>> +categories www
>> +maintainers devans openmaintainer
>> +platforms darwin
>> +
>> +description This library enables you to leverage the power \
>> + of HTTPSEverywhere to any desktop-application.
>> +
>> +long_description ${description}. HTTPSEverywhere is a browser plugin \
>> + that comes with a set of rules that you can use \
>> + to ensure that you use HTTP instead of HTTPS only \
>> + when this is absolutely not circumventable. \
>> + With libhttpseverywhere you get a C-bindable, \
>> + GLib-based library you can link/bind against \
>> + in almost all languages
>> +
>> +checksums rmd160 04d5f814feb434d799e2c43e1a6db8204d8e47f1 \
>> + sha256
>> 2f32e105e2751c0639892a57d1b652571e08c6937c4cc192cfa1f97cd7f49d0c
>> +
>> +depends_build port:pkgconfig \
>> + port:meson \
>> + port:ninja \
>> + port:valadoc
>> +
>> +depends_lib path:lib/pkgconfig/glib-2.0.pc:glib2 \
>> + port:json-glib \
>> + port:gobject-introspection \
>> + port:libarchive \
>> + port:libgee \
>> + port:libsoup \
>> + port:libxml2 \
>> + port:vala
>> +
>> +pre-configure {
>> + xinstall -d -m 755 ${worksrcpath}/build
>> +}
>> +
>> +configure.cmd cd build && meson ..
>> +
>> +build.cmd cd build && ninja
>> +build.target
>> +
>> +destroot.cmd cd build && DESTDIR=${destroot} ninja
>> +destroot.destdir
>
> Why not set configure.dir and build.dir instead of manually running `cd`?
>
Because these didn't cross my mind at the time. :-)
Thanks for the suggestion. Will put it on my to do list.
Dave
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
