[MacPorts] #31004: nginx should not own nginx.conf

[MacPorts]

#31004: nginx should not own nginx.conf
------------------------------+---------------------------------------------
 Reporter:  ast@…             |       Owner:  macports-tickets@…                   
     Type:  defect            |      Status:  new                                  
 Priority:  Normal            |   Milestone:                                       
Component:  ports             |     Version:  2.0.1                                
 Keywords:                    |        Port:  nginx                                
------------------------------+---------------------------------------------
Description changed by ryandesign@…:

Old description:

> Just hit this one today when I was trying to configure nginx with SSL on
> my development machine.  Had made all the required changes to configure a
> new server instance in my nginx.conf (I don't use subconfigs on this
> box), and then got this message:
>
> {{{
> valkyrie$ sudo nginx -s reload
> nginx: [emerg] unknown directive "ssl" in
> /opt/local/etc/nginx/nginx.conf:99
> }}}
>
> Finding this page [http://kete.net.nz/documentation/topics/show/167
> -configure-nginx-to-use-ssl], I followed the instructions, but once I'd
> deactivated nginx, ''it deleted my nginx.conf file! ''
>
> Even RPM got this right over 15 years ago, so I can't understand why this
> package has so much trouble whacking configuration files (see my other
> ticket: [https://trac.macports.org/ticket/27354]).
>
> The nginx.conf file shouldn't be part of the files managed by the
> installation, or if it is, it needs to be checked against either a
> modification time or a hash value of the package one so that these
> problems don't happen.

New description:

 Just hit this one today when I was trying to configure nginx with SSL on
 my development machine.  Had made all the required changes to configure a
 new server instance in my nginx.conf (I don't use subconfigs on this box),
 and then got this message:

 {{{
 valkyrie$ sudo nginx -s reload
 nginx: [emerg] unknown directive "ssl" in
 /opt/local/etc/nginx/nginx.conf:99
 }}}

 Finding this page [http://kete.net.nz/documentation/topics/show/167
 -configure-nginx-to-use-ssl], I followed the instructions, but once I'd
 deactivated nginx, ''it deleted my nginx.conf file! ''

 Even RPM got this right over 15 years ago, so I can't understand why this
 package has so much trouble whacking configuration files (see my other
 ticket: #27354).

 The nginx.conf file shouldn't be part of the files managed by the
 installation, or if it is, it needs to be checked against either a
 modification time or a hash value of the package one so that these
 problems don't happen.

--

-- 
Ticket URL: <https://trac.macports.org/ticket/31004#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS