Why is it that one of those variants is required?
Is there any problem with having glib2 without both?
Jan
https://en.wikipedia.org/wiki/Port_of_Oakland#/media/File:USA-Oakland-Port-View_from_Alameda-4.jpg
On 21/02/18 21:56, Dave Horsfall wrote:
On Wed, 21 Feb 2018, Arno Hautala wrote:
https://www.tripadvisor.com/LocationPhotoDirectLink-g32810-i36315229-Oakland_California.html
I nominate "Porti
On 2018-02-22 11:33, Jan Stary wrote:
> Why is it that one of those variants is required?
> Is there any problem with having glib2 without both?
The glib2 port uses a MacPorts-specific patch [1] to either use .desktop
files (+x11) or macOS app bundles (+quartz) for the GAppInfo API. This
has to be
On 2018-02-21 20:14, Jan Stary wrote:
> If I am reading https://guide.macports.org/chunked/reference.phases.html
> right, there is are no "fetch dependencies". Would it make sense
> to introduce fetch dependencies just like we have build dependencies
> and run dependencies, so that the affected por
One of the libraries in MP providing SSL functionality is WolfSSL.
Only two other ports mention it:
sysutils/gearmand explicitly disables it
net/curl has a +wolfssl variant (beside +ssl, +darwinssl, etc).
Is anyone using it? Would there be any objections to removing it?
While here, curl also kno
On Feb 22 17:09:22, rai...@macports.org wrote:
> On 2018-02-21 20:14, Jan Stary wrote:
> > If I am reading https://guide.macports.org/chunked/reference.phases.html
> > right, there is are no "fetch dependencies". Would it make sense
> > to introduce fetch dependencies just like we have build depend
On Feb 22 19:04:41, h...@stare.cz wrote:
> > depends_fetch exists, but apparently is not documented in the guide.
>
> Thanks for the insight. Currently, nothing is using it,
> except: these explicitly clear it (why?)
Is there a default nonempty value for depends_fetch
that makes these ports want
On Feb 22 18:54:18, h...@stare.cz wrote:
> One of the libraries in MP providing SSL functionality is WolfSSL.
> Only two other ports mention it:
>
> sysutils/gearmand explicitly disables it
> net/curl has a +wolfssl variant (beside +ssl, +darwinssl, etc).
>
> Is anyone using it? Would there be an
I second.
A single port crane, done as a line drawing in the O'Reilly book cover
style (possibly anthropomorphized) would work well as a logo and could
probably be made into a plush toy if someone really wanted to take it that
far.
Wouldn't work very well as a halloween/cosplay constume though.
On Feb 21, 2018, at 13:14, Jan Stary wrote:
>
> Would it make sense
> to introduce fetch dependencies just like we have build dependencies
> and run dependencies, so that the affected ports could specify e.g. curl,
> and MP vuld use _that_ for those ports?
As was mentioned, depends_fetch exists.
On Feb 22 12:31:24, billc_li...@greenbuilder.com wrote:
> A single port crane, done as a line drawing in the O'Reilly book cover
> style (possibly anthropomorphized) would work well as a logo and could
> probably be made into a plush toy if someone really wanted to take it that
> far.
A plush toy
On Feb 22 18:54:18, Jan Stary wrote:
> One of the libraries in MP providing SSL functionality is WolfSSL.
> Only two other ports mention it:
>
> sysutils/gearmand explicitly disables it
> net/curl has a +wolfssl variant (beside +ssl, +darwinssl, etc).
>
> Is anyone using it? Would there be any o
The fix:
https://trac.macports.org/ticket/55878
On 2018-02-21, at 11:14 AM, Jan Stary wrote:
>> You are done. No more circular dependency.
>
> Yes. One installation of MP depends on another installation.
>
That's not circular. CIrcular is when an installation of MacPorts depends on
itself, and is therefore fragile. The installation of libc
On Feb 22, 2018, at 20:04, Ken Cunningham wrote:
> or until we bundle in libcurl.
Note that bundling libcurl is insufficient to fix the issue; we would have to
bundle an ssl library too, and there was an objection that we don't want to be
in the business of needing to quickly release a new ver
15 matches
Mail list logo
