[Asterisk-Dev] moving sounds out of asterisk repository
Tzafrir Cohen
tzafrir.cohen at xorcom.com
Fri Jan 13 02:45:35 MST 2006
On Thu, Jan 12, 2006 at 09:32:41PM -0600, Kevin P. Fleming wrote:
> Russell Bryant wrote:
>
> >2) Modify the Asterisk Makefile to check for the existence of the sounds
> >directory.
>
> I don't see a reason to do it this way. The sounds are very rarely
> changed,
Is there any reason, thus, that the version of asterisk-sounds is
automatically bumped on each release of Asterisk? Could it be bumped
only when there is actually a releasble change? If not: could the
tarball include some sort of changelog?
> so my thinking has been this:
>
> 1) Create a separate version number for the 'base' sounds. Export the
> sounds into a tarball named with that version number and put it on
> ftp.digium.com.
>
> 2) Modify the 'make install' target in the Asterisk makefile to check
> the currently-installed-version tag in /var/lib/asterisk/sounds.
>
> 3) If the installed version is older than the version embedded in the
> Makefile, then download that version's tarball, unpack it and install it.
Note that this breaks badly if you don't have internet connection. Or
install a package to an empty build-root, and are thus forced again and
again to download a bunch of files. Thus this should be made very easy
to remove without too big a patch to the makefile.
>
> 4) For tarballs of Asterisk, the needed version of the sounds will be
> included into the tarball when it gets made.
So will it be in asterisk-sounds or in asterisk? Or both? The base/
directory can be a source of problems if people start to use it
literally (if it is in the asterisk-sounds tarball).
--
Tzafrir Cohen icq#16849755 +972-50-7952406
tzafrir.cohen at xorcom.com http://www.xorcom.com
More information about the asterisk-dev
mailing list