On Jun 27, 2007, at 12:49, Eric Hall wrote:
On Thu, Jun 21, 2007 at 09:31:25AM -0400, Daniel J. Luke wrote:
On Jun 21, 2007, at 5:35 AM, Ryan Schmidt wrote:
Is MacPorts officially no longer supporting Jaguar?
Our policy (from quite a while ago) is to support the current Mac OS
X major release, and the one previous to it (so currently 10.4 and
10.3).
If we are officially no longer supporting Jaguar, then MacPorts
should decline to install on that OS, port should decline to run on
that OS, and we should remove all darwin 6 platform selectors from
all ports.
I think it's better to make the policy clear to the end-user and let
them try to make things work if they want to (and I don't think the
project would be opposed to including patches to fix things on older
'non-supported' releases, just like how we're happy to include fixes
for other operating systems that aren't them main focus of macports).
I agree, I don't see a reason to take actions to make supporting
older OS versions more difficult. Perhaps a message to the user (at
install time, that they have to ack) indicating their OS version is
no longer officially supported would be good.
I think the from-source installer is not interactive, and the dmg
installer uses Apple Installer which doesn't provide a way to prompt
users for arbitrary questions...
I'm ok with keeping old Jaguar stuff in the portfiles. This desire
should however be clearly communicated to all portfile authors then,
mentioned in the (absent) documentation, etc. I have previously
received patches that have explicitly removed Jaguar support from my
portfiles, on the sole basis that it's no longer supported by
MacPorts. (See e.g. ticket #11934.)
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
