Date: Thu, 29 Jun 2000 18:38:09 +0300 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Ade Lovett <ade@FreeBSD.org> Cc: "David O'Brien" <obrien@FreeBSD.org>, cvs-committers@FreeBSD.org, ports@FreeBSD.org Subject: Re: Diking out ports a.out support (was Re: cvs commit: ports/audio/sidplay Makefile) Message-ID: <395B6D60.65640F29@FreeBSD.org> References: <200006230927.CAA23802@freefall.freebsd.org> <20000623080800.F77304@argon.gryphonsoft.com> <3953573F.7B95B83E@FreeBSD.org> <20000623094306.I44870@FreeBSD.org> <20000628221306.G31775@dragon.nuxi.com> <20000629103349.D31932@lovett.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ade Lovett wrote: > On Wed, Jun 28, 2000 at 10:13:06PM -0700, David O'Brien wrote: > > On Fri, Jun 23, 2000 at 09:43:06AM -0500, Ade Lovett wrote: > > > Agreed. At the same time, any remnants of PORTOBJFORMAT, or a.out > > > shared library names in PLISTs, or aout in general needs to go > > > (adios 2.x) > > > > Since we already have the machanism in place, I fail to see what we gain > > by diking it out. Since we have a method, there is no reason to not give > > the 2.x users a fighting chance of getting a port to build and install. > > Well, in my eyes, it is extra "cruft" that is no longer needed, since > it's stated quite clearly that ports only supports -stable and -current > and that anything else is a fluke. > > Second, we're almost certainly going to be visiting a large number > of PLISTs in the not to distant future with the "famous" NOPORTDOCS > hack, which is already being used elsewhere to manage PLISTS more > effectively. > > Third, someone staying with an a.out machine is doing so for reasons > of extreme stability -- adding new-fangled versions of ports would > go against that stability. > > Fourth, killing a.out support just after 4.1-RELEASE means that > we'll have had 7 releases (3.1 and up) since an purely a.out > FreeBSD system existed. That's an awful long time to keep legacy > around. > > Finally, I would imagine that most ports going in now rely on other > ports where there is no a.out support, so there's going to be > very little chance of them ever working under a.out > > Having said all of the above, I'm willing to go with the majority. > (Perhaps we need a freebsd-portsarch.. just kidding :) Seconded (I'm forwarding it to -ports where it belongs). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?395B6D60.65640F29>