A post-install would be great (or I myself can write a script)... it isn't that big of a deal.. I just wanted to see if I was over looking something. Tagging the sound directory for a version would also be good.... but if there is no way (and I do understand the reasoning) then I can just write a simple shell script to copy my files back and keep them safe elsewhere.
On 9/30/05, Kevin P. Fleming <[EMAIL PROTECTED]> wrote: > Matt wrote: > > > I end up with the version of Asterisk I wanted installed, my sound > > files get over written, and my config files stay in place.... =\ > > very odd and slightly frustraighting! > > That is correct. 'make install' installs the standard sound files along > with the binaries; if we did not do that, then when the code had been > changed to required new sound files they would not be present... > > However, we have been working on a simpler method to handle this, where > the sound files directory would be version-tagged, and we wouldn't > overwrite anything unless the new version was needed. This would still > overwrite your files though, if a new version of the sound files was > needed with an Asterisk upgrade. The only solution for that problem is > to version-tag every single sound file, and I don't think it's worth the > hassle for that. > > How about if we add a 'post-install' step in the Makefile, that would > run a local script/program if specified, which could copy your sound > files back into place? > _______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
