Re: [php84] php84-vld

https://github.com/BjarneDMat/macports-ports/commit/8e1bcd9 OK - so what goes wrong here, is that the developer has made some un-published changes to the code-base. In particular : 1) https://github.com/derickr/vld/commit/d7abb0c PHP_CHECK_GCC_ARG is now AX_CHECK_COMPILE_FLAG 2) https://g

Re: [php84] php-mcrypt

https://www.php.net/manual/en/intro.mcrypt.php This feature was DEPRECATED in PHP 7.1.0, and REMOVED in PHP 7.2.0. https://pecl.php.net/package/mcrypt This package is not maintained https://github.com/BjarneDMat/macports-ports/commit/f89526a Author: BjarneDM Date: Wed Feb 12 19:20:10 2025 +010

Re: Netatalk 4.x

The quoting on startupitem.executable was my main issue. I’ll incorporate these other tips as well. Thanks! > On Feb 11, 2025, at 9:30 PM, Ryan Carsten Schmidt > wrote: > > On Feb 11, 2025, at 20:19, Blake wrote: >> >> startupitem.name${name} > > That's the default so you should omit

Re: [MacPorts] #72050: py39-webcolors won't upgrade

It builds with that change. Thanks, --Adam > On Feb 12, 2025, at 8:08 AM, MacPorts wrote: > > #72050: py39-webcolors won't upgrade > -+ > Reporter: dershow | Owner: (none) > Type: defect | Status: new > Prio

Re: Please do not remove Tiger support

Hi, AFAIK it might be useful to have Tiger binaries and e.g. not updating from sources all the time. That way, Tiger users might have less current versions of software but at least you might have some version of freeciv instead of nothing, as an example. Johan Sent from my iPod > On Feb 11,

Re: Netatalk 4.x

On Feb 11, 2025, at 20:19, Blake wrote: > > startupitem.name${name} That's the default so you should omit this line. > startupitem.executable "${prefix}/sbin/netatalk -d -F ${prefix}/etc/afp.conf" Per guide.macports.org: Do not wrap values in quotes if passing arguments to the daemon; “ex

Re: Netatalk 4.x

I have made some good progress on this port. However, the startup item functionality in the profile is giving me some difficulty. What I have in the ports is… startupitem.create yes startupitem.name${name} startupitem.executable "${prefix}/sbin/netatalk -d -F ${prefix}/etc/afp.conf" start

Re: Please do not remove Tiger support

On Tue, Feb 11, 2025 at 02:36:03AM +, Gleb Mazovetskiy wrote: > Our port of DevilutionX to Tiger PPC, released yesterday and powered by > macports and, has made the news: > > https://www.pcgamer.com/games/rpg/the-best-way-to-play-diablo-1-on-pretty-much-anything-just-got-an-update-for-a-20-

Re: [perl5 update to v5.40.1]

Hello Ryan et al., Thank you for your help! > On 11 Feb 2025, at 15:36, Ryan Carsten Schmidt > wrote: > > On Feb 11, 2025, at 06:59, Maxim Abalenkov wrote: >> >> Thank you for your help! But when I try to install it with >> >> sudo port install perl5.40 >> >> I face the following error: >>

Re: Please do not remove Tiger support

Sergey Fedorov wrote: There was nearly no active support for any PowerPC systems for years anyway (outside of legacy-support subproject), and most of PowerPC-related fixes were from my side (which I now stopped submitting here). I have a small core on 10.4 PPCwhich serves me well... git, svn,

Re: Please do not remove Tiger support

Hi Christopher! Christopher Nielsen wrote: deally we would have kept this discussion open for at least a few weeks, to allow time for busy individuals to chime in. That’s not meant as a criticism of anyone, but just throwing that out there. Had there been a formal vote on whether we remove s

Re: Please do not remove Tiger support

It seems like the interested people fork MacPorts just before the commits that remove 10.4 and focus on supporting that for the legacy funtime use case. Let that fork of Macports age gracefully with the hardware that supports it. Reducing the burden of keeping current macports up to date and fun

Re: [perl5 update to v5.40.1]

On Feb 11, 2025, at 06:59, Maxim Abalenkov wrote: > > Thank you for your help! But when I try to install it with > > sudo port install perl5.40 > > I face the following error: > > sudo port install perl5.40 > ---> Computing dependencies for perl5.40 > ---> Fetching distfiles for perl5.40 > --

RE: Please do not remove Tiger support

Just for a note, there is no problem in explicitly stating that no tickets for 10.4 will be accepted and just close such tickets as wontfix. (And Ken, for example, recently went as far as closing as wontfix all tickets for bugs discovered on 10.6 PowerPC even when those had not been specific to

Re: [perl5 update to v5.40.1]

Hello Ryan et al., > On 11 Feb 2025, at 11:02, Ryan Carsten Schmidt > wrote: > > On Feb 11, 2025, at 03:52, Maxim Abalenkov wrote: >> >> 6) I can verify that I now see Perl 5.40.1 with the port search command and >> port variants command: >> >> perl5.40 @5.40.1 (lang) >> Perl 5.40.1 - Prac

Re: [perl5 update to v5.40.1]

On Feb 11, 2025, at 03:52, Maxim Abalenkov wrote: > > 6) I can verify that I now see Perl 5.40.1 with the port search command and > port variants command: > > perl5.40 @5.40.1 (lang) >Perl 5.40.1 - Practical Extraction and Report Language > > perl5_40: Use MacPorts perl5.40 > * conflict

Re: [perl5 update to v5.40.1]

Dear all, How are you? I hope all is well with you. I apologise for my beginner questions. I’m still struggling to test install the updated Portfile for Perl5.40.1. 1) I created a local MacPorts tree under /opt/local/ports. 2) I created a directory structure for Perl5: /opt/local/ports/lang/pe

Re: Please do not remove Tiger support

I really don't know how I feel about this: https://github.com/mistydemeo/tigerbrew In general, I am not a fan of Homebrew. However, for Tiger users feeling left out by MacPorts' recent changes, maybe that fork will be helpful? I've already seen mention on MacRumors of forking MacPorts to retain

Re: Please do not remove Tiger support

Hello, I'm not sure if this is the right place to send this email, but as a user of Tiger MacPorts, I think it is very unfortunate that you have decided to no longer support Tiger, and I hope there may be some room to reconsider this decision for those of us who still need it. Although the l

Re: Please do not remove Tiger support

> I'm still running an update on 10.4 that has been taking days (feels like a week!). I host binary packages here if you don't feel like waiting http://macports-tiger-ppc.glebm.com/ On Tue, Feb 11, 2025 at 2:36 AM Gleb Mazovetskiy wrote: > Our port of DevilutionX to Tiger PPC, released yesterday

Re: Please do not remove Tiger support

Our port of DevilutionX to Tiger PPC, released yesterday and powered by macports and, has made the news: https://www.pcgamer.com/games/rpg/the-best-way-to-play-diablo-1-on-pretty-much-anything-just-got-an-update-for-a-20-year-old-apple-os-that-runs-on-a-dead-chipset-one-lunatic-somewhere-presumabl

Re: Please do not remove Tiger support

On Mon, Feb 10, 2025 at 11:33:53AM -0500, Christopher Nielsen wrote: > [...] > It’s also important to separate our support policy toward Tiger - > which is to now de-emphasize it - from what base supports. And that > seems to have been lost, or perhaps not really discussed as thoroughly > as we

Re: Please do not remove Tiger support

On 10/02/2025 10.36, Gleb Mazovetskiy wrote: > I've subscribed to the mailing list just to post this. This is in > response to https://lists.macports.org/pipermail/macports-dev/2025- > January/046014.html dev/2025-January/046014.html>, which I notic

Re: Please do not remove Tiger support

Hi, To be concrete, I don’t like intel, I play Neverwinter Nights on an iBook, as well as freeciv. So to be very easy, bring Darwin back in the picture instead of complaining about “we have Leopard”. Oh, and thanks you all for maintaining everything. Johan Sent from my iPod On Feb 10, 2025,

RE: Please do not remove Tiger support

> I think dropping support for Tiger in this way is quite heavy-handed. I’d > like to ask for a compromise, where Tiger stuff is maintained on a volunteer > best-effort per-issue basis rather than entirely ripped out. > > I understand that maintaining Tiger causes some overhead. Only a subset of

Re: [perl5 update to v5.40.1]

On 10/2/2025 08:42, Ryan Carsten Schmidt wrote: On Feb 9, 2025, at 15:26, Maxim Abalenkov wrote: sudo port -d install perl5 +perl5_40 This fails with ‘Dependency perl5.40 not found’. Obviously, I missed something in the Portfile. The portfiles is probably fine. You probably just need to run

Re: [perl5 update to v5.40.1]

On Feb 9, 2025, at 15:26, Maxim Abalenkov wrote: > > sudo port -d install perl5 +perl5_40 > > This fails with ‘Dependency perl5.40 not found’. Obviously, I missed > something in the Portfile. The portfiles is probably fine. You probably just need to run sudo port -d install subport=perl5.40

Re: [php84] php84-imagick rc1

https://github.com/BjarneDMat/macports-ports/commit/0c4cd8e php84-imagick rc1 fixes for 1) patching 2) default variant On branch php84 Changes to be committed: modified: php/php-imagick/Portfile > It doesn't look like you're using vercmp correctly.

Re: [php84] php84-imagick beta1

On Feb 7, 2025, at 17:50, Bjarne D Mathiesen via macports-dev wrote: > > https://github.com/BjarneDMat/macports-ports/commit/0fb4448 > >php84-imagick beta1 > >!!NOT!! working correctly >1) patching >2) default variant > >On branch php84 > >Changes to be committed: >

Re: [php84] php84-imagick beta1

https://github.com/BjarneDMat/macports-ports/commit/0fb4448 php84-imagick beta1 !!NOT!! working correctly 1) patching 2) default variant On branch php84 Changes to be committed: modified: php/php-imagick/Portfile new file: php/php-imagick/file

Re: [php84] current status for php74 - php84

@7.4.33 doesn't like libxml2 @2.13.5_2 => fails to compile logfile: https://macports.mathiesen.info/logs/php/php74/main.log @8.0.30 doesn't like libxml2 @2.13.5_2 => fails to compile logfile: https://macports.mathiesen.info/logs/php/php80/main.log @8.1.31 builds - but segfaults wh

Re: [php84] xxhash in php81, php82, php83

On Feb 7, 2025, at 10:33, Bjarne D Mathiesen wrote: > >patchfiles-append \ >patch-${php}-ext-hash-php_hash_xxhash.h.diff \ >patch-${php}-ext-hash-config.m4.diff \ >patch-${php}-ext-hash-config.w32.diff Since you're f

Re: [php84] xxhash in php81, php82, php83

So, we discovered an error in xxhash for php @8.1.31, @8.2.27, @8.3.16 I'm attempting to backport the php @8.4.3 changes to these. if {[vercmp ${branch} >= 8.1] && [vercmp ${branch} <= 8.3]} { patchfiles-append \ patch-${php}-ext-hash-php_hash_xxhash.h.diff \

Re: Recent events ...

On Feb 4, 2025, at 11:44, Ken Cunningham wrote: > > First of all, I’ve been pretty strongly attacked, as you can see. On behalf of management, we have taken action on this issue.

Re: [php84] missing extensions

Bjarne, you reported build failure for `php-imagick` in your first draft. Here are a couple fixes. Feel free to incorporate these into your branch, or else let this PR go through as is. This could use some follow-up testing which I can not provide. https://github.com/macports/macports-ports/pull

Re: [php84] missing extensions

pspell was evicted from PHP core in version 8.4; php81-pspell and later subports are now found in the separate php-pspell Portfile. On branch php84 Changes to be committed: modified: lang/php/Portfile new file: php/php-pspell/Portfile -- Bjarne D Mathiesen S

Re: Recent events ...

Hi, grey wrote: Ken, sorry to see you go. By all means, prioritizing self care is vital! I've experienced burn out with other libre/free open source endeavors in the past (I stepped away as a contributing editor to undeadly.org for over a decade when my marriage disintegrated and only returned i

Re: Recent events ...

On Wed, Feb 05, 2025 at 01:06:59AM +0100, Riccardo Mottola via macports-dev wrote: > Hi Ken, > [...] > Without you, no TenFourFox on Intel and also no ArcticFox on Macs. Ooh, that's ineresting. I just tried to install TenFourFox on intel 10.6 and it complained that it's only for ppc. I'll have

Re: Recent events ...

ecause of that interaction, but in > respect to other general life events, I have re-evaluated how I choose to > spend my time. Life is short, as we all know, and there are only so many > hours in the day. I have resigned from the MacPorts’ committer team, and > deleted all my MacP

Re: Recent events ...

I saw that the swift.org team has adopted https://www.contributor-covenant.org It could be an option. > On Feb 4, 2025, at 5:57 PM, Joshua Root wrote: > > On 5/2/2025 05:18, Nicklas Larsson via macports-dev wrote: >> I’m not aware o

Re: funding/grants

On 5/2/2025 08:01, Clemens Lang wrote: I don't believe there is a secret cabal of MacPorts devs that are getting funding behind our backs and are keeping quiet about it. Chances are nobody is getting funding, because these things take time. As a consequence, I'd encourage anybody who wants to try

Re: Recent events ...

On 5/2/2025 05:18, Nicklas Larsson via macports-dev wrote: I’m not aware of MacPorts have a Code of Conduct, a commonly used CoC in open source projects is [1]. We do ask posters to abide by netiquette as defined in RFC 1855 (a document which, while it shows its age in places, is still remarka

Re: Recent events ...

Ken, sorry to see you go. By all means, prioritizing self care is vital! I've experienced burn out with other libre/free open source endeavors in the past (I stepped away as a contributing editor to undeadly.org for over a decade when my marriage disintegrated and only returned in a volunteer capac

Re: Recent events ...

being said — and not strictly because of that interaction, but in respect to other general life events, I have re-evaluated how I choose to spend my time. Life is short, as we all know, and there are only so many hours in the day. I have resigned from the MacPorts’ committer team, and deleted

Re: [php84] php-imap

imap was evicted from PHP core in version 8.4; php83-imap and later subports are now found in the separate php-imap Portfile. Author: BjarneDM Date: Tue Feb 4 23:59:41 2025 +0100 php-imap for php83 & php84 moved to separate Portfile On branch php84 Changes to be committed:

Re: Recent events ...

e best I will ever be able to do. > > There was also one brief email exchange with him where expressed his > displeasure with me, and I pointed out he was very new and there was much > to learn. > > All that being said — and not strictly because of that interaction, but in >

Re: Recent events ...

Hi Ken, On Tue, Feb 04, 2025 at 09:44:24AM -0800, Ken Cunningham wrote: > All that being said — and not strictly because of that interaction, > but in respect to other general life events, I have re-evaluated how I > choose to spend my time. Life is short, as we all know, and there are

Re: funding/grants

Hi, On Mon, Feb 03, 2025 at 11:33:50PM +, grey wrote: > https://resources.github.com/github-secure-open-source-fund/ >From the reuqirements: - You can also apply as a team for a given open source project (max of 3 people). - Clear governance structure prior to kick-off - Interest and willing

Re: What's on the macports keychain?

Hi, On Tue, Feb 04, 2025 at 09:38:07AM -0300, Gregorio Litenstein wrote: > Hey all. I was about to post a ticket, but honestly this is probably > just a me problem. In fact, it's not even really a problem; more of an > annoyance, really. > > […] Just one gripe I have is that sometimes, I can't ej

Re: Recent events ...

w and there was much to > learn. > > All that being said — and not strictly because of that interaction, but in > respect to other general life events, I have re-evaluated how I choose to > spend my time. Life is short, as we all know, and there are only so many > hours in the d

Re: Recent events ...

s-ports/pull/26031 > >> > >> Any failings of mine in there are about the best I will ever be able to > do. > >> > >> There was also one brief email exchange with him where expressed his > displeasure with me, and I pointed out he was very new and there w

Re: Recent events ...

gt;> displeasure with me, and I pointed out he was very new and there was much to >> learn. >> >> All that being said — and not strictly because of that interaction, but in >> respect to other general life events, I have re-evaluated how I choose to >> spend my tim

Re: What's on the macports keychain?

On Feb 4, 2025, at 06:38, Gregorio Litenstein wrote: > > I've been running my entire macports environmen on an external drive. I make > this work almost seamlessly by having it listed in /etc/fstab and set to > mount at /opt. You will want to do something similar for /Applications/MacPorts For

Re: Recent events ...

There was also one brief email exchange with him where expressed his > displeasure with me, and I pointed out he was very new and there was much to > learn. > > All that being said — and not strictly because of that interaction, but in > respect to other general life events, I have re-eval

Re: [php84] missing extensions

I've started working on php84 - 8.4.3 https://github.com/BjarneDMat/macports-ports/tree/php84 Author: BjarneDM Date: Tue Feb 4 17:12:53 2025 +0100 1st version / try updating to stable version of php84 (8.4.3) On branch php84 Changes to be committed: modified: _resou

Re: Close ticket #51310

On 03/02/2025 20.46, Dave Allured - NOAA Affiliate via macports-dev wrote: > Please close https://trac.macports.org/ticket/51310 trac.macports.org/ticket/51310> as fixed.  Thanks. Done. Rainer

Re: [php84] missing extensions

On Feb 3, 2025, at 12:15, Bjarne D Mathiesen wrote: > > These extensions havent been updated to php84 No php extensions that are not bundled with php are available for php84 yet. I don't add extensions until I update the corresponding php port to the first stable version and I have not yet upd

Re: Time to say goodbye to Tiger?

Joshua Root wrote: By my count, 3 committers other than me have expressed unambiguous support for dropping Tiger, and 0 have expressed opposition. That's probably as clear a consensus as we're going to reach. Although understandable from the point of who does the "hard work", it is not a cle

Re: Time to say goodbye to Tiger?

On Fri, Jan 31, 2025 at 12:35:51PM +1100, Joshua Root wrote: > By my count, 3 committers other than me have expressed unambiguous support > for dropping Tiger, and 0 have expressed opposition. That's probably as > clear a consensus as we're going to reach. > > - Josh :(

Re: Time to say goodbye to Tiger?

By my count, 3 committers other than me have expressed unambiguous support for dropping Tiger, and 0 have expressed opposition. That's probably as clear a consensus as we're going to reach. - Josh

Re: Time to say goodbye to Tiger?

Hi Ryan, Ryan Carsten Schmidt wrote: On Jan 26, 2025, at 18:25, Gagan Sidhu wrote: Gagan, I'm pretty close to permanently banning you from this project. Ken is a valued contributor and doesn't deserve your insults. MacPorts is a community where people volunteer their time to make things bett

Re: Time to say goodbye to Tiger?

Hi, Fred Wright wrote: I'm never a fan of dropping something just because it's "old". You're not very specific about "workarounds for 10.4" in base, but if any code specifically related to *any* OS version isn't well-segregated, then that's a bad design.  And aside from base, what you're pro

Re: Time to say goodbye to Tiger?

Hi Josh, Joshua Root wrote: On 24/1/2025 08:19, Riccardo Mottola wrote: I understand it feels a bit wrong to throw away working hardware. There's always the option of Linux if you just need those commands? Well, linux is another Operating System. I install certain tools, e.g. gcc, ssh, git,

Re: Sequoia Local Network blocking?

On Jan 26, 2025, at 7:12 PM, Ryan Carsten Schmidt wrote: > On Jan 26, 2025, at 14:17, Daniel J. Luke wrote: >> >> After thinking that I had somehow broken my home network - it looks like >> I'm actually stumbling on Sequoia's Local Network blocking. >> >> If I ssh into a Mac on my LAN, I can'

Re: Time to say goodbye to Tiger?

where i’m from, you treat others the way they treat you. instead of admitting when he is wrong, he attacks others, puts words in their mouth and says they’re at fault. your response is not encouraging at all. it feels like you are condoning the antagonistic behaviour of the person you’re defend

Re: Time to say goodbye to Tiger?

On Jan 26, 2025, at 18:25, Gagan Sidhu wrote: > > you make this project suck. i’ve heard it from others too. > > to be honest, i wonder how many contributors this project has lost over the > past decade because of his uncivilised behaviour. Gagan, I'm pretty close to permanently banning you fro

Re: Time to say goodbye to Tiger?

does anyone notice that, ken seems to think he can attack others because he undertakes a larger role than anyone wants? as we see below, he gets upset when someone shares their own opinion and threatens to stop contributing. and who’s to say that the month-plus he spent on gcc-14 wasn’t a night

Re: Sequoia Local Network blocking?

On Jan 26, 2025, at 14:17, Daniel J. Luke wrote: > > After thinking that I had somehow broken my home network - it looks like I'm > actually stumbling on Sequoia's Local Network blocking. > > If I ssh into a Mac on my LAN, I can't ssh out using MacPorts openssh to > other hosts on the same sub

Re: Time to say goodbye to Tiger?

> Except of course when someone decides to inflict a > new compiler on it when the old one was working fine. > > Fred Wright Yes, after I last updated the gcc ports on older systems, I also then left gcc-7 as the default compiler for a very very long time specifically to avoid problems -- and

Re: Time to say goodbye to Tiger?

sorry one clarification: what i meant to say with: > what this liar stated was that 10.6-ppc uses libc++ and that the 10.6-x86_64 > variant does not. is that he stated 10.6-ppc uses libstdc++ but the 10.6-x86_64 variant does not. my apologies. certain personality traits really irritate me. > O

Re: Time to say goodbye to Tiger?

took you how long to think of a recovery, which is embedded with lies? rootie, are you going to do something about this pathological liar? should i dig up the tickets where he makes baseless accusations and never responds because he likes to abuse his power? anyways let’s revisit his post, whic

Re: Time to say goodbye to Tiger?

MacPorts defaults all builds on 10.6 to libc++, and has done for YEARS now, exactly so that supporting 10.6 won't be a huge, silly project of workarounds. libsdtc++ is supported only so far as it takes to bootstrap libc++ Everything else you said was pretty much drivel, as usual, and I'll just l

Re: Time to say goodbye to Tiger?

On Fri, 24 Jan 2025, Joshua Root wrote: This year marks the 20th anniversary of the release of Mac OS X 10.4 Tiger. It's had a good run, but it's long been getting harder and harder to support. Upstream projects are understandably reluctant to add fixes for it. The very few users who open Tr

Re: Request review of PR 26725 (p5-dbd-mysql)

Hi, It's been a while since I first requested a review of PR 26725 . I am asking again as it's been there for a while now and I'm hoping to get some feedback on what needs to be done to get it commited or if I should just abandon the effort.

Re: Time to say goodbye to Tiger?

barracuda is correct about libstdc++ being the default on 10.6 for both x86_64 and ppc. ryan even said this in a bugticket that our beloved self-anointed sage responded to: https://trac.macports.org/ticket/56042 `` 10.7 and later ship with libc++, but 10.6 doesn’t ‘' to criticise others as yo

Re: Time to say goodbye to Tiger?

Ken, you got some degree of superficial acquaintance with the system in question 2,5 years ago and keep convincing yourself and others that your, obviously emotionally biased, take represents an accurate account of reality, and that reality could not possibly have changed ever since. As a matter o

Re: Time to say goodbye to Tiger?

Well -- of course 10.6-PPC needs lots and lots and lots and lots of special workarounds. 10.6-PPC is basically 10.5 PPC wearing lipstick and a wig. It is very very different from 10.6 / Intel / libc++. It builds with gcc, not clang. It links against libstdc++, nott libc++. It does not have the

Re: Abandoned JDK Ports

Ryan Carsten Schmidt wrote: > On Jan 23, 2025, at 17:35, Nils Breunese wrote: >> >> Joshua Root wrote: >> >>> Please file a Port Abandoned ticket as per the procedure: >>> >>> >> Thanks. Tha

Re: Time to say goodbye to Tiger?

On Jan 25, 2025 at 04:34 +0800, Ken Cunningham , wrote: > PS. -- I personally have absolutely no intention of ever supporting efforts > to shoehorn MacPorts into the pre-beta of 10.6 stolen from from the Apple Dev > meeting, and agree it is just plain frickin' silly to have a crap-ton of > spag

Re: Time to say goodbye to Tiger?

On Fri, Jan 24, 2025 at 05:15:46AM +1100, Joshua Root wrote: > 10.4 is of course already unsupported in the sense that we have no > expectation that maintainers should fix any problems on OS versions > older than current-2. So practically speaking, this would mean > removing all workarounds for 10.

Re: Time to say goodbye to Tiger?

I'm done with Tiger, and it's a pain to keep supporting it. So +1 from me. Ken PS. -- I personally have absolutely no intention of ever supporting efforts to shoehorn MacPorts into the pre-beta of 10.6 stolen from from the Apple Dev meeting, and agree it is just plain frickin' silly to have a

Re: Time to say goodbye to Tiger?

On 25/1/2025 00:42, raf via macports-dev wrote: I would hate to see macports start to have a changing window of support. It would technically not be a start but a delayed resumption. We have previously dropped support for 10.3 and 10.2. - Josh

Re: Time to say goodbye to Tiger?

On 24/1/2025 08:19, Riccardo Mottola wrote: I use MacPorts on 10.4 for basic stuff, it works and is very useful. Of course I have no high expectations, since I actively work on 10.5 and there it is already a big hurdle... However having basics working: subversions, git, openssl, gnumake and suc

Re: Time to say goodbye to Tiger?

On Fri, Jan 24, 2025 at 05:15:46AM +1100, Joshua Root wrote: > This year marks the 20th anniversary of the release of Mac OS X 10.4 Tiger. > It's had a good run, but it's long been getting harder and harder to > support. Upstream projects are understandably reluctant to add fixes for it. > The ve

Re: Time to say goodbye to Tiger?

Not sure what bugs you imply in 10.5; while this is not OS of my choice, I used 10.5, and don’t remember any particular issues with it. Probably on a slow hardware some graphical bells and whistles are to be turned off, to improve GUI speed. However, context of my comparison was using MacPorts (

Re: Abandoned JDK Ports

On Jan 23, 2025, at 17:35, Nils Breunese wrote: > > Joshua Root wrote: > >> Please file a Port Abandoned ticket as per the procedure: >> >> > Thanks. That link describes creating a ticket for

Re: Abandoned JDK Ports

Joshua Root wrote: > On 23/1/2025 11:41, Nils Breunese wrote: >> Hello, >> I maintain quite a few JDK-related (Java Development Kit) ports, but there >> are also 17 JDK ports that have @usersxx as their maintainer [0]. This >> GitHub user’s profile doesn’t show any contributions after June 2023

Re: Time to say goodbye to Tiger?

No point supporting anything below 10.5. All PowerPC machines that are actually usable can run 10.5–10.6. 10.4 is much more broken than later systems and got no advantages. While I do not appreciate Homebrew policy and do not think it would be wise to mimic it, it is reasonable to expect that Ma

Re: Time to say goodbye to Tiger?

Hi, Sergey Fedorov wrote: No point supporting anything below 10.5. All PowerPC machines that are actually usable can run 10.5–10.6. 10.4 is much more broken than later systems and got no advantages. While I do not appreciate Homebrew policy and do not think it would be wise to mimic it, it is

Re: Time to say goodbye to Tiger?

Hi, Joshua Root wrote: This year marks the 20th anniversary of the release of Mac OS X 10.4 Tiger. It's had a good run, but it's long been getting harder and harder to support. Upstream projects are understandably reluctant to add fixes for it. The very few users who open Trac tickets for Tig

Re: Time to say goodbye to Tiger?

Joshua, I agree. We overachieve in the backward compatibility! The folks over at Homebrew shake their heads when we say that we support systems older than current - 2. At some point we need to regularly move the window of supported systems forward. P.S.: My oldest functioning Mac is a MacBook

Re: Abandoned JDK Ports

On 23/1/2025 11:41, Nils Breunese wrote: Hello, I maintain quite a few JDK-related (Java Development Kit) ports, but there are also 17 JDK ports that have @usersxx as their maintainer [0]. This GitHub user’s profile doesn’t show any contributions after June 2023 and the associated email addre

Re: Netatalk 4.x

On 22/1/2025 16:29, Jason Liu wrote: Install count looks super low however. Yet one more example of why we should be encouraging as many MacPorts users as possible to be installing the 'mpstats' port, so that we can obtain better statistics. It will still be a self-selected sample, with

Re: Netatalk 4.x

Netatalk can be a shim to pick this or that version, and then having several versions in parallel does not create a confusion. On Jan 22, 2025 at 11:35 +0800, bl...@netjibbing.com, wrote: > OK thanks for that info. With Netatalk, it shows as building and running back > to Snow leopard i386 now. W

Re: Netatalk 4.x

On Jan 21, 2025, at 23:30, Jason Liu wrote: > > but I also don't remember how difficult it would be to turn a completely > separate port into a subport of another later on. Subports are merely a convenience for the programmer; there is no difference for the end user. If it is easier for the pro

Re: Netatalk 4.x

> > What if I make a netatalk4 port and give that some time to bake before > making changes to the netatalk port to select the newer version based on OS? Off the top of my head, I can't think of any reason why that would be a problem, but I also don't remember how difficult it would be to turn a

Re: Netatalk 4.x

OK thanks for that info. With Netatalk, it shows as building and running back to Snow leopard i386 now. What if I make a netatalk4 port and give that some time to bake before making changes to the netatalk port to select the newer version based on OS? Install count looks super low however. I 100

Re: Netatalk 4.x

Take a look at the Portfile for MoltenVK: https://github.com/macports/macports-ports/blob/master/graphics/MoltenVK/Portfile The base MoltenVK port, which is just a stub, will select the correct versioned subport based on the user's macOS version. Unfortunately, there is no way to know how to divi

Re: Netatalk 4.x

I like that idea. Is there a good example port that already does this? My plan is to get a functional PR started and hope for some collaborative advice.  I’m not very interested in spending a lot of effort testing every possible version of macOS. Can these supports have their own supported macOS ve

Re: Netatalk 4.x

Yeah, this is a better idea, perhaps. On Tue, Jan 21, 2025 at 10:13 AM Jason Liu wrote: > Whoever updates the Portfile, can you make sure to preserve the old > version(s) of netatalk using a versioned subport, i.e. 'netatalk3', > 'netatalk2' (or whatever), so that old versions of macOS can still

  1   2   3   4   5   6   7   8   9   10   >