Re: www/nginx-devel Name Change
Hi Robert, On Wed, Mar 04, 2015 at 04:52:58PM -0500, Robert Simmons wrote: The port www/nginx-devel should really be renamed nginx-mainline. It is definitely not the development branch as is explained by the upstream project. Calling it devel may cause users to avoid using this port over the www/nginx port. I have a detailed explanation of this in a bug report here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196480 Does this seem logical? Objection. The nginx project basically provides two versions of nginx: stable and mainline. New releases of the stable version contains bug and security fixes. The mainline usually introduces a bugs in a new features. This is why it has been marked with '-devel' suffix. For stable version FreeBSD ports tree historycally uses the same name as a software product has been named by author, for development version with '-devel' prefix. Also, I see no reason why user may cause to avoid using the www/nginx-devel port. Think it's always up to user to use or not to use any port from FreeBSD ports tree as well as FreeBSD operating system. -- Sergey A. Osokin o...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: www/nginx-devel Name Change
Also, I don't believe that bugs in new features has the same meaning as development. On Sat, Mar 7, 2015 at 1:46 AM, Robert Simmons rsimmo...@gmail.com wrote: Here is a quote from the NGINX project: 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. From this and checking the source code repository here: hg.nginx.org/nginx the development branch is default. Perhaps the -devel port should be tied to a specific date on the true development branch? I am only interested in calling a spade a spade here to reduce confusion. If the NGINX project called mainline development there wouldn't be a problem. But it seems that this is a distinction that FreeBSD has decided rather than using upstream terminology and thinking. On Fri, Mar 6, 2015 at 11:02 PM, Sergey A. Osokin o...@freebsd.org wrote: Hi Robert, On Wed, Mar 04, 2015 at 04:52:58PM -0500, Robert Simmons wrote: The port www/nginx-devel should really be renamed nginx-mainline. It is definitely not the development branch as is explained by the upstream project. Calling it devel may cause users to avoid using this port over the www/nginx port. I have a detailed explanation of this in a bug report here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196480 Does this seem logical? Objection. The nginx project basically provides two versions of nginx: stable and mainline. New releases of the stable version contains bug and security fixes. The mainline usually introduces a bugs in a new features. This is why it has been marked with '-devel' suffix. For stable version FreeBSD ports tree historycally uses the same name as a software product has been named by author, for development version with '-devel' prefix. Also, I see no reason why user may cause to avoid using the www/nginx-devel port. Think it's always up to user to use or not to use any port from FreeBSD ports tree as well as FreeBSD operating system. -- Sergey A. Osokin o...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: www/nginx-devel Name Change
Here is a quote from the NGINX project: 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. From this and checking the source code repository here: hg.nginx.org/nginx the development branch is default. Perhaps the -devel port should be tied to a specific date on the true development branch? I am only interested in calling a spade a spade here to reduce confusion. If the NGINX project called mainline development there wouldn't be a problem. But it seems that this is a distinction that FreeBSD has decided rather than using upstream terminology and thinking. On Fri, Mar 6, 2015 at 11:02 PM, Sergey A. Osokin o...@freebsd.org wrote: Hi Robert, On Wed, Mar 04, 2015 at 04:52:58PM -0500, Robert Simmons wrote: The port www/nginx-devel should really be renamed nginx-mainline. It is definitely not the development branch as is explained by the upstream project. Calling it devel may cause users to avoid using this port over the www/nginx port. I have a detailed explanation of this in a bug report here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196480 Does this seem logical? Objection. The nginx project basically provides two versions of nginx: stable and mainline. New releases of the stable version contains bug and security fixes. The mainline usually introduces a bugs in a new features. This is why it has been marked with '-devel' suffix. For stable version FreeBSD ports tree historycally uses the same name as a software product has been named by author, for development version with '-devel' prefix. Also, I see no reason why user may cause to avoid using the www/nginx-devel port. Think it's always up to user to use or not to use any port from FreeBSD ports tree as well as FreeBSD operating system. -- Sergey A. Osokin o...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
www/nginx-devel Name Change
The port www/nginx-devel should really be renamed nginx-mainline. It is definitely not the development branch as is explained by the upstream project. Calling it devel may cause users to avoid using this port over the www/nginx port. I have a detailed explanation of this in a bug report here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196480 Does this seem logical? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
