Re: What's the push to require the latest Perl?

[Ryan Schmidt]

On Jan 5, 2018, at 17:49, Dave Horsfall wrote:

> On Fri, 5 Jan 2018, Ryan Schmidt wrote:
> 
>> If you have been using perl5.24 and p5.24 modules for your own projects and 
>> now want to use perl5.26, simply install the p5.26 versions of the modules 
>> you want.
> 
> Err, why should a user have to waste disk space on two versions of Perl? 
> Surely if a port needs features in 5.24 then it should be happy with 5.26?

I guess I don't have any answers that are going to make you happy. MacPorts has 
limited manpower. We've chosen a solution that we believe works. It may come at 
the expense of some disk space. This is not the first nor the last decision 
we've made that will have that consequence.


>> I have not used FreeBSD and am not familiar with the UPDATING file.
> 
> I do, and I am :-)  It's a file summarising the changes in that particular 
> update, with particular attention on traps for the unwary etc e.g. "You must 
> now do XXX" etc.

OK. Ports don't generally provide anything like that, though a port maintainer 
can choose to put such information into the "notes" field when upgrading a port 
to a new major version, and that would then be shown to the user when upgrading 
the port.

Re: TenFourFox on Intel

[Riccardo Mottola via macports-users]

Hi Ken,

Riccardo Mottola via macports-users wrote:

I actually use a different one, it is not commited (*), I attach it here.
It disables several problematic features: The goal is currently to "finish the 
build" and see if we start up the browser.
Slowly we can then debug enable things again, but with a priority.
It makes no sense to concentrate on the first issue found when there are maybe 
other important features missing.

  


Did you get my patches and build configuration I sent you off-list?

How fare do you get now? I'm still stuck at the same point before Christmas


Riccardo


The miracle didn't happen yet :)

I attach some other local patches whcich are either mere hacks or written in a 
way upsteam does not approve.

1) stuff to disable SSE2 and AVX2 in libvpx
2) patch to disable SKIA completely. It is disabled on current PPC builds, 
might be difficult to enable in the future
3) patch to work around some libstdc++ namespace issues. Perhaps there are better ways, 
it is very strange that TT maintainer does NOT have this issues, while from some bug I 
found in GCC and MacPorts they look like issues with older OS's. My guess is that a newer 
version of GCC might help. I think the GCC headers are not correctly working around the 
missing functions because "something" is not enabled. The patch comes out of 
the GCC 4.8 headers themselves, but without the ifdef's inside

Since you need to pach configure, I am sorry, but you need to remove your build 
directory and restart from scatch.


You may apply them blindly or check them one by one. For SKIA you can 
trust me, AVX2 is possibly compiler and configuration related, if you 
use gcc 4.8 as suggested, go with that one to.
The patch 3) about libstcc is very interesting, since the maintainer 
doesn't needed it. You could try without.



(**) I just found out that my Mailer GNUMail currently chokes on attachments... 
will send you them in a different way. More details on that Later


Fixed that too :)

Riccardo

Re: What's the push to require the latest Perl?

[Dave Horsfall]

On Fri, 5 Jan 2018, Ryan Schmidt wrote:

If you have been using perl5.24 and p5.24 modules for your own projects 
and now want to use perl5.26, simply install the p5.26 versions of the 
modules you want.


Err, why should a user have to waste disk space on two versions of Perl? 
Surely if a port needs features in 5.24 then it should be happy with 5.26?



I have not used FreeBSD and am not familiar with the UPDATING file.


I do, and I am :-)  It's a file summarising the changes in that particular 
update, with particular attention on traps for the unwary etc e.g. "You 
must now do XXX" etc.


--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."

Re: no more Quartz in new MacOS 10.13.2?

[pagani laurent via macports-users]

I think I have the same problem and I limited myself to python3.5.4
I did not find any clues about the problem either.

LP

> Le 5 janv. 2018 à 13:35, Ryan Schmidt  a écrit :
> 
> 
> On Jan 5, 2018, at 06:11, Clayson wrote:
> 
>> Dear Ryan,
>> 
>> Have you had a chance to look at this? I’ve been told by several rresponders 
>> to my qurestion that Quartz is of course in ALL recent Mac system BUT my 
>> question was not that.
>> 
>> Instead I was asking about: when I install python using
>> 
>> sudo port install py36-tkinter +quartz 
>> 
>> the built version crashes whenever I load a py file. 
>> 
>> This may be due to some problem on my Mac, of course, rather than anything 
>> to do with MacPorts. But I needed some help on this.
>> 
>> Thanks for your help.
>> 
>> sincerely
>> 
>> James
> 
> I've looked at the crash log, but I have no further suggestions to offer. I 
> briefly searched Google but couldn't find any similar reports. Maybe 
> reporting the problem to the developers of Python would help.
> 
> Remember to Reply All so the conversation stays on the mailing list.
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: meltdown and spectre

[Vincent Habchi]

Hey folks,

for Meltdown, MacOS 10.13.2 is already patched and secure.

As for Spectre, LLVM developers have committed a workaround (it’s a bit complex 
to detail here) for 5/6 which should be back ported. Whomever is responsible 
for LLVM should be on the lookout for the new versions to appear anytime soon.

Vincent

meltdown and spectre

[db]

In case anyone hasn't heard of it yet,

https://meltdownattack.com/
https://lwn.net/Articles/742999/

Re: no more Quartz in new MacOS 10.13.2?

[Ryan Schmidt]

On Jan 5, 2018, at 06:11, Clayson wrote:

> Dear Ryan,
> 
> Have you had a chance to look at this? I’ve been told by several rresponders 
> to my qurestion that Quartz is of course in ALL recent Mac system BUT my 
> question was not that.
> 
> Instead I was asking about: when I install python using
> 
> sudo port install py36-tkinter +quartz 
> 
> the built version crashes whenever I load a py file. 
> 
> This may be due to some problem on my Mac, of course, rather than anything to 
> do with MacPorts. But I needed some help on this.
> 
> Thanks for your help.
> 
> sincerely
> 
> James

I've looked at the crash log, but I have no further suggestions to offer. I 
briefly searched Google but couldn't find any similar reports. Maybe reporting 
the problem to the developers of Python would help.

Remember to Reply All so the conversation stays on the mailing list.

Re: What's the push to require the latest Perl?

[Ryan Schmidt]

There's no problem here. Just because ports use perl5.24 or perl5.26 for their 
own purposes has no bearing on what you use for your own personal projects. 
perl5.24 and perl5.26 install to different locations, do not conflict with one 
another, and can be simultaneously installed and used. Install and use whatever 
version of perl you want. Install whatever variant of the perl5 port you want, 
which is how /opt/local/bin/perl and related symlinks get set to a particular 
perl version.

If you have been using perl5.24 and p5.24 modules for your own projects and now 
want to use perl5.26, simply install the p5.26 versions of the modules you want.

Ports that require a perl module must specify a dependency on a specific perl 
version of that module (e.g. p5.24-... or p5.26-...). Ports must not declare a 
dependency on the perl versionless "stub" port (p5-...).

I have not used FreeBSD and am not familiar with the UPDATING file.