Closed p5pRT closed 6 years ago
perl dropped MacOS classic and EPOC support many years ago. There is no point in keeping support for them in PathTools.
This change will make any further work on PathTools a bit easier.
the patch is attached
Due to code freeze\, we'll defer evaluation of this ticket until after release of perl-5.26.0.
Thank you very much. -- James E Keenan (jkeenan@cpan.org)
On Sun\, Feb 19\, 2017 at 09:36:46AM -0800\, Tomasz Konojacki wrote:
perl dropped MacOS classic and EPOC support many years ago. There is no point in keeping support for them in PathTools.
This change will make any further work on PathTools a bit easier.
But since PathTools is dual-lifed\, is there any possibility that someone will want to use a newer CPAN PathTools release on an old perl running on such a platform? Or are MacOS classic and EPOC so old that they're not supported on any perl that supports PathTools?
-- Hofstadter's Law: It always takes longer than you expect\, even when you take into account Hofstadter's Law.
The RT System itself - Status changed from 'new' to 'open'
On Wed\, Mar 29\, 2017 at 11:39 AM\, Dave Mitchell \davem@​iabyn\.com wrote:
But since PathTools is dual-lifed\, is there any possibility that someone will want to use a newer CPAN PathTools release on an old perl running on such a platform? Or are MacOS classic and EPOC so old that they're not supported on any perl that supports PathTools?
MakeMaker dropped MacOS classic support in 2004\, and the commit message says it "hasn't worked since 5.5x". I think we can safely assume it's dead. EPOC is the predecessor of Symbian\, and apparently we're already using FIle::Spec::Win32 on Symbian so it also seems of little use (I have no idea if Perl on Symbian is in a working state).
Leon
On Wed\, 29 Mar 2017 09:03:33 -0700\, LeonT wrote:
On Wed\, Mar 29\, 2017 at 11:39 AM\, Dave Mitchell \davem@​iabyn\.com wrote:
But since PathTools is dual-lifed\, is there any possibility that someone will want to use a newer CPAN PathTools release on an old perl running on such a platform? Or are MacOS classic and EPOC so old that they're not supported on any perl that supports PathTools?
MakeMaker dropped MacOS classic support in 2004\, and the commit message says it "hasn't worked since 5.5x". I think we can safely assume it's dead.
Perl may not run on MacOS classic any more\, but many Mac OS X GUI applications still use old-style paths. The ability to manipulate them in a Perl script is still valuable.
--
Father Chrysostomos
On Thu\, Mar 30\, 2017 at 12:39 AM\, Father Chrysostomos via RT \perlbug\-followup@​perl\.org wrote:
Perl may not run on MacOS classic any more\, but many Mac OS X GUI applications still use old-style paths. The ability to manipulate them in a Perl script is still valuable.
That is an interesting point. It actually seems at least one module on CPAN does exactly this (Mac::iPod::Gnupod). Guess it's not as dead as thought.
Leon
On Wed\, 29 Mar 2017 15:39:28 -0700\, sprout wrote:
Perl may not run on MacOS classic any more\, but many Mac OS X GUI applications still use old-style paths. The ability to manipulate them in a Perl script is still valuable.
If it's the case and there's still some support for old-style paths in OS X\, we indeed should consider keeping File::Spec::MacOS.
However\, I think that MacOS-specific code in Cwd.pm should be removed anyway. That code isn't platform independent and will work only when $^O eq 'MacOS'\, which means it's useless on other (i.e. supported) platfoms.
On Wed\, 29 Mar 2017 02:40:29 -0700\, davem wrote:
But since PathTools is dual-lifed\, is there any possibility that someone will want to use a newer CPAN PathTools release on an old perl running on such a platform? Or are MacOS classic and EPOC so old that they're not supported on any perl that supports PathTools?
The last EPOC device was released in 1999. EPOC perl port wasn't much more than a toy and I'd be surprised if anyone is still using it\, let alone relying on it.
Regarding MacOS\, I have nothing to add to the other posts in this thread.
On Thu\, 30 Mar 2017 00:40:48 GMT\, me@xenu.pl wrote:
On Wed\, 29 Mar 2017 02:40:29 -0700\, davem wrote:
But since PathTools is dual-lifed\, is there any possibility that someone will want to use a newer CPAN PathTools release on an old perl running on such a platform? Or are MacOS classic and EPOC so old that they're not supported on any perl that supports PathTools?
The last EPOC device was released in 1999. EPOC perl port wasn't much more than a toy and I'd be surprised if anyone is still using it\, let alone relying on it.
Regarding MacOS\, I have nothing to add to the other posts in this thread.
Tomasz:
It seems there is more consensus for removing support for EPOC tool in PathTools than for MacOS.
In order to move this RT toward resolution\, would you be able to provide a patch that *only* removes EPOC support?
Thank you very much.
-- James E Keenan (jkeenan@cpan.org)
On Tue\, 16 May 2017 00:58:39 GMT\, jkeenan wrote:
On Thu\, 30 Mar 2017 00:40:48 GMT\, me@xenu.pl wrote:
On Wed\, 29 Mar 2017 02:40:29 -0700\, davem wrote:
But since PathTools is dual-lifed\, is there any possibility that someone will want to use a newer CPAN PathTools release on an old perl running on such a platform? Or are MacOS classic and EPOC so old that they're not supported on any perl that supports PathTools?
The last EPOC device was released in 1999. EPOC perl port wasn't much more than a toy and I'd be surprised if anyone is still using it\, let alone relying on it.
Regarding MacOS\, I have nothing to add to the other posts in this thread.
Tomasz:
It seems there is more consensus for removing support for EPOC tool in PathTools than for MacOS.
In order to move this RT toward resolution\, would you be able to provide a patch that *only* removes EPOC support?
I decided to try to do this myself. I started from the patch already submitted in this RT. However\, I found several mentions of /EPOC/i in the core distribution apart from those addressed in the original patch. In addition\, when you modify source code in\, say\, File::Spec::Unix\, you have to bump $VERSION in all the *.pm files under dist/File-Spec.
The results so far can be found in the smoke-me/jkeenan/130818-remove-epoc branch. That still needs more work\, since:
* There are 2 modules under cpan/ which refer to EPOC. Our protocol is that those should be corrected upstream first.
* I made no attempt to revise the data in Module::CoreList to reflect removal of one .pm file and the modification of several others.
All this\, of course\, presumes that we have actually made a final decision to remove EPOC support from the core distribution -- and we haven't done that yet.
Thank you very much.
-- James E Keenan (jkeenan@cpan.org)
On Wed\, 14 Jun 2017 01:34:57 GMT\, jkeenan wrote:
On Tue\, 16 May 2017 00:58:39 GMT\, jkeenan wrote:
On Thu\, 30 Mar 2017 00:40:48 GMT\, me@xenu.pl wrote:
On Wed\, 29 Mar 2017 02:40:29 -0700\, davem wrote:
But since PathTools is dual-lifed\, is there any possibility that someone will want to use a newer CPAN PathTools release on an old perl running on such a platform? Or are MacOS classic and EPOC so old that they're not supported on any perl that supports PathTools?
The last EPOC device was released in 1999. EPOC perl port wasn't much more than a toy and I'd be surprised if anyone is still using it\, let alone relying on it.
Regarding MacOS\, I have nothing to add to the other posts in this thread.
Tomasz:
It seems there is more consensus for removing support for EPOC tool in PathTools than for MacOS.
In order to move this RT toward resolution\, would you be able to provide a patch that *only* removes EPOC support?
I decided to try to do this myself. I started from the patch already submitted in this RT. However\, I found several mentions of /EPOC/i in the core distribution apart from those addressed in the original patch. In addition\, when you modify source code in\, say\, File::Spec::Unix\, you have to bump $VERSION in all the *.pm files under dist/File-Spec.
The results so far can be found in the smoke-me/jkeenan/130818-remove- epoc branch. That still needs more work\, since:
* There are 2 modules under cpan/ which refer to EPOC. Our protocol is that those should be corrected upstream first.
* I made no attempt to revise the data in Module::CoreList to reflect removal of one .pm file and the modification of several others.
All this\, of course\, presumes that we have actually made a final decision to remove EPOC support from the core distribution -- and we haven't done that yet.
Sawyer: Can we get a thumbs up for this removal of EPOC support from PathTools?
If so\, I'll proceed with the next steps.
-- James E Keenan (jkeenan@cpan.org)
On 06/22/2017 05:28 PM\, James E Keenan via RT wrote:
On Wed\, 14 Jun 2017 01:34:57 GMT\, jkeenan wrote:
On Tue\, 16 May 2017 00:58:39 GMT\, jkeenan wrote:
On Thu\, 30 Mar 2017 00:40:48 GMT\, me@xenu.pl wrote:
On Wed\, 29 Mar 2017 02:40:29 -0700\, davem wrote:
But since PathTools is dual-lifed\, is there any possibility that someone will want to use a newer CPAN PathTools release on an old perl running on such a platform? Or are MacOS classic and EPOC so old that they're not supported on any perl that supports PathTools? The last EPOC device was released in 1999. EPOC perl port wasn't much more than a toy and I'd be surprised if anyone is still using it\, let alone relying on it.
Regarding MacOS\, I have nothing to add to the other posts in this thread. Tomasz:
It seems there is more consensus for removing support for EPOC tool in PathTools than for MacOS.
In order to move this RT toward resolution\, would you be able to provide a patch that *only* removes EPOC support?
I decided to try to do this myself. I started from the patch already submitted in this RT. However\, I found several mentions of /EPOC/i in the core distribution apart from those addressed in the original patch. In addition\, when you modify source code in\, say\, File::Spec::Unix\, you have to bump $VERSION in all the *.pm files under dist/File-Spec.
The results so far can be found in the smoke-me/jkeenan/130818-remove- epoc branch. That still needs more work\, since:
* There are 2 modules under cpan/ which refer to EPOC. Our protocol is that those should be corrected upstream first.
* I made no attempt to revise the data in Module::CoreList to reflect removal of one .pm file and the modification of several others.
All this\, of course\, presumes that we have actually made a final decision to remove EPOC support from the core distribution -- and we haven't done that yet.
Sawyer: Can we get a thumbs up for this removal of EPOC support from PathTools?
I agree with removing the Mac OS specific code from Cwd.pm\, but not removing File::Spec::MacOS. (Just to be clear on it.)
I've removed support for running PathTools on EPOC in commit e9a5b59fedc30cba91617c6b239f9568cf4ce08e\, and on MacOS Classic in commit e229c0feaa828e8255bda950ed3456ef196226b3. There's no reason to remove support for processing paths of those platforms. This ticket can be closed.
-zefram
@iabyn - Status changed from 'open' to 'resolved'
Migrated from rt.perl.org#130818 (status was 'resolved')
Searchable as RT130818$