Date: Mon, 31 Mar 1997 20:28:43 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.ru> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Mark Murray <mark@grondar.za>, John Fieber <jfieber@indiana.edu>, Kevin Eliuk <kevin_eliuk@sunshine.net>, FreeBSD-Ports <freebsd-ports@freebsd.org>, peter@freebsd.org Subject: Re: Error installing pine-3.96 Message-ID: <Pine.BSF.3.96.970331202521.788A-100000@nagual.ru> In-Reply-To: <11502.859825093@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 31 Mar 1997, Jordan K. Hubbard wrote: > > Example - SSH. SSH is one of those things that folk always want the > > latest version of. We moved libz and libgmp into mainstream code, > > but our versions in the RELENG_* branch are not those that the port > > wanted. Making this work was _very_ dirty. Around these parts, most > > folk just gave up, said "sod the ports system" and rolled their own. > > Cock-ups abounded. > > I'm aware of those specific examples, though I also think that our > propensity for bringing things like this into FreeBSD has waned in > recent months and I don't expect it to be such a big problem. Why not > shoot for overall compatibility and cross the occasional ports->src > migration problem (and I hope very occasional or even I will start > yelling "Bloat! Bloat!" along with the bloatist camp) when we come to > it? We need to split ports team in two parts: one do -current compatibility (f.e. myself) and other one 2.2 compatibility. Of course the same person can be included into two groups at once. Droping -current compatibility from ports is very bad idea and I strongy object because many -current features, incompatibilities, bugs revealed from running -current ports... -- Andrey A. Chernov <ache@null.net> http://www.nagual.ru/~ache/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970331202521.788A-100000>