Date: Sun, 04 Jan 2015 09:51:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 196480] www/nginx-devel: This port should be named nginx-mainline not -devel Message-ID: <bug-196480-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196480 Bug ID: 196480 Summary: www/nginx-devel: This port should be named nginx-mainline not -devel Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: osa@FreeBSD.org Reporter: rsimmons0@gmail.com Assignee: osa@FreeBSD.org Flags: maintainer-feedback?(osa@FreeBSD.org) If a -devel version of the port is needed, it should be a mercurial checkout from the source repository for NGINX at the head of the master branch. This port should be called nginx-mainline as its referred to in the upstream project. Calling this port -devel is misleading, since this is not really a development branch. The following is a quote from the upstream project's blog: Which version should I use? In general, you should deploy the NGINX mainline branch at all times. You may wish to use stable if you are concerned about possible impacts of new features, such as incompatibility with third-party modules or the introduction of bugs in new features. http://nginx.com/blog/nginx-1-6-1-7-released/ Some people who are not familiar with the upstream project may shy away from installing a port named -devel when they should not. --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Auto-assigned to maintainer osa@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196480-13>