Re: Removal of acorn26 port
acorn26 was moved to Tier III last week and unless someone steps forward it will be removed sometime in Mid-October 2015. To quote http://www.netbsd.org/ports/ : “The reasons can range from lack of community interest to the hardware becoming so rare that it is simply not available any more. Both are true. Removing arm26 support from the common arm code will make maintain arm code easier.
Re: Removal of acorn26 port
On 17 April 2015 at 13:02, Thomas Mueller mueller6...@bellsouth.net wrote: Moving a port to Tier III and letting it become more broken is not fair; better to be honest and put it out of its misery. It has been moved to tier III... https://www.netbsd.org/ports/ Since there is no immediate urgency, maybe give two weeks or a month for anybody who uses port-acorn26 to speak up, then delete if nobody comes forward. I can't figure how I'd use it or find a compatible computer; running in an emulator doesn't really count. I could probably find a computer here in the UK, but have other things I would rather work on. Justin
Re: Removal of acorn26 port
On Fri 17 Apr 2015 at 12:02:04 +, Thomas Mueller wrote: For that matter, does anybody still use port-vax? I have a few microVAXen... -Olaf. -- ___ Olaf 'Rhialto' Seibert -- The Doctor: No, 'eureka' is Greek for \X/ rhialto/at/xs4all.nl-- 'this bath is too hot.' pgpxDeoZtn55O.pgp Description: PGP signature
Re: Removal of acorn26 port
Hi, I can't figure how I'd use it or find a compatible computer; running in an emulator doesn't really count. True. Just like the ns32k, it was nice, but without hardware to run it, it's hardly worth the effort. For that matter, does anybody still use port-vax? Actually, yes. That port gets much more use. VAXen are pretty common and they're more than just a curiosity. Mine are used for various things - secondary DNS and backup MX in a non-temperature controlled location, performance profiling of code which will eventually run on embedded hardware, edge case testing of floating point code and so on. netbsd-6 runs just fine on VAXen, but netbsd-7 and current have toolchain issues at the moment. In some ways removal of acorn26 isn't too unlike the removal of support for i80386 processors from the i386 port (the name is a bit of a misnomer now, though). John
Removal of acorn26 port
Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it.
Re: Removal of acorn26 port
On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ Justin
Re: Removal of acorn26 port
Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. Does the port currently work? If so, maybe it'd be nice to have a 7.0 release before it's removed so it's clear what the last known working release, tag and date are. John
Re: Removal of acorn26 port
On Wed, Apr 15, 2015 at 01:20:33PM -0700, Matt Thomas wrote: On Apr 15, 2015, at 10:28 AM, Justin Cormack jus...@specialbusservice.com wrote: On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011. It should also be said that noone really cares about pre-ARMv4 in toolchain-land. We are already the odd kid for caring about ARMv4. Joerg
Re: Removal of acorn26 port
On Apr 15, 2015, at 10:28 AM, Justin Cormack jus...@specialbusservice.com wrote: On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011.
Re: Removal of acorn26 port
In article trinity-40fe500f-df8d-4b60-a4b4-3b73f95b9bfe-1429133530648@3capp-mailcom-bs10, Kamil Rytarowski n...@gmx.com wrote: I strongly agree, please follow the rules and move it to Tier III even now. There are more broken or incomplete ports than acorn26. acorn26 should run on emulators/arcem, it's worth to give it a try. I a proponent of following the rules, but I feel we've been dragging dead bodies and it's having an impact in our available resources. People who use the port should shout if they want the port kept around. christos
Re: Removal of acorn26 port
Justin Cormack jus...@specialbusservice.com wrote: acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011. Yes, I am sure it qualifies to move to tier III, and has done for some years. Procedurally, moving it officially to tier III and then removing all support for it from the common code to make it even more broken (it would then be removed from the build matrix), and then deleting it in 6 months might be better than just deleting it now. Back in 2009 when I removed uarea swap-out [1], I managed to find only *one* user of acorn26 - its former maintainer (bjh21). He managed to boot to single-user mode but run out of time trying multi-user. Since then nobody managed to show acorn26 being usable without uarea swapout. There is really no point to keep it dusting. [1] https://mail-index.netbsd.org/source-changes/2009/10/21/msg002198.html -- Mindaugas
Re: Removal of acorn26 port
Sent: Wednesday, April 15, 2015 at 9:25 PM From: Justin Cormack jus...@specialbusservice.com To: Matt Thomas m...@3am-software.com Cc: port-arm port-...@netbsd.org, current-users current-users@netbsd.org, port-acor...@netbsd.org Subject: Re: Removal of acorn26 port On 15 April 2015 at 21:20, Matt Thomas m...@3am-software.com wrote: On Apr 15, 2015, at 10:28 AM, Justin Cormack jus...@specialbusservice.com wrote: On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011. Yes, I am sure it qualifies to move to tier III, and has done for some years. Procedurally, moving it officially to tier III and then removing all support for it from the common code to make it even more broken (it would then be removed from the build matrix), and then deleting it in 6 months might be better than just deleting it now. I strongly agree, please follow the rules and move it to Tier III even now. There are more broken or incomplete ports than acorn26. acorn26 should run on emulators/arcem, it's worth to give it a try. Justin
Re: Removal of acorn26 port
On 15 April 2015 at 21:20, Matt Thomas m...@3am-software.com wrote: On Apr 15, 2015, at 10:28 AM, Justin Cormack jus...@specialbusservice.com wrote: On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011. Yes, I am sure it qualifies to move to tier III, and has done for some years. Procedurally, moving it officially to tier III and then removing all support for it from the common code to make it even more broken (it would then be removed from the build matrix), and then deleting it in 6 months might be better than just deleting it now. Justin
