[Bug 213679] www/py-django16-tastypie: Should deprecate because django16 expired

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213679

--- Comment #7 from Kubilay Kocak <koobs at FreeBSD.org> ---
(In reply to Dan Langille from comment #4)

I wouldn't use move for renames including version updates (foo16 -> foo18).

Having said that, I'm sure someone might argue both a move and copy/delete
require a MOVED entry and a single operation is better than one.

Having said that, as a user of a port fooXY, I would *not* expect that port
ever to move past version X.Y, which a move would do.

My vote would be for a copy+version update (new port), and then a deletion of
16 (expired), OR, just delete django16-*, and create a new django18-* (without
the history).

-- 
You are receiving this mail because:
You are on the CC list for the bug.