nginx port

Clemens Lang cal at macports.org
Tue Sep 30 12:13:52 PDT 2014


Hi,

----- On 30 Sep, 2014, at 11:16, Ivan Larionov xeron.oskom at gmail.com wrote:

> https://trac.macports.org/changeset/125927
> 
> How you can say it’s not “unstable” if 2 modules doesn’t work at all?

Upstream no longer calls it unstable and recommends using mainline rather
than stable:

"Note that stable does not mean ‘more reliable or more bug-free’. In fact,
 mainline is generally regarded as more reliable because only critical
 fixes are merged to stable."

The packaging of stable was a remnant from a time when what now is
mainline was still called "unstable" (and obviously unstable isn't
something we package in MacPorts).

The modules don't affect whether the main port is stable or not. These
are 3rd party modules, and apparently these 3rd parties are currently
lagging behind nginx development. If you want to help out getting them
compatible with 1.7.5 I'm sure they'd welcome some help. Most of these
changes are simple renames anyway and easily fixed. If you can provide a
patch that fixes the build for one of the modules, I'd happily apply it.


> May be it’s better to have 2 different ports, like nginx and nginx-devel?

No. This would mean more effort for me which I am not willing to spend on
the already pretty time-intensive nginx port. If somebody else wants to do
the extra work he/she is very welcome to provide a patch.

-- 
Clemens Lang


More information about the macports-dev mailing list