[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#548288: marked as done (xserver-xephyr: prefer lowercase commands in /usr/bin)



Your message dated Fri, 25 Sep 2009 13:05:16 +0300
with message-id <87vdj7xrtv.fsf@jondo.cante.net>
and subject line Re: Bug#548288: xserver-xephyr: prefer lowercase commands in /usr/bin
has caused the Debian Bug report #548288,
regarding xserver-xephyr: prefer lowercase commands in /usr/bin
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
548288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548288
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xephyr
Version: 2:1.6.3-1
Severity: minor


It appears that the binary is installed as:

   /usr/bin/Xephyr

SUGGESTION

To launch programs from command line it is a little difficult with
capital letters. After installation, the user searching the command
according to package name, would type "xep" + TAB and can not complete
to name "Xephyr".

If possible, please rename the installed /usr/bin/ command to

   xephyr

See e.g. xbiff(1) xcalc(1) xclock(1) that have "x" in front and use
lowercase letters, althought they are X-window related. Similarly all
the graphical modern commands like konqueror(1) and gnome-*(1)
commands are all in lowercase.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xserver-xephyr depends on:
ii  libaudit0                     1.7.13-1   Dynamic library for security audit
ii  libc6                         2.9-25     GNU C Library: Shared libraries
ii  libdbus-1-3                   1.2.16-2   simple interprocess messaging syst
ii  libdrm2                       2.4.13-1   Userspace interface to kernel DRM 
ii  libfontenc1                   1:1.0.4-3  X11 font encoding library
ii  libgcrypt11                   1.4.4-4    LGPL Crypto library - runtime libr
ii  libgl1-mesa-glx [libgl1]      7.5.1-1    A free implementation of the OpenG
ii  libhal1                       0.5.13-3   Hardware Abstraction Layer - share
ii  libpixman-1-0                 0.14.0-1   pixel-manipulation library for X a
ii  libselinux1                   2.0.85-4   SELinux runtime shared libraries
ii  libx11-6                      2:1.2.2-1  X11 client-side library
ii  libxau6                       1:1.0.4-2  X11 authorisation library
ii  libxdmcp6                     1:1.0.2-3  X11 Display Manager Control Protoc
ii  libxext6                      2:1.0.4-1  X11 miscellaneous extension librar
ii  libxfont1                     1:1.4.0-2  X11 font rasterisation library
ii  libxv1                        2:1.0.4-1  X11 Video extension library
ii  xserver-common                2:1.6.3-1  common files used by various X ser

Versions of packages xserver-xephyr recommends:
ii  libgl1-mesa-dri               7.5.1-1    A free implementation of the OpenG
ii  xbase-clients                 1:7.4+4    miscellaneous X clients - metapack

xserver-xephyr suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Brice Goglin <Brice.Goglin@ens-lyon.org> writes:

>
> Well, the Xserver itself is called Xorg (and there's a "X" wrapper). And
> the other server variants are Xnest, Xfbdev, Xephyr, ... There's even
> Xvnc, ... So we would have to change much more than just Xephyr
> unfortunately. A symlink maybe...

Oh, please excuse; somehow I failed to register "xserver" while looking
at similar problems in other packages.

Closing,
Jari


--- End Message ---

Reply to: