about (config) files created in the post-activate stage
René J.V. Bertin
rjvbertin at gmail.com
Sun Sep 27 01:28:30 PDT 2015
On Saturday September 26 2015 21:02:43 Ryan Schmidt wrote:
>Then in post-activate, if /opt/local/etc/foo.conf does not exist, the port may copy the sample file to that location and advise the user that they may edit that file.
That's not really relevant for my usage case (port:qtchooser) and could actually mean that an inappropriate config file is installed. These config files just summarise what Qt ports are installed currently and where and is not supposed to be user-editable. I'm not even sure there's support for adding comments in them. There's a provision to regenerate them through the port's binary though, and to add configuration profiles ("environments") with a different name and referring to any Qt install you want. So find it preferable to have a few reserved environments that are not supposed to be user-modifiable, and regenerated when the port is reactivated.
It could make sense to detect and warn/abort when a different config exists under the reserved name, requiring the use of `activate -f` ... if that's even possible.
I submitted qtchooser on trac, and uploaded the latest (I think...) version. I don't have the ticket number at hand now, sorry.
>There is currently no provision for MacPorts to later remove files created that way. The request to improve this situation is:
OK, I'll have a look and add my voice if I find I have something to say :)
More information about the macports-dev