Re: Why don't p5-* ports mark their dependencies?
On 2021-06-12 at 12:11:47 UTC-0400 (Sat, 12 Jun 2021 09:11:47 -0700) Kastus Shchuka is rumored to have said: I wish it could be so easy to remove perl5.28. Apparently, I have to keep it because of git: port uninstall git port install git -perl5_28 +perl5_30 -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
Re: Why don't p5-* ports mark their dependencies?
On 2021-06-12 at 12:55:24 UTC-0400 (Sat, 12 Jun 2021 09:55:24 -0700) Ken Cunningham is rumored to have said: macports recommended perl is still 5.28 Which has been unsupported upstream for just over a year. 5.30 just fell out of support a few weeks ago. They are doing a major release every year and only supporting the current and prior stable releases. "Pace" is all the rage these days, having supplanted "stability." I still have stable production on 5.28.3 because of some known issues in 5.30 and later with code hygiene, but I need to work on those issues so a 5.30 test system (and soon 5.32) is necessary for me. $ port info perl5 perl5 @5.28.3 (lang) Sub-ports:perl5.16, perl5.18, perl5.20, perl5.22, perl5.24, perl5.26, perl5.28, perl5.30, perl5.32 Variants: perl5_26, [+]perl5_28, perl5_30 Odd that perl5.32 is a sub-port but perl5_32 isn't a variant. so that is supposed to be the default perl for everything, until such time as that is changed to perl 5.30. So if you want perl 5.30 for everything, you will be fighting upstream at every turn. I see it more as opening a second front downstream of MacPorts in alliance with the Perl upstream. :) Someone could make a full-time+ job of maintaining just the Perl packages in MacPorts. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
Re: Why don't p5-* ports mark their dependencies?
I wish it could be so easy to remove perl5.28. Apparently, I have to keep it
because of git:
$ port info git
git @2.31.1_2 (devel)
Variants: [+]credential_osxkeychain, [+]diff_highlight, [+]doc,
gitweb, [+]pcre, perl5_26, [+]perl5_28,
perl5_30, python, svn, universal
Description: Git is a fast, scalable, distributed open source version
control system focusing on speed and
efficiency.
Homepage: https://git-scm.com/
Extract Dependencies: xz
Library Dependencies: perl5.28, curl, zlib, openssl, expat, libiconv, pcre2
Runtime Dependencies: p5.28-authen-sasl, p5.28-error, p5.28-net-smtp-ssl,
p5.28-term-readkey, p5.28-cgi, rsync
Platforms:darwin
License: GPL-2 and LGPL-2.1+
Maintainers: Email: ciserl...@macports.org, GitHub: ci42
Policy: openmaintainer
Are Library and Runtime dependencies of git on perl5.28 intentional or an
oversight?
Thanks,
Kastus
> On Jun 12, 2021, at 8:34 AM, Bill Cole
> wrote:
>
> On 2021-06-09 at 15:51:09 UTC-0400 (Wed, 9 Jun 2021 15:51:09 -0400)
> Daniel J. Luke
> is rumored to have said:
>
>> On Jun 6, 2021, at 1:41 PM, Bill Cole
>> wrote:
>>> I *think* I've even worked out the right way to use that construct to make
>>> Perl upgrades simpler, so I use the p5-* ports:
>>
>> I gave up on trying to use this in any useful way a while ago - if you've
>> got some way that it works, please share.
>
> According to my shell history, this is what I did to clear out all the old
> perl5.2[68] and
>
> port deactivate perl5
> port install perl5 +perl5_30
> port deactivate perl5.26
> port deactivate perl5.28
> port installed|grep '^ p5\.2.*-' |awk '{print $1}'|while read x; do y=`echo
> $x|sed 's/\.2.-/-/'`; port -v -f deactivate $x ; port -v install $y; done
>
> Adjust to suit whatever versions you're trying to remove/replace.
>
> --
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire
Re: Why don't p5-* ports mark their dependencies?
macports recommended perl is still 5.28 $ port info perl5 perl5 @5.28.3 (lang) Sub-ports:perl5.16, perl5.18, perl5.20, perl5.22, perl5.24, perl5.26, perl5.28, perl5.30, perl5.32 Variants: perl5_26, [+]perl5_28, perl5_30 so that is supposed to be the default perl for everything, until such time as that is changed to perl 5.30. So if you want perl 5.30 for everything, you will be fighting upstream at every turn. Ken
Re: Why don't p5-* ports mark their dependencies?
On 12/06/2021 18.32, Bill Cole wrote: > On 2021-06-12 at 12:11:47 UTC-0400 (Sat, 12 Jun 2021 09:11:47 -0700) > Kastus Shchuka > is rumored to have said: > >> I wish it could be so easy to remove perl5.28. Apparently, I have to >> keep it because of git: > > port uninstall git > port install git -perl5_28 +perl5_30 sudo port upgrade --enforce-variants git -perl5_28 +perl5_30 https://guide.macports.org/#using.port.upgrade Rainer
Re: Why don't p5-* ports mark their dependencies?
> On Jun 12, 2021, at 9:54 AM, Rainer Müller wrote: > > On 12/06/2021 18.32, Bill Cole wrote: >> On 2021-06-12 at 12:11:47 UTC-0400 (Sat, 12 Jun 2021 09:11:47 -0700) >> Kastus Shchuka >> is rumored to have said: >> >>> I wish it could be so easy to remove perl5.28. Apparently, I have to >>> keep it because of git: >> >> port uninstall git >> port install git -perl5_28 +perl5_30 > > sudo port upgrade --enforce-variants git -perl5_28 +perl5_30 > Thank you, that worked and allowed me to uninstall all p5.28 modules. What puzzles me still, why port info shows that git depends on perl 5.28 modules: $ port info git git @2.32.0 (devel) Variants: [+]credential_osxkeychain, [+]diff_highlight, [+]doc, gitweb, [+]pcre, perl5_26, [+]perl5_28, perl5_30, python, svn, universal Description: Git is a fast, scalable, distributed open source version control system focusing on speed and efficiency. Homepage: https://git-scm.com/ Extract Dependencies: xz Library Dependencies: perl5.28, curl, zlib, openssl, expat, libiconv, pcre2 Runtime Dependencies: p5.28-authen-sasl, p5.28-error, p5.28-net-smtp-ssl, p5.28-term-readkey, p5.28-cgi, rsync Platforms:darwin License: GPL-2 and LGPL-2.1+ Maintainers: Email: ciserl...@macports.org, GitHub: ci42 Policy: openmaintainer $ port installed and git The following ports are currently installed: git @2.31.1_2+credential_osxkeychain+diff_highlight+doc+pcre+perl5_30 git @2.32.0_0+credential_osxkeychain+diff_highlight+doc+pcre+perl5_30 (active) git works, as far as I can test. Thanks, Kastus
Re: Why don't p5-* ports mark their dependencies?
On 2021-06-09 at 15:51:09 UTC-0400 (Wed, 9 Jun 2021 15:51:09 -0400)
Daniel J. Luke
is rumored to have said:
On Jun 6, 2021, at 1:41 PM, Bill Cole
wrote:
I *think* I've even worked out the right way to use that construct to
make Perl upgrades simpler, so I use the p5-* ports:
I gave up on trying to use this in any useful way a while ago - if
you've got some way that it works, please share.
According to my shell history, this is what I did to clear out all the
old perl5.2[68] and
port deactivate perl5
port install perl5 +perl5_30
port deactivate perl5.26
port deactivate perl5.28
port installed|grep '^ p5\.2.*-' |awk '{print $1}'|while read x; do
y=`echo $x|sed 's/\.2.-/-/'`; port -v -f deactivate $x ; port -v install
$y; done
Adjust to suit whatever versions you're trying to remove/replace.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
unexpected warning from dylib
My MacOS version is fully up to date 11.4, and my Xcode is fully up to date (12.5) and I’m seeing these warnings: ld: warning: dylib (/opt/local/lib/libidn2.dylib) was built for newer macOS version (11.3) than being linked (11.0) ld: warning: dylib (/opt/local/lib/libzstd.dylib) was built for newer macOS version (11.3) than being linked (11.0) ld: warning: dylib (/opt/local/lib/libssl.dylib) was built for newer macOS version (11.2) than being linked (11.0) ld: warning: dylib (/opt/local/lib/libcrypto.dylib) was built for newer macOS version (11.2) than being linked (11.0) 2 Questions: 1 - Why? 2 - How can I make them go away? David David Barto | Principal Engineer ba...@cambridgesemantics.com
apache doc folder permissions problem
For the Macports apache2 installation, I’m using a non-default location for my web sites. The httpd.conf includes a httpd-vhosts.conf file, and the latter includes entries such as: DocumentRoot "/Users/me/Sites/MyHomePage" ServerName MyHomePage.local ServerAlias www.MyHomePage.local ErrorLog "var/log/apache2/me-MyHomePageerror_log" CustomLog "var/log/apache2/me-MyHomePage-access_log" common Options Indexes FollowSymLinks Require all granted And in my /private/etc/hosts I include the lines: 127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost fe80::1%lo0 localhost 127.0.0.1 me-html.local 127.0.0.1 MyHomePage.local When I start apache and try to open the site MyHomePage.local, i get error: Forbidden You don't have permission to access this resource. The permissions on /Users/me/Sites/MyHomePage are: drwxr-xr-x@ 92 me staff 2944 Apr 10 2015 MyHomePage and the permissions for /Users/me/Sites/MyHomePage/index.html are: -rw-r--r--@ 1 me staff 8331 Apr 10 2015 index.html What’s wrong? --- Murray Eisenbergmurrayeisenb...@gmail.com 503 King Farm Blvd #101 Rockville, MD 20850-6667Mobile (413)-427-5334
Re: Why don't p5-* ports mark their dependencies?
On Sat, Jun 12, 2021 at 06:02:25PM -0700, Ken Cunningham wrote: > I think Bill perhaps then you really want to open a thread with the title: > > “I would like to suggest we move MacPorts default perl to 5.30 now”. > > And then let the conversation happen, and if the outcome is “Yes” then that > will happen. > > Or 5.32. Whatever you care to suggest. > > But trying to fight against the current default recommended perl, whatever it > is, is kind of a waste of precious time and effort. > > Ken 5.34 has just been released, so 5.32 might be better. but they're all fine choices. cheers, raf
Re: Why don't p5-* ports mark their dependencies?
I think Bill perhaps then you really want to open a thread with the title: “I would like to suggest we move MacPorts default perl to 5.30 now”. And then let the conversation happen, and if the outcome is “Yes” then that will happen. Or 5.32. Whatever you care to suggest. But trying to fight against the current default recommended perl, whatever it is, is kind of a waste of precious time and effort. Ken
Re: apache doc folder permissions problem
How about the permissions on the Sites folder? On Jun 12, 2021, at 20:24, Murray Eisenberg wrote: For the Macports apache2 installation, I’m using a non-default location for my web sites. The httpd.conf includes a httpd-vhosts.conf file, and the latter includes entries such as: DocumentRoot "/Users/me/Sites/MyHomePage" ServerName MyHomePage.local ServerAlias www.MyHomePage.local ErrorLog "var/log/apache2/me-MyHomePageerror_log" CustomLog "var/log/apache2/me-MyHomePage-access_log" common Options Indexes FollowSymLinks Require all granted And in my /private/etc/hosts I include the lines: 127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost fe80::1%lo0 localhost 127.0.0.1 me-html.local 127.0.0.1 MyHomePage.local When I start apache and try to open the site MyHomePage.local, i get error: Forbidden You don't have permission to access this resource. The permissions on /Users/me/Sites/MyHomePage are: drwxr-xr-x@ 92 me staff 2944 Apr 10 2015 MyHomePage and the permissions for /Users/me/Sites/MyHomePage/index.html are: -rw-r--r--@ 1 me staff 8331 Apr 10 2015 index.html What’s wrong? --- Murray Eisenbergmurrayeisenb...@gmail.com 503 King Farm Blvd #101 Rockville, MD 20850-6667Mobile (413)-427-5334
Re: unexpected warning from dylib
> My MacOS version is fully up to date 11.4, and my Xcode is fully up to date > (12.5) and I’m seeing these warnings: > > ld: warning: dylib (/opt/local/lib/libidn2.dylib) was built for newer macOS > version (11.3) than being linked (11.0) > ld: warning: dylib (/opt/local/lib/libzstd.dylib) was built for newer macOS > version (11.3) than being linked (11.0) > ld: warning: dylib (/opt/local/lib/libssl.dylib) was built for newer macOS > version (11.2) than being linked (11.0) > ld: warning: dylib (/opt/local/lib/libcrypto.dylib) was built for newer macOS > version (11.2) than being linked (11.0) > > 2 Questions: > 1 - Why? > 2 - How can I make them go away? For a while the buildbot was building software with a deployment target of 11.2, and sometimes 11.3. Now the deployment target is 11.0. We think that is probably right, to cover all 11.x systems with one buildbot. Some software from the buildbot that has a newer deployment target of 11.2 or 11.3 will have to be rebuilt with a dep target of 11.0. That means rev-bumping the software to make a new build on the buildbot, or rebuilding the software yourself on your machine. In this case, you would run “port provides /path/to/troubled/lib.dylib” with your libs above, and rebuild from source what needs rebuilding by running: sudo port -v -s install my_troubled_port and if you want to be really helpful, PR some revbumps too for everyone else. Best, Ken
