asterisk-core-sounds - extra sound files of asterisk

Jonas Smedegaard dr at jones.dk
Sat Mar 20 02:33:59 UTC 2010


Hi Tzafrir (and others),

On Fri, Mar 19, 2010 at 10:10:25PM +0200, Tzafrir Cohen wrote:
>On Sat, Mar 06, 2010 at 11:17:55PM +0100, Jonas Smedegaard wrote:
>> On Mon, Feb 22, 2010 at 11:31:15PM +0200, Tzafrir Cohen wrote:
>>> A follow-up:
>>>
>>> On Mon, Jan 18, 2010 at 05:36:19PM +0200, Tzafrir Cohen wrote:
>>
>>>> Another issue: should those files be installed directly at 
>>>> /usr/share/asterisk/sounds/LANG (e.g.: LANG=en)? or do we want to 
>>>> avoid that, and make it something along the lines of en_digium or 
>>>> en_US ?
>>>
>>> In order to avoid potential collisions, I wanted to use the semy 
>>> standard schema of:
>>>
>>>  ${lang}_${country}_${gender}_${description}.
>>>
>>> Thus the prompts we have are:
>>>
>>> en_US_f_Allison
>>> es_MX_f_Allison [*]
>>> fr_CA_f_June
>>>
>>> This all works fine if LANGUAGE was set. But what if it isn't?
>>
>>> So, do we make /usr/share/sounds/en a symlink? Or more direct symlinks?
>>> This collides with the current asterisk-sounds package that places
>>> files in /usr/share/sounds/en (it is basically the same as
>>> asterisk-core-en-gsm).
>>
>> I'd suggest to...
>>
>>  1. Update package using /usr/share/sounds/$LANG directly
>>  2. use /etc/alternatives, allowing local admin to override default
>
>That does not seem to work. update-alternatives doesn't work well with 
>directories.

What is broken about it?

mplayer seems to use it for default skin.

I believed Java used it too but I notice now that apparently they only 
use it for files.


>And more importantly, we have three "alternatives' pointing to the same 
>target.

I do not understand what issue you describe here: isn't multiple 
alternatives exactly the point of using the elternatives mechanism in 
the first place?!?


>I'll have to manage something complex on my own.

...and reinvent the wheel? :-(


>Seems like a simple and more manual symlink will do:
>
>At postinst:
>
>  If there's no symlink: create a symlink to my package's directory
>
>At postrm:
>
>  If the symlink is dandling: remove it.

In other words, whatever package happen to get installed first wins, 
with no way to programmatically control.  That sound pretty bad! :-(

Anyone who cares about those files will also care about the setup of 
them being deterministic and reliably overridable.


>Beyond that, it is up to the sysadmin to manage things using 'ln -s'

Sysadmins should not mess below /usr/share. Please do not encourage 
that!


Kind regards,

  - Jonas

-- 
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20100320/ebd85c2f/attachment-0001.pgp>


More information about the Pkg-voip-maintainers mailing list