[Bash-completion-devel] vncviewer

Guillaume Rousse Guillaume.Rousse at inria.fr
Wed Mar 4 21:13:32 UTC 2009


Freddy Vulto a écrit :
> On Tue, Mar 3, 2009 at 11:49 AM, Guillaume Rousse
> <Guillaume.Rousse at inria.fr> wrote:
>>> assuming `/usr/bin/vncviewer' is a symlink to `tightvncviewer' on
>>> your machine?
>> No, it is not, that's what I'm trying to explain :) We only have one
>> only 'vncviewer' in the distribution, from the 'tightvnc' package, and
>> it's the actual executable name.
>>
>> I think we should try to find a generic way to handle distributions
>> difference, and that way may eventually be manageable at the packaging
>> level, not mandatorily at runtime.
> 
> Maybe both solutions are needed.  I think the
> runtime-symlink-resolving-solution would address the Debian-alternatives
> system which can happen at runtime.  Are the options below feasible as a
> package-level solution on Mandriva (without waiting for the new
> directory layout)?
> 
> 1.  If the `tightvnc' package would provide its own completion:
> 
> Let the `tightvnc' package install a file
> `$BASH_COMPLETION_DIR/tightvncviewer' to complete `vncviewer'.  This
> would override any default `vncviewer' completion installed by
> bash-completion.
> 
> 
> 2.  If the `tightvnc' package would rely on bash-completion:
> 
> Provided that bash-completion installs `xvnc4viewer' and
> `tightvncviewer' completion as separate files, the `tightvnc' package
> could install a file in $BASH_COMPLETION_DIR containing:
> 
>      . /etc/bash_completion/contrib/tightvncviewer
>      complete -F _tightvncviewer vncviewer
Perfect for me.
-- 
BOFH excuse #176:

vapors from evaporating sticky-note adhesives



More information about the Bash-completion-devel mailing list