On 2017-12-25, at 6:07 PM, Ryan Schmidt wrote:
>
> This doesn't match now. The error message says it needs 10.7 or later, but
> the port allows installation on 10.6 or later. Which is it?
>
> If it builds on 10.6, does it need the 10.7 SDK to do so? If so, the port
> should enforce that. See
On Dec 25, 2017, at 16:06, Ken wrote:
> Ken (kencu) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/5d8fbbdc86dbb15c908fd4a076d06ec9004d1421
>
> The following commit(s) were added to refs/heads/master by this push:
>
>
On 2017-12-25 11:34, Jan Stary wrote:
> On Dec 24 13:56:08, ryandes...@macports.org wrote:
> Perhaps Chris is suggesting to just change the tag going forward.
I would find that more confusing.
>>>
>>> How is "10.13" confusing?
>>> How is it more confusing than "High Sierra"?
>>
>> I meant
On Dec 25 15:16:24, ryandes...@macports.org wrote:
> >>> The point of that page, if I get it, is to list problems
> >>> specific to that vesion of the OS, and it doesn't,
> >>> precisely because "sierra" matches "highsierra" (right?).
> >>> So using these silly names is precisely the problem, no?
>
On Dec 25, 2017, at 15:28, Mojca Miklavec wrote:
> I would be in favour of changing the strings from cat names to
> numbers, but of course this would only make sense if this was done
> properly, automatically for all tickets. I'm sure that there's a way
> to make such mass-edits, potentially whil
On Dec 25, 2017, at 12:38, Mojca Miklavec wrote:
> On 23 December 2017 at 16:38, Ryan Schmidt wrote:
>> Should we add a "use_autogen" (or "use_autogen_sh") option to MacPorts base?
>
> What about use_bootstrap.sh? (This is one I would need at the moment,
> but it's only used in 9 other ports rath
Hi,
Just my two cents.
I would be in favour of changing the strings from cat names to
numbers, but of course this would only make sense if this was done
properly, automatically for all tickets. I'm sure that there's a way
to make such mass-edits, potentially while disabling email
notifications fo
On Dec 25, 2017, at 04:34, Jan Stary wrote:
> On Dec 24 13:56:08, Ryan Schmidt wrote:
> Perhaps Chris is suggesting to just change the tag going forward.
I would find that more confusing.
>>>
>>> How is "10.13" confusing?
>>> How is it more confusing than "High Sierra"?
>>
>> I meant t
On Dec 25, 2017, at 13:38, Jeremy Lavergne wrote:
> I have a weird situation where default_variants appear to be ignored.
>
> Hoping for some insight on what I can change without getting into broken
> builds from +x11 poisoning, or some more clarity on the +quartz/+x11
> debacle.
>
>
>
> http
I have a weird situation where default_variants appear to be ignored.
Hoping for some insight on what I can change without getting into broken
builds from +x11 poisoning, or some more clarity on the +quartz/+x11
debacle.
https://trac.macports.org/ticket/55563
PSPP uses the standard "if no va
On Dec 25 10:04:33, vi...@macports.org wrote:
> > On 24 Dec 2017, at 11:23, Jan Stary wrote:
> >> On Dec 24 05:19:35, j...@macports.org wrote:
> >>> On 2017-12-24 04:28 , Clemens Lang wrote:
> >>> Is there a reason to not just always use a newer version?
> >> And to turn the question around, what
On 23 December 2017 at 16:38, Ryan Schmidt wrote:
> Should we add a "use_autogen" (or "use_autogen_sh") option to MacPorts base?
What about use_bootstrap.sh? (This is one I would need at the moment,
but it's only used in 9 other ports rather than 200.)
I support the idea except that the list coul
Hi,
On Mon, Dec 25, 2017 at 08:32:00AM +, Chris Jones wrote:
> > Ports are free to override configure.optflags if desired.
>
> That’s not the same as simply letting the underlying package decide,
> via its configure script or similar. That’s the point at which
> upstream gets to say what they
On Dec 24 13:56:08, ryandes...@macports.org wrote:
> >>> Perhaps Chris is suggesting to just change the tag going forward.
> >> I would find that more confusing.
> >
> > How is "10.13" confusing?
> > How is it more confusing than "High Sierra"?
>
> I meant that I would find it more confusing to u
Folks,
happy Xmas to all!
> On 24 Dec 2017, at 11:23, Jan Stary wrote:
>
>> On Dec 24 05:19:35, j...@macports.org wrote:
>>> On 2017-12-24 04:28 , Clemens Lang wrote:
>>> Is there a reason to not just always use a newer version?
>> And to turn the question around, what is gained by using the ne
> On 24 Dec 2017, at 7:57 pm, Ryan Schmidt wrote:
>
>
>> On Dec 24, 2017, at 04:36, Chris Jones wrote:
>>
>> In general its not possible to say one setting will always perform better
>> than another, its very use case dependant. For instance if you really want
>> maximum numerical performa
On 24 December 2017 at 21:02, Ryan Schmidt wrote:
> On Dec 22, 2017, at 18:10, Benjamin Redelings wrote:
>
>> However, even after that fix I have to define BOOST_ROOT=/opt/local to find
>> boost. For manual builds, if don't do PATH=/opt/local:$PATH then meson uses
>> pkgconfig from homebrew and
17 matches
Mail list logo
