Date: Mon, 07 Dec 2009 20:53:31 +0300 From: Alex Keda <admin@lissyara.su> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: ports@freebsd.org, Oliver Schonrock <oliver@realtsp.com>, Doug Barton <dougb@FreeBSD.org>, Alex Dupre <ale@FreeBSD.org>, alistair@realtsp.com Subject: Re: FreeBSD Port: php5-5.2.11_1 upgrade path to 5.3.0/1 Message-ID: <4B1D411B.4000602@lissyara.su> In-Reply-To: <4AF568E1.8090803@quip.cz> References: <200911051539.21097.oliver@realtsp.com> <4AF4110C.6060501@FreeBSD.org> <4AF4308B.4080905@quip.cz> <4AF43319.1010909@FreeBSD.org> <4AF44DE2.2040304@quip.cz> <4AF45FDF.4030800@FreeBSD.org> <4AF568E1.8090803@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Miroslav Lachman пишет: > Seriously - if ports team is willing to have "legacy" versions in ports, > we need to discuss some rules for this work. Not just for PHP, but more > general. In which conditions we need/allow them, the naming conventions > (some ports already have more versions but names are not consistent, > some ports are using -dev, -devel, -current [3 different sufixes for the > development branch], Perl always uses p5- prefix, Python have py25-, > py26- etc.) > So is it better to renumber the legacy (forked) version to > php52-ext_name-5.2.12 leaving php5- line for 5.3 version or do it like > Python (py25, py26): php52- and php53-. It's good idea. But, it may be very hard. I very small know about port system (but, I maintain two or three ports =)), but can small help - some test, or "hands" operations (rename, & etc)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B1D411B.4000602>