Re: perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)
Thanks! It's better now. On Sat, Nov 4, 2023 at 4:53 PM Ken Cunningham wrote: > > > > On Nov 4, 2023, at 4:51 PM, Ken Cunningham > wrote: > > So to clean that up: > > sudo port -f uninstall perl5 perl5.36 > > and then: > > sudo port -f install perl5 > > > That last line should have been: > > sudo port -v install perl5 > > K
Re: perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)
> On Nov 4, 2023, at 4:51 PM, Ken Cunningham > wrote: > > So to clean that up: > > sudo port -f uninstall perl5 perl5.36 > > and then: > > sudo port -f install perl5 That last line should have been: sudo port -v install perl5 K
Re: perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)
MacPorts current "default" perl is perl5.34. I tooks like you have manually installed perl5.36 and there is no need for perl 5.36, so you could uninstall that if you care to. Everything else is pegged to perl 5.34 currently, except your "perl5" port which must have manually been installed with the +perl5.36 variant to get that variant installed. So to clean that up: sudo port -f uninstall perl5 perl5.36 and then: sudo port -f install perl5 and that should pick up the defaults, which you want, so you don't have to build everything all the time.. Once a year MacPorts updates it's default perl and python versions, in January if I recall the routine. There is (AFAIK) no current method to say "just use the current latest perl all the time"... you get pegged to the one that is designated the current default when you install perl or a perl port, and thereafter you are stuck on that perl version forevermore for those ports... So if you want to be really neat and tidy, you would keep a list (port echo requested) of what you actually wanted installed, and approximately every February or March, after the dust has settled, do a: sudo port -f uninstall installed and then a sudo port reclaim and then reinstall the things on your "requested list" -- manually, I would suggest, so you can look them over -- one by one. If you see any gcc or llvm ports on your "requested" list probably best not to reinstall those, as the new defaults will call in the current needed versions. Ken
perl5 variants (was: #68635: meld port depends on a nonexistent p5.36-xml-parser port)
Hi Ryan; I am indeed confused about these Perl variants. port installed | grep perl5 ack @3.7.0_0+perl5_34 (active) docbook2X @0.8.8_11+perl5_34 (active) git @2.42.1_0+credential_osxkeychain+diff_highlight+doc+pcre+perl5_34 (active) icoutils @0.32.3_1+perl5_34 (active) net-snmp @5.9.4_0+perl5_34+ssl (active) ossp-uuid @1.6.2_13+perl5_34 (active) perl5 @5.34.1_0+perl5_36 (active) perl5.34 @5.34.1_0 (active) perl5.36 @5.36.0_0 perl5.36 @5.36.1_0 (active) xmltoman @0.4_1+perl5_34 (active) Is there a way to simplify this? Looks all tangled up... Thanks, Ken Wolcott
Re: FYI: The meld port depends on the p5.36-xml-parser port, which does not exist
HI Joshua; Thank you for your reply. I created "#68635: meld port depends on a nonexistent p5.36-xml-parser port". I hope this helps. Ken Wolcott On Sat, Nov 4, 2023 at 11:12 AM Joshua Root wrote: > > > FYI: The meld port depends on the p5.36-xml-parser port, which does not > > exist > > > > sudo port -v -s install meld > > ---> Computing dependencies for meld > > Error: Dependency 'p5.36-xml-parser' not found. > > Error: Followhttps://guide.macports.org/#project.tickets if you > > believe there is a bug. > > Error: Processing of port meld failed > > Meld itself does not have this dependency: > > % port deps meld > Full Name: meld @3.21.0_2+x11 > Extract Dependencies: xz > Build Dependencies: intltool, itstool, libxml2, py311-distro, makeicns, >librsvg > Library Dependencies: desktop-file-utils, glib2, gtk3, gtksourceview4, >py311-cairo, py311-gobject3, shared-mime-info, > python311 > Runtime Dependencies: adwaita-icon-theme, gsettings-desktop-schemas, yelp > > So it must be one of its dependencies. But on my machine there is no > such dependency: > > % port rdeps meld | grep -F p5.36-xml-parser > % > > So it must be something that is changing dynamically, perhaps based on > variants. > > % port echo depends:xml-parser and rdepof:meld > intltool > pulseaudio > > Looking at the portfiles for these two, intltool sets a fixed > perl5.major, but pulseaudio does not. The perl5 portgroup has something > of a misfeature where it sets the default perl to use based on the > currently active variant of the perl5 port. So I guess you have > perl5+perl5_36 installed. > > Please file a ticket. The pulseaudio port may not even need the > p5-xml-parser dependency (many ports that use intltool once added this > as a poor workaround for an old bug). But if it does, or if it records > the path to perl at build time and then uses it at runtime, it needs to > set a fixed perl5.major. > > - Josh >
Re: FYI: The meld port depends on the p5.36-xml-parser port, which does not exist
FYI: The meld port depends on the p5.36-xml-parser port, which does not exist sudo port -v -s install meld ---> Computing dependencies for meld Error: Dependency 'p5.36-xml-parser' not found. Error: Followhttps://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port meld failed Meld itself does not have this dependency: % port deps meld Full Name: meld @3.21.0_2+x11 Extract Dependencies: xz Build Dependencies: intltool, itstool, libxml2, py311-distro, makeicns, librsvg Library Dependencies: desktop-file-utils, glib2, gtk3, gtksourceview4, py311-cairo, py311-gobject3, shared-mime-info, python311 Runtime Dependencies: adwaita-icon-theme, gsettings-desktop-schemas, yelp So it must be one of its dependencies. But on my machine there is no such dependency: % port rdeps meld | grep -F p5.36-xml-parser % So it must be something that is changing dynamically, perhaps based on variants. % port echo depends:xml-parser and rdepof:meld intltool pulseaudio Looking at the portfiles for these two, intltool sets a fixed perl5.major, but pulseaudio does not. The perl5 portgroup has something of a misfeature where it sets the default perl to use based on the currently active variant of the perl5 port. So I guess you have perl5+perl5_36 installed. Please file a ticket. The pulseaudio port may not even need the p5-xml-parser dependency (many ports that use intltool once added this as a poor workaround for an old bug). But if it does, or if it records the path to perl at build time and then uses it at runtime, it needs to set a fixed perl5.major. - Josh
Re: Help with legacysupport PortGroup for building GIMP for older MacOS's
Building and using legacysupport on a newer system to target an older system is tricky to design and implement properly. I think it is possible to do it, but issues will probably arise that only show up at deployment time. If I wanted to deploy gimp to 10.13, I would set up a 10.13 VM in Parallels on an Intel system, and build the final package there. That would be fully supported by macports, and require nothing special to work properly. I’m not sure if you would need a special prefix for your package, but if not, if you build a self-contained application bundle, then you could even use premade binaries. Ken
