Date: Sat, 22 Oct 2016 08:27:28 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 213679] www/py-django16-tastypie: Should deprecate because django16 expired Message-ID: <bug-213679-21822-fmtcZCpAwu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213679-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-213679-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213679 --- Comment #7 from Kubilay Kocak <koobs@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-* (with= out the history). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213679-21822-fmtcZCpAwu>