Why is RELEASE now included in CONFIG_INSTALLS ?

["Brian McAllister" <mcallister@mit.edu>]

Hello EPICS folks -

I have returned to EPICS work after some time and encountered some
unexpected behavior.

The last version I worked with was 3.14.8.2.  Sometime between that release
and 3.14.12.3, the definition of "CONFIG_INSTALLS" in
base/configure/CONFIG_COMMON was changed to include "RELEASE*".  I say
"sometime" as this change is NOT DOCUMENTED in the release notes.

I was using a directory structure for modules such as Asyn and StreamDevice
where I defined INSTALL_LOCATION as the parent directory of all the module
directory trees so that all the includes/libs/dbds from all the modules
were in one location, simplifying the inclusion of such modules in IOC
applications.  This also allowed me to "make" all the modules at once from
the parent directory.

Now, the standard build system wants to install the RELEASE file from each
module tree into to the top-level "configure" directory, where they
over-write each other.

Before I hack the config files to do what I want, I'd like to understand
the purpose of this change.  There was a reason, right ?

----
Brian McAllister                                   Senior Software Engineer
mcallister@mit.edu                                                Bates Lab
(617) 253-9537                                                Middleton, MA