From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 Description of problem: There are currently at least two ways in which ccmbuild upgrades could be made a lot easier for the end user. 1) The ccm-config RPM can run ccm-configure-all.sh in the %post section. This would ensure that all build.xml files are built wit hthe latest template. Perhaps the original build.xml files could be backed up first. 2) The /etc/profile.d/*.sh scripts can get sourced in %post so that any changes to these files are automatically picked up. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. install ccm-config 2. upgrade 3. Additional info:
I've discovered that sourcing scripts during the %post section of an RPM install doesn't help as it happens in a subshell and any environment changes are lost.