[MacPorts] #29849: group php5extension - add default configs to *.ini files

MacPorts noreply at macports.org
Thu Jun 16 10:34:38 PDT 2011


#29849: group php5extension - add default configs to *.ini files
--------------------------------------+-------------------------------------
 Reporter:  macintosh@…               |       Owner:  ryandesign@…           
     Type:  enhancement               |      Status:  new                    
 Priority:  Normal                    |   Milestone:                         
Component:  ports                     |     Version:  1.9.2                  
 Keywords:                            |        Port:  group php5extension    
--------------------------------------+-------------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (removed)
  * owner:  macports-tickets@… => ryandesign@…


Comment:

 Do not increase the version of the portgroup.

 The problem with this suggestion is that the user is not meant to modify
 the configuration file the portgroup installs. For example
 php5-eaccelerator's eaccelerator.ini file reads:

 {{{
 ; Do not edit this file; it is automatically generated by MacPorts.
 ; Any changes you make will be lost if you upgrade or uninstall
 php5-eaccelerator.
 ; To configure PHP, edit /opt/local/etc/php5/php.ini.
 extension=eaccelerator.so
 }}}

 Therefore, we do not want to put default settings into that file, if the
 user would need to edit them there, since the changes will not persist.

 So I don't want to put default settings in the extension's ini file,
 unless there is a well-defined way for users to override them by editing
 another file. For example, do we know the order in which all the ini files
 are processed? If we can guarantee that the main php.ini is processed
 after all the extensions' ini files, then the user can customize
 extensions' settings in php.ini, just as we've always recommended, but I
 don't know if that's the case. Or, if we can guarantee that the
 extensions' ini files are processed in, say, alphabetical order, then we
 can tell the user to put their custom extension settings into a file whose
 name comes alphabetically after the extension's ini file.

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


More information about the macports-tickets mailing list