Date: Sun, 31 Dec 2017 17:31:01 -0800 From: Ultima <ultima1252@gmail.com> To: Alfred Perlstein <alfred@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r457271 - head/www/py-djangorestframework Message-ID: <CANJ8om6DLHpTR0CrB=qnGT65sWWt4aCCC7afeDxkL7EvSXFOzQ@mail.gmail.com> In-Reply-To: <ec5b1d96-9f9a-fdcf-7e21-69a540b7ff99@freebsd.org> References: <201712261012.vBQACwJ9016524@repo.freebsd.org> <CANJ8om7cmXZKaQ5tmoeMf1yB74NjmNt37icexzhLogph6E145w@mail.gmail.com> <ec3563a8-4ef0-e2ca-b370-992dae6a6496@freebsd.org> <CANJ8om7SsjeC2ozRTp9BQa5r1i2pr7%2Bu5ipc4rSgVG=Egu8=OA@mail.gmail.com> <ec5b1d96-9f9a-fdcf-7e21-69a540b7ff99@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Back ~17 years ago, when I first started committing to ports, what we would have done is just made a version py-djangorestframework364 > and fixed up the dependencies for Seafile (and other older things) to point to this stuck older version if the port was truly (Seafile) that important. > Will that work? It would, but I think one of the points for making flavors was to remove these version specific ports. Looks like antoine@ decided to do option 3 and not break the django18 ports. D12592 looks like its ready for commit so I think we should just wait for that. I'll make a patch once its committed into the tree if you would like. Best regards, Richard Gallamore
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANJ8om6DLHpTR0CrB=qnGT65sWWt4aCCC7afeDxkL7EvSXFOzQ>