Date: Mon, 2 Nov 2009 08:52:35 +0300 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: freebsd-ports@freebsd.org Subject: Renaming port when it forks to two different branches Message-ID: <YeZ0UD/3YXhjDo1EpRG5kb3dBd4@m7CpruDFVVXtHTpJF1FPSUwA%2BUQ>
next in thread | raw e-mail | index | archive | help
Good day.
I am maintaining net-mgmt/pnp and it was recently brought to my
attention that the current port development line (0.4.x) will cease in
some time and now we have 0.6.x that is better, will be supported and
developed further. But it requires PHP >= 5.2. I am planning to
upgrade the net-mgmt/pnp to 0.6.x and make request to repocopy the
current (0.4.x-based) port to net-mgmt/pnp-legacy.
Here comes a question: does anyone sees any drawbacks from such
a plan and may be there are better ways to do it?
Thanks!
--
Eygene
_ ___ _.--. #
\`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard
/ ' ` , __.--' # to read the on-line manual
)/' _/ \ `-_, / # while single-stepping the kernel.
`-'" `"\_ ,_.-;_.-\_ ', fsc/as #
_.-'_./ {_.' ; / # -- FreeBSD Developers handbook
{_.-``-' {_/ #
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YeZ0UD/3YXhjDo1EpRG5kb3dBd4>