Re: [LCFC] templates://xorg/{xserver-xorg.templates,x11-common.templates}
Christian Perrier wrote:
> This is the last call for comments for the review of debconf
> templates for xorg.
Sorry I'm late. Comments and diffs below, revised versions attached.
The x11-common.templates file looks fine.
There's a tiny but definite typo in the control file:
> Package: xlibs-static-dev
...
> This package depends on the individual libraries that used to be contained
> within the package of this name. These libraries used to be static
> libraries, but have since become shared libraries with their own packages
> and can be depended on by themselves. This package is for transitional
> purposes to prevent disruptions during automated package builds, and my be
> safely removed from your system.
Spotted it? Here's the diff:
--- control~ 2007-04-04 21:26:54.000000000 +0100
+++ control 2007-04-04 21:27:16.000000000 +0100
@@ -161,7 +161,7 @@
within the package of this name. These libraries used to be static
libraries, but have since become shared libraries with their own packages
and can be depended on by themselves. This package is for transitional
- purposes to prevent disruptions during automated package builds, and my be
+ purposes to prevent disruptions during automated package builds, and may be
safely removed from your system.
Package: xlibmesa-dri
And the xserver-xorg.templates file contains a single word worth
removing:
> - ddc : support for Data Display Channel, respectively. Allows to query
> the monitor capabilities via the video card;
A lot of Germans (especially) seem to have been taught that
"repectively" is a neat translation of "beziehungsweise" (or
something). It isn't. In the above sentence, the idiomatic
English way of expressing the idea is with the null string.
--- xserver-xorg.templates~ 2007-04-04 21:21:06.000000000 +0100
+++ xserver-xorg.templates 2007-04-04 21:39:56.000000000 +0100
@@ -84,7 +84,7 @@
- dri : support in the X server for DRI (Direct Rendering Infrastructure);
- vbe : support for VESA BIOS Extensions. Allows to query
the monitor capabilities via the video card;
- - ddc : support for Data Display Channel, respectively. Allows to query
+ - ddc : support for Data Display Channel. Allows to query
the monitor capabilities via the video card;
- int10 : real-mode x86 emulator used to softboot secondary VGA cards.
Should be enabled if vbe is enabled;
--
JBR
Ankh kak! (Ancient Egyptian blessing)
# Maintainers, keep this template at the top
# It's the most often used one so better have it translated first
Template: xserver-xorg/config/display/modes
Type: multiselect
Choices: 1920x1440, 1920x1200, 1856x1392, 1792x1344, 1680x1050, 1600x1200, 1440x900, 1400x1050, 1280x1024, 1280x960, 1280x854, 1280x800, 1280x768, 1200x800, 1152x864, 1152x768, 1024x768, 800x600, 640x480
Default: 1024x768, 800x600, 640x480
_Description: Video modes to be used by the X server:
Please keep only the resolutions you would like the X server to use. Removing
all of them is the same as removing none, since in both cases the
X server will attempt to use the highest possible resolution.
Template: xserver-xorg/autodetect_video_card
Type: boolean
Default: true
_Description: Attempt to autodetect video hardware?
You should choose this option if you would like to attempt to autodetect the recommended
X server and driver module for your video card. If the autodetection fails, you
will be asked to specify the desired X server and/or driver module. If
it succeeds, further configuration questions about your video hardware
will be pre-answered.
.
If you would rather select the X server and driver module yourself, do not choose
this option. You will not be asked to select the X server if there is only
one available.
Template: shared/no_known_x-server
Type: note
_Description: No X server known for your video hardware
There is either no video hardware installed on this machine (e.g. serial console
only), or the "discover" program was unable to determine which X server is
appropriate for the video hardware. This could be due to incomplete
information in discover's hardware database, or because your video
hardware is not supported by the available X servers.
Template: shared/multiple_possible_x-servers
Type: note
_Description: Multiple potential default X servers for your hardware
Multiple video cards have been detected, and different X servers are required
to support the various devices. It is thus not possible to automatically
select a default X server.
.
Please configure the device that will serve as
this computer's "primary head"; this is generally the video card and monitor
used for display when the computer is booted up.
.
The configuration process currently only supports single-headed setups;
however, the X server configuration files can be edited later to support a
multi-head configuration.
Template: shared/default-x-server
Type: select
Choices: ${choices}
_Description: Desired default X server:
The X server is the hardware interface of the X Window System. It
communicates with the video display and input devices, providing a foundation for
the chosen Graphical User Interface (GUI).
.
Several X servers may be available; the default is selected via the
/etc/X11/X symbolic link. Some X servers may not work with some particular
graphics hardware.
Template: xserver-xorg/config/write_files_section
Type: boolean
Default: true
_Description: Write default Files section to configuration file?
The Files section of the X server configuration file tells the X server where
to find server modules, the RGB color database, and font files. This option
is recommended to experienced users only. In most cases, it should be enabled.
.
Disable this option if you want to maintain a custom Files section into the
X.Org server configuration file. This may be needed to
remove the reference to the local font server, add a reference to a different
font server, or rearrange the default set of local font paths.
Template: xserver-xorg/config/modules
Type: multiselect
Choices: bitmap, dbe, ddc, dri, extmod, freetype, glx, int10, record, v4l, vbe
Default: bitmap, dbe, ddc, dri, extmod, freetype, glx, int10, record, vbe
_Description: X.Org server modules that should be loaded by default:
This option is recommended to experienced users only. In most
cases, all of these modules should be enabled.
.
- glx : support for OpenGL rendering;
- dri : support in the X server for DRI (Direct Rendering Infrastructure);
- vbe : support for VESA BIOS Extensions. Allows to query
the monitor capabilities via the video card;
- ddc : support for Data Display Channel. Allows to query
the monitor capabilities via the video card;
- int10 : real-mode x86 emulator used to softboot secondary VGA cards.
Should be enabled if vbe is enabled;
- dbe : enables the double-buffering extension in the server.
Useful for animation and video operations;
- extmod: enables many traditional and commonly used extensions, such as
shaped windows, shared memory, video mode switching, DGA, and Xv;
- record: implements the RECORD extension, often used in server testing;
- bitmap: font rasterizer (so are freetype, and type1 modules).
.
For further information about these modules, please consult the X.Org
documentation.
Template: xserver-xorg/multiple_possible_x-drivers
Type: note
_Description: Multiple potential default X.Org server drivers for the hardware
Multiple video cards have been detected, and different X servers are required
to support the various devices. It is thus not possible to automatically
select a default X server.
.
Please configure the device that will serve as
this computer's "primary head"; this is generally the video card and monitor
used for display when the computer is booted up.
.
The configuration process currently only supports single-headed setups;
however, the X server configuration files can be edited later to support a
multi-head configuration.
Template: xserver-xorg/config/device/identifier
Type: string
_Description: Identifier for your video card:
The X server configuration file associates your video card with a name that
you may provide. This is usually the vendor or brand name followed by the
model name, e.g., "Intel i915", "ATI RADEON X800", or "NVIDIA GeForce 6600".
Template: xserver-xorg/config/device/default-identifier
Type: text
_Description: Generic Video Card
Template: xserver-xorg/config/device/driver
Type: select
Choices: ${choices}
_Description: X server driver:
For the X Window System graphical user interface to operate correctly, it is
necessary to select a video card driver for the X server.
.
Drivers are typically named for the video card or chipset manufacturer, or
for a specific model or family of chipsets.
Template: xserver-xorg/config/device/use_fbdev
Type: boolean
_Description: Use kernel framebuffer device interface?
Rather than communicating directly with the video hardware, the X server may
be configured to perform some operations, such as video mode switching, via
the kernel's framebuffer driver.
.
In theory, either approach should work, but in practice, sometimes one does
and the other does not. Enabling this option is the safe bet, but feel free
to turn it off if it appears to cause problems.
Template: xserver-xorg/config/device/bus_id
Type: string
#flag:translate!:4
_Description: Video card's bus identifier:
Users of PowerPC machines, and users of any computer with multiple video
devices, should specify the BusID of the video card in an accepted
bus-specific format.
.
Examples:
.
ISA:1
PCI:0:16:0
SBUS:/iommu@0,10000000/sbus@0,10001000/SUNW,tcx@2,800000
.
For users of multi-head setups, this option will configure only one of the
heads. Further configuration will have to be done manually in the X server
configuration file, /etc/X11/xorg.conf.
.
You may wish to use the "lspci" command to determine the bus location of
your PCI, AGP, or PCI-Express video card.
.
When possible, this question has been pre-answered for you and you should
accept the default unless you know it doesn't work.
Template: xserver-xorg/config/device/bus_id_error
Type: note
_Description: Incorrect format for the bus identifier
Template: xserver-xorg/config/device/video_ram
Type: string
_Description: Amount of memory (kB) to be used by the video card:
Typically, the amount of dedicated memory used by the video card is autodetected
by the X server, but some integrated video chips (such as the Intel i810)
have little or no video memory of their own, and instead borrow main system
memory for their needs.
.
This parameter should usually be left blank and specified only if the video
card lacks RAM, or if the X server has trouble autodetecting the RAM size.
Template: xserver-xorg/config/inputdevice/keyboard/rules
Type: string
_Description: XKB rule set to use:
For the X server to handle the keyboard correctly, an XKB rule set must be
chosen.
.
Users of most keyboards should enter "xorg". Users of Sun Type 4 and Type
5 keyboards, however, should enter "sun".
.
Experienced users can use any defined XKB rule set. If the xkb-data
package has been unpacked, see the /usr/share/X11/xkb/rules directory for
available rule sets.
.
When in doubt, this value should be set to "xorg".
Template: xserver-xorg/config/inputdevice/keyboard/model
Type: string
_Description: Keyboard model:
For the X server to handle the keyboard correctly, a keyboard model must be
entered. Available models depend on which XKB rule set is in use.
.
With the "xorg" rule set:
- pc101: traditional IBM PC/AT style keyboard with 101 keys, common in
the United States. Has no "logo" or "menu" keys;
- pc104: similar to pc101 model, with additional keys, usually engraved
with a "logo" symbol and a "menu" symbol;
- pc102: similar to pc101 and often found in Europe. Includes a "< >" key;
- pc105: similar to pc104 and often found in Europe. Includes a "< >" key;
- macintosh: Macintosh keyboards using the new input layer with Linux
keycodes;
- macintosh_old: Macintosh keyboards not using the new input layer.
With the "sun" rule set:
- type4: Sun Type4 keyboards;
- type5: Sun Type5 keyboards.
.
Laptop keyboards often do not have as many keys as standalone models; laptop
users should select the keyboard model most closely approximated by the
above.
.
Experienced users can use any model defined by the selected XKB rule set. If
the xkb-data package has been unpacked, see the /usr/share/X11/xkb/rules
directory for available rule sets.
.
Users of U.S. English keyboards should generally enter "pc104". Users of
most other keyboards should generally enter "pc105".
Template: xserver-xorg/config/inputdevice/keyboard/layout
Type: string
_Description: Keyboard layout:
For the X server to handle the keyboard correctly, a keyboard layout must be
entered. Available layouts depend on which XKB rule set and keyboard model
were previously selected.
.
Experienced users can use any layout supported by the selected XKB rule set. If
the xkb-data package has been unpacked, see the /usr/share/X11/xkb/rules
directory for available rule sets.
.
Users of U.S. English keyboards should enter "us". Users of keyboards
localized for other countries should generally enter their ISO 3166 country
code. E.g., France uses "fr", and Germany uses "de".
Template: xserver-xorg/config/inputdevice/keyboard/variant
Type: string
_Description: Keyboard variant:
For the X server to handle the keyboard as desired, a keyboard variant
may be entered. Available variants depend on which XKB rule set, model, and
layout were previously selected.
.
Many keyboard layouts support an option to treat "dead" keys such as
non-spacing accent marks and diaereses as normal spacing keys, and if this is
the preferred behavior, enter "nodeadkeys".
.
Experienced users can use any variant supported by the selected XKB layout. If
the xkb-data package has been unpacked, see the /usr/share/X11/xkb/symbols
directory for the file corresponding to your selected layout for available
variants.
.
Users of U.S. English keyboards should generally leave this entry blank.
Template: xserver-xorg/config/inputdevice/keyboard/options
Type: string
_Description: Keyboard options:
For the X server to handle the keyboard as desired, keyboard options may
be entered. Available options depend on which XKB rule set was previously
selected. Not all options will work with every keyboard model and layout.
.
For example, if you wish the Caps Lock key to behave as an additional
Control key, you may enter "ctrl:nocaps"; if you would like to switch the
Caps Lock and left Control keys, you may enter "ctrl:swapcaps".
.
As another example, some people prefer having the Meta keys available on
their keyboard's Alt keys (this is the default), while other people prefer
having the Meta keys on the Windows or "logo" keys instead. If you
prefer to use your Windows or logo keys as Meta keys, you may enter
"altwin:meta_win".
.
You can combine options by separating them with a comma, for instance
"ctrl:nocaps,altwin:meta_win".
.
Experienced users can use any options compatible with the selected XKB model,
layout and variant.
.
When in doubt, this value should be left blank.
Template: xserver-xorg/autodetect_mouse
Type: boolean
Default: true
_Description: Attempt mouse device autodetection?
If a mouse is attached to the computer, autodetection can be attempted;
it may help to move the mouse while detection is attempted (the
gpm program should be stopped if it is used). Plugging a PS/2 or
bus/inport mouse now requires rebooting.
.
Do not choose this option if you wish to select a mouse type manually.
.
If you choose it and autodetection fails, you will be asked this
question again. Autodetection can be attempted as many times as desired. If
it succeeds, further configuration questions about the mouse will be
pre-answered.
Template: xserver-xorg/config/inputdevice/mouse/port
Type: select
Choices: /dev/input/mice, /dev/psaux, /dev/ttyS0, /dev/tts0, /dev/gpmdata
Default: /dev/input/mice
_Description: Mouse port:
For the X Window System graphical user interface to operate correctly,
certain characteristics of the mouse (or other pointing device, such as a
trackball) must be known.
.
It is necessary to determine which port (connection type) is used by the mouse.
Serial ports use D-shaped connectors with 9 or 25 pins (a.k.a. DB-9 or
DB-25); the mouse connector is female (has holes) and the computer connector
is male (has pins). PS/2 ports are small round connectors (DIN) with 6 pins;
the mouse connector is male and the computer side female. You may
alternatively use a USB mouse, a bus/inport (very old) mouse, or be using
the gpm program as a repeater. If you need to attach or remove PS/2 or
bus/inport devices from your computer, please do so with the computer's power
off.
Template: xserver-xorg/config/inputdevice/mouse/protocol
Type: select
Choices: ${choices}
_Description: Mouse protocol:
Template: xserver-xorg/config/inputdevice/mouse/emulate3buttons
Type: boolean
Default: true
_Description: Emulate 3 button mouse?
Most programs in the X Window System expect the mouse to have 3 buttons
(left, right, and middle). Mice with only 2 buttons can emulate the presence
of a middle button by treating simultaneous clicks or drags of the left and
right buttons as middle button events.
.
This option may also be used on mice with 3 or more buttons; the middle
button will continue to work normally.
.
Note that mouse buttons in excess of five (counting a scroll wheel as two
buttons, one each for "up" and "down", and a third if the wheel "clicks") are
not yet supported with this configuration tool.
Template: xserver-xorg/autodetect_monitor
Type: boolean
Default: true
_Description: Attempt monitor autodetection?
Many monitors (including LCD's) and video cards support a communication
protocol that allows the monitor's technical characteristics to be
communicated back to the computer. If the monitor and video card support
this protocol, further configuration questions about the monitor
will be pre-answered.
.
If autodetection fails, you will be asked for information about the monitor.
Template: xserver-xorg/config/monitor/selection-method
Type: select
Choices: ${choices}
_Description: Method for selecting the monitor characteristics:
For the X Window System graphical user interface to operate correctly,
certain characteristics of the monitor must be known.
.
The "simple" option will prompt about the monitor's physical size; this
will set some configuration values appropriate for a typical CRT of the
corresponding size, but may be suboptimal for high-quality CRT's.
.
The "medium" option will present you with a list of resolutions and refresh
rates, such as "800x600 @ 85Hz"; you should choose the best mode you wish to
use (and that you know the monitor is capable of).
.
The "advanced" option will let you specify the monitor's horizontal sync and
vertical refresh tolerances directly.
Template: xserver-xorg/config/monitor/screen-size
Type: select
__Choices: Up to 14 inches (355 mm), 15 inches (380 mm), 17 inches (430 mm), 19-20 inches (480-510 mm), 21 inches (530 mm) or more
Default: 17 inches (430 mm)
_Description: Approximate monitor size:
High-quality CRT's may be able to use the next highest size category.
Template: xserver-xorg/config/monitor/mode-list
Type: select
Choices: 640x480 @ 60Hz, 640x480 @ 72Hz, 800x600 @ 60Hz, 800x600 @ 72Hz, 800x600 @ 85Hz, 832x624 @ 75Hz, 1024x768 @ 60Hz, 1024x768 @ 70Hz, 1024x768 @ 75Hz, 1152x768 @ 54.8Hz, 1152x768 @ 60Hz, 1152x864 @ 75Hz, 1280x960 @ 60Hz, 1280x960 @ 85Hz, 1280x1024 @ 60Hz, 1400x1050 @ 60Hz, 1400x1050 @ 75Hz, 1440x900 @ 100Hz, 1600x1024 @ 60Hz, 1600x1200 @ 60Hz, 1600x1200 @ 75Hz, 1600x1200 @ 85Hz, 1680x1050 @ 75Hz, 1792x1344 @ 60Hz, 1792x1344 @ 75Hz, 1856x1392 @ 60Hz, 1856x1392 @ 75Hz, 1920x1200 @ 60Hz, 1920x1200 @ 75 Hz, 1920x1440 @ 60Hz, 1920x1440 @ 75Hz, 1920x1440 @ 85Hz, 2048x1536 @ 60Hz, 2048x1536 @ 75Hz, 2048x1536 @ 85Hz
Default: 1024x768 @ 60Hz
_Description: Monitor's best video mode:
Choose the "best" resolution and refresh rate the monitor is
capable of. Larger resolutions and refresh rates are better. With a
CRT monitor, it is perfectly acceptable to select a "worse" video mode than
the monitor's best if you wish. Users of LCD displays may also be able to
do this, but only if both the video chipset and the driver support it; if in
doubt, use the video mode recommended by the manufacturer of your LCD.
Template: xserver-xorg/config/monitor/identifier
Type: string
_Description: Identifier for the monitor:
The X server configuration file associates the monitor with a name that you
may provide. This is usually the vendor or brand name followed by the model
name, e.g., "Sony E200" or "Dell E770s".
Template: xserver-xorg/config/monitor/default-identifier
Type: text
_Description: Generic Monitor
Template: xserver-xorg/config/monitor/use_sync_ranges
Type: boolean
_Description: Write monitor sync ranges to the configuration file?
The monitor synchronization ranges should be autodetected by the X server in
most cases, but sometimes it needs hinting. This option is for experienced users,
and should be left at its default.
Template: xserver-xorg/config/monitor/horiz-sync
Type: string
_Description: Monitor's horizontal sync range:
Please enter either a comma-separated list of discrete values (for
fixed-frequency displays), or a pair of values separated by a dash (all
modern CRT's). This information should be available in the monitor's
manual. Values lower than 30 or higher than 130 are extremely rare.
Template: xserver-xorg/config/monitor/vert-refresh
Type: string
_Description: Monitor's vertical refresh range:
Please enter either a comma-separated list of discrete values (for
fixed-frequency displays), or a pair of values separated by a dash (all
modern CRT's). This information should be available in the monitor's
manual. Values lower than 50 or higher than 160 are extremely rare.
Template: xserver-xorg/config/monitor/range_input_error
Type: note
_Description: Incorrect values entered
The valid syntax is a comma-separated list of discrete values, or a pair of
values separated by a dash.
Template: xserver-xorg/config/display/default_depth
Type: select
Choices: 1, 4, 8, 15, 16, 24
Default: 24
_Description: Desired default color depth in bits:
Usually 24-bit color is desirable, but on graphics cards with limited amounts
of framebuffer memory, higher resolutions may be achieved at the expense of
higher color depth. Also, some cards support hardware 3D acceleration only
for certain depths. Consult your video card manual for more information.
.
So-called "32-bit color" is actually 24 bits of color information plus 8
bits of alpha channel or simple zero padding; the X Window System can handle
both. If you want either, select 24 bits.
Template: xserver-xorg/config/null_string_error
Type: note
_Description: Empty value
A null entry is not permitted for this value.
Template: xserver-xorg/config/doublequote_in_string_error
Type: note
_Description: Invalid double-quote characters
Double-quote (") characters are not permitted in the entry value.
Template: xserver-xorg/config/nonnumeric_string_error
Type: note
_Description: Numerical value needed
Characters other than digits are not allowed in the entry.
Template: xserver-xorg/autodetect_keyboard
Type: boolean
Default: false
_Description: Autodetect keyboard layout?
The default keyboard layout selection for the Xorg server will be based on a
combination of the language and the keyboard layout selected in the installer.
.
Choose this option if you want the keyboard layout to be redetected. Do not
choose it if you want to keep your current layout.
Template: shared/fontpath/fontserver
Type: string
Description: Extra fontpath URL
This is an internal (hidden) debconf question. It should not be translated.
Source: xorg
Section: x11
Priority: optional
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Uploaders: David Nusinow <dnusinow@debian.org>, Branden Robinson <branden@debian.org>, Drew Parsons <dparsons@debian.org>, Julien Cristau <jcristau@debian.org>
Standards-Version: 3.7.2.0
Build-Depends: dpkg (>= 1.7.0), po-debconf, debhelper (>= 4.1.16)
Package: x11-common
Architecture: any
Depends: ${misc:Depends}, debianutils (>= 1.13), lsb-base (>= 1.3-9ubuntu2)
Pre-Depends: debconf | debconf-2.0
Conflicts: xfree86-common, xorg-common, xserver-common, x-common,
xserver-xorg (<< 1:7.0.12), xserver-xfree86 (<< 1:7.0),
libxft-dev (<= 2.1.8.2-5), aee (<= 2.2.15b-1), ascd (<= 0.13.2-3),
bibview (<= 2.2-8), fvwm1 (<= 1.24r-46), grace (<= 1:5.1.18-1),
groff (<= 1.18.1.1-7), hfsutils-tcltk (<= 3.2.6-7), login.app (<= 1.2.1-18),
oneko (<= 1.2.sakura.6-1), procmeter (<= 2.5.1-11), propsel (<= 971130-5.3),
regexplorer (<= 0.1.6-12), tkseti (<= 3.06-1), wdm (<= 1.28-1),
wily (<= 0.13.41-6), wmnetselect (<= 0.85-5.5), wmsensors (<= 1.0.4-3.4),
wmtv (<= 0.6.5-15), xbanner (<= 1.31-23), xcolors (<= 1.5a-2),
xcolorsel (<= 1.1a-11), xezmlm (<= 1.0.3-11), xfs-xtt (<= 1:1.4.1.xf430-6),
xgdipc (<= 1.2-0.3), xgmod (<= 3.1-9), xgraph (<= 12.1-3),
xlogmaster (<= 1.6.0-8), xmailbox (<= 2.5-9), xmem (<= 1.20-19),
xnecview (<= 1.34-2), xodo (<= 1.2-9.2), xturqstat (<= 2.2.2sarge1),
xwit (<= 3.4-6), lbxproxy (<< 7.0), proxymngr (<< 7.0), twm (<< 7.0),
xbase-clients (<< 1:7.0), xdm (<= 1:1.0.1-6), xfs (<< 1:1.0), xfwp (<< 7.0),
xutils (<< 1:7.0), xvfb (<< 1:1.0), qcam (<= 0.91-11.1), twlog (<= 1.3-4),
xdmx (<< 1:1.0), bugsx (<= 1.08-8), buici-clock (<= 0.4.5+b1),
ctwm (<= 3.7-2), emelfm (<= 0.9.2-7), fte-xwindow (<= 0.50.0-1.3),
fvwm95 (<= 2.0.43ba-23+b1), gerstensaft (<= 0.2-5.1), gipsc (<= 0.4.3-2),
gradio (<= 1.0.1-6), hanterm-classic (<= 3.1.6.0-4),
hanterm-xf (<= 1:3.3.1p18-9.2), ibp (<= 0.21-4),
isdnutils-xtools (<= 1:3.8.2005-12-06-4), ivtools-bin (<= 1.1.3-5),
kdrill (<= 6.4-2.1), kinput2-canna (<= 3.1-7), kinput2-canna-wnn (<= 3.1-7),
kinput2-wnn (<= 3.1-7), kterm (<= 6.2.0-45), lm-batmon (<= 0.96-3),
lwm (<= 1.2.1-1), mctools-lite (<= 970129-16), mgp (<= 1.11b-6),
olvwm (<= 4.4.3.2p1.4-21), olwm (<= 3.2p1.4-21), pixmap (<= 2.6pl4-14.1),
plotmtv (<= 1.4.4t-8.1), ppxp-x11 (<= 0.2001080415-14), seyon (<= 2.20c-20),
skkinput (<= 1:2.06.4-4), tkdesk (<= 2.0-5), videogen (<= 0.32-1),
vtwm (<= 5.4.7-2), w9wm (<= 0.4.2-4), wmavgload (<= 0.7.0-6.1),
wmcpu (<= 1.3-4.1), wmdate (<= 0.5-7.1), wmnet (<= 1.05-12),
wmscope (<= 3.0-9.1), xautolock (<= 1:2.1-6), xbatt (<= 1.2.1-4),
xbattbar (<= 1.4.2-3.1), xcal (<= 4.1-18.2),
xcalendar-i18n (<= 4.0.0.i18p1-13.1), xcb (<= 2.4-4), xclip (<= 0.08-5),
xclips (<= 6.21-6), xdkcal (<= 0.9d-2.1), xdu (<= 3.0-14),
xengine (<= 1.11-9), xfaces (<= 3.3-25), xfishtank (<= 2.2-23.1),
xfm (<= 1.4.3-8), xinput (<= 1.2-5.2), xipmsg (<= 0.8088-1.1),
xlbiff (<< 4.1-4), xli (<= 1.17.0-21), xlockmore (<= 1:5.21-1),
xlockmore-gl (<= 1:5.21-1), xmeter (<= 1.15-6), xmix (<= 2.1-5),
xmon (<= 1.5.6-1.3), xpostit (<= 3.3.1-8.2), xprint (<= 1:0.1.0.alpha1-13),
xrn (<= 9.02-7.1), xsysinfo (<= 1.7-2), xtel (<= 3.3.0-5.4),
xtoolwait (<= 1.3-6), xtrlock (<= 2.0-11), xview-clients (<= 3.2p1.4-21),
xviewg (<= 3.2p1.4-21), xviewg-dev (<= 3.2p1.4-21), xvkbd (<= 2.6-2.1),
xxkb (<= 1.10-2.1), xzoom (<= 0.3-17), pgaccess (<= 1:0.98.8.20030520-2),
xearth (<= 1.1-10.2), libmotif-dev (<= 2.2.3-1.3),
motif-clients (<= 2.2.3-1.3), xslideshow (<= 3.1-8.1), xtrkcad (<= 3.1.4-1),
pmud (<= 0.10-9), xnest (<< 1:1.0), xterm (<< 208-1), xmh (<= 6.8.2.dfsg.1-4),
beaver (<= 0.2.5-2), lsb-core (<= 3.1-4), yank (<=0.2.1-7.2),
xpmumon (<= 1.3.0), ivtools-dev (<= 1.1.3-5), ppxp (<= 0.2001080415-14),
guitar (<= 0.1.4-11), xftp, xext, xpaste, ghostview, xv (<= 3.10a-26),
xserver-xfree86-dbg, grace6 (<= 5.99.0+final-4), xephem,
opera (<< 9.10-20060616), hamsoft (<< 0.2.3-1), phototk, tkworld
Replaces: xfree86-common, xorg-common, xserver-common, x-common
Description: X Window System (X.Org) infrastructure
x11-common contains the filesystem infrastructure required for further
installation of the X Window System in any configuration; it does not
provide a full installation of clients, servers, libraries, and utilities
required to run the X Window System.
.
A number of terms are used to refer to the X Window System, including "X",
"X Version 11", "X11", "X11R6", and "X11R7". The version of X used in
Debian is derived from the version released by the X.Org Foundation, and
is thus often also referred to as "X.Org". All of the preceding quoted
terms are functionally interchangeable in an Debian system.
Package: xserver-xorg
Architecture: all
Conflicts: xserver-xfree86 (<< 6.8.2.dfsg.1-1), xserver-common
Replaces: xserver-common
Pre-Depends: x11-common (>= 7.0.0-0ubuntu3)
Depends: xserver-xorg-core (>= 2:1.1.1-11), xserver-xorg-video-all | xserver-xorg-video-1.0, xserver-xorg-input-all | xserver-xorg-input, ${misc:Depends}, xkb-data | xkb-data-legacy, xbase-clients
Recommends: xserver-xorg-video-all, xserver-xorg-input-all, laptop-detect, xresprobe, mdetect, discover1 | discover
Description: the X.Org X server
This package depends on the full suite of the server and drivers for the
X.Org X server, as well as providing a configuration infrastructure to manage
xorg.conf. It does not provide the actual server itself, but removing it
is strongly discouraged.
# versioned dependency on xserver-xorg-core needed because xserver-xorg
# contains a symlink to the reportbug script shipped in that package starting
# with 2:1.1.1-11
Package: xserver-xfree86
Architecture: all
Depends: xserver-xorg
Description: transitional package for moving from XFree86 to X.Org
This package smooths upgrades from Debian 3.1 by depending on xserver-xorg.
Package: xserver-xorg-video-all
Architecture: any
Depends: ${F:XServer-Xorg-Video-Depends}
Description: the X.Org X server -- output driver metapackage
This package depends on the full suite of output drivers for the X.Org X server
(Xorg). It does not provide any drivers itself, and may be removed if you wish
to only have certain drivers installed.
Package: xserver-xorg-input-all
Architecture: any
Depends: ${F:XServer-Xorg-Input-Depends}
Description: the X.Org X server -- input driver metapackage
This package depends on the full suite of input drivers for the X.Org X server
(Xorg). It does not provide any drivers itself, and may be removed if you wish
to only have certain drivers installed.
Package: xorg
Architecture: all
Depends: xserver-xorg, libgl1-mesa-glx, libgl1-mesa-dri, libglu1-mesa, xfonts-base (>= 1:1.0.0-1), xfonts-100dpi (>= 1:1.0.0-1), xfonts-75dpi (>= 1:1.0.0-1), xfonts-scalable (>= 1:1.0.0-1), xbase-clients (>= 1:1.0.1-1), xutils (>= 1:1.0.1-1), xkb-data, xterm | x-terminal-emulator, sparc-utils | not+sparc
Provides: x-window-system, x-window-system-core
Description: X.Org X Window System
This metapackage provides the components for a standalone
workstation running the X Window System. It provides the X libraries, an X
server, a set of fonts, and a group of basic X clients and utilities.
.
Higher level metapackages, such as those for desktop environments, can
depend on this package and simplify their dependencies.
.
It should be noted that a package providing x-window-manager should also
be installed to ensure a comfortable X experience.
Package: xorg-dev
Architecture: all
Depends: libdmx-dev, libfontenc-dev, libfs-dev, libice-dev, libsm-dev, libx11-dev, libxau-dev, libxaw7-dev, libxcomposite-dev, libxcursor-dev, libxdamage-dev, libxdmcp-dev, libxevie-dev, libxext-dev, libxfixes-dev, libxfont-dev, libxft-dev, libxi-dev, libxinerama-dev, libxkbfile-dev, libxkbui-dev, libxmu-dev, libxmuu-dev, libxpm-dev, libxrandr-dev, libxrender-dev, libxres-dev, libxss-dev, libxt-dev, libxtrap-dev, libxtst-dev, libxv-dev, libxvmc-dev, libxxf86dga-dev, libxxf86misc-dev, libxxf86vm-dev, x11proto-bigreqs-dev, x11proto-composite-dev, x11proto-core-dev, x11proto-damage-dev, x11proto-dmx-dev, x11proto-evie-dev, x11proto-fixes-dev, x11proto-fontcache-dev, x11proto-fonts-dev, x11proto-gl-dev, x11proto-input-dev, x11proto-kb-dev, x11proto-randr-dev, x11proto-record-dev, x11proto-render-dev, x11proto-resource-dev, x11proto-scrnsaver-dev, x11proto-trap-dev, x11proto-video-dev, x11proto-xcmisc-dev, x11proto-xext-dev, x11proto-xf86bigfont-dev, x11proto-xf86dga-dev, x11proto-xf86dri-dev, x11proto-xf86misc-dev, x11proto-xf86vidmode-dev, x11proto-xinerama-dev, xserver-xorg-dev, xtrans-dev
Description: the X.Org X Window System development libraries
This metapackage provides the development libraries for the X.Org X Window
System.
.
X Window System design documentation, manual pages, library reference
works, unstripped and static versions of the shared libraries, C header
files, and special versions of libraries available only in static form
(with and without PIC symbols included) are supplied by the packages
depended on by this metapackage.
.
Note that this is a convenience package for users and is not a package for
Debian developers to have their package depend on.
Package: xlibs-data
Architecture: all
Section: libs
Depends: xbitmaps, xcursor-themes, libx11-6 (>= 2:1.0.0-2)
Description: transitional package for X11 client data
This package is provided to ease upgrades from Debian 3.1 ("sarge"). It
may be safely removed from your system.
Package: xlibs-static-dev
Architecture: all
Section: libs
Depends: libxfont-dev, libfontenc-dev
Description: transitional metapackage
This package depends on the individual libraries that used to be contained
within the package of this name. These libraries used to be static
libraries, but have since become shared libraries with their own packages
and can be depended on by themselves. This package is for transitional
purposes to prevent disruptions during automated package builds, and may be
safely removed from your system.
Package: xlibmesa-dri
Section: libs
Architecture: all
Depends: libgl1-mesa-dri
Description: transitional package for Debian etch
This package is provided to smooth upgrades from Debian 3.1 ("sarge") to
Debian etch. It may be safely removed from your system.
Package: xlibmesa-gl
Section: libs
Architecture: all
Depends: libgl1-mesa-glx
Description: transitional package for Debian etch
This package is provided to smooth upgrades from Debian 3.1 ("sarge") to
Debian etch. It may be safely removed from your system.
Package: xlibmesa-gl-dev
Section: libdevel
Architecture: all
Depends: libgl1-mesa-dev
Description: transitional package for Debian etch
This package is provided to smooth upgrades from Debian 3.1 ("sarge") to
Debian etch. It may be safely removed from your system.
Package: xlibmesa-glu
Section: libdevel
Architecture: all
Depends: libglu1-mesa
Description: transitional package for Debian etch
This package is provided to smooth upgrades from Debian 3.1 ("sarge") to
Debian etch. It may be safely removed from your system.
Package: libglu1-xorg
Section: libs
Architecture: all
Depends: libglu1-mesa
Description: transitional package for Debian etch
This package is provided to smooth upgrades from Debian 3.1 ("sarge") to
Debian etch. It may be safely removed from your system.
Package: libglu1-xorg-dev
Section: libdevel
Architecture: all
Depends: libglu1-mesa-dev
Description: transitional package for Debian etch
This package is provided to smooth upgrades from Debian 3.1 ("sarge") to
Debian etch. It may be safely removed from your system.
Package: x-window-system
Section: x11
Architecture: all
Depends: xorg
Description: transitional package for Debian etch
This package is provided to smooth upgrades from Debian 3.1 ("sarge") to
Debian etch. It may be safely removed from your system. It depends on the
xorg package which is the new metapackage for installing the X Window
System in Debian.
Package: x-window-system-core
Section: x11
Architecture: all
Depends: xorg
Description: transitional package for Debian etch
This package is provided to smooth upgrades from Debian 3.1 ("sarge") to
Debian etch. It may be safely removed from your system. It depends on the
xorg package which is the new metapackage for installing the X Window
System in Debian.
Reply to: