[blfs-book] [BLFS Trac] #4421: Issues with dependencies on individual Xorg parts

BLFS Trac trac at linuxfromscratch.org
Fri Dec 6 03:02:12 PST 2013

#4421: Issues with dependencies on individual Xorg parts
 Reporter:  chris@…  |       Owner:  blfs-book@…
     Type:  defect   |      Status:  new
 Priority:  normal   |   Milestone:  current
Component:  BOOK     |     Version:  SVN
 Severity:  normal   |  Resolution:
 Keywords:           |

Comment (by Krejzi):

 From the current svn checkout

 pst/printing/gs.xml:      <xref linkend="x-window-system"/> and
 pst/typesetting/texlive.xml:      <xref linkend="x-window-system"/>,
 pst/scanning/sane.xml:      <xref linkend="x-window-system"/>,

 How would any of these strictly need x-window-system? They might require
 the libraries to build them for some functionality, ie a gui program which
 is only small part of the package, but how would one need x window system
 to print something? to scan something? to write a LaTeX document and
 compile it?

 general/prog/php.xml:    <xref linkend="x-window-system"/>,
 general/genutils/imagemagick.xml:      <xref linkend="x-window-system"/>

 Really? To build php and ImageMagick (and both only use a library to
 provide image functionality - libXpm) I need an entire X Window System.
 Even on my server? :O

 general/graphlib/jasper.xml:    <xref linkend="x-window-system"/>, and
 general/graphlib/imlib2.xml:      <xref linkend="x-window-system"/>,
 general/graphlib/aalib.xml:    <para role="optional"><xref linkend="x

 These are image libraries, they might only expect libraries at build time,
 and might be used in a non-x11 environment (ie, server) while still having
 the functionality. It should be obvious that you need a gui to view the
 image (well, except the ascii art).

 server/mail/exim.xml:      <xref linkend="x-window-system"/>,

 I don't even want to mention this one.

 multimedia/libdriv/libdv.xml:      <xref linkend="x-window-system"/>
 multimedia/libdriv/libao.xml:      <xref linkend="x-window-system"/>,
 multimedia/libdriv/xine-lib.xml:      <xref linkend="x-window-system"/>,
 multimedia/libdriv/sdl.xml:      <xref linkend="x-window-system"/>,
 multimedia/libdriv/libmpeg2.xml:    <para role="optional"><xref linkend="x
 -window-system"/> and
 multimedia/videoutils/ffmpeg.xml:      <xref linkend="x-window-system"/>,

 Multimedia libraries might require entire X to function in some
 conditions, but given that mostly programs of these use x libs, it
 shouldn't list X window system as a dep at all.

 postlfs/security/openssh.xml:      <xref linkend="x-window-system"/>,

 This is a lie. OpenSSH only needs xauth app from xorg applications to set
 up x server remoting.

 networking/textweb/links.xml:    <xref linkend="x-window-system"/></para>
 pst/ps/a2ps.xml:      <xref linkend="x-window-system"/>,
 x/wm/icewm.xml:      <xref linkend="x-window-system"/> and
 x/wm/openbox.xml:      <xref linkend="x-window-system"/> and
 x/wm/fluxbox.xml:    <para role="required"><xref linkend="x-window-
 x/wm/other-wms.xml:  window manager installed by the <xref linkend="x
 general/genutils/rxvt-unicode.xml:      <xref linkend="x-window-system"/>
 general/sysutils/mc.xml:      <xref linkend="x-window-system"/>, and
 multimedia/videoutils/vlc.xml:      <xref linkend="x-window-system"/>,
 postlfs/virtualization/qemu.xml:      <xref linkend="x-window-system"/>
 postlfs/editors/emacs.xml:    <para role="optional"><xref linkend="x
 postlfs/editors/vim.xml:    <para role="recommended"><xref linkend="x

 I have no comment for these.

 As you can see, most of the x-window-system deps are currently "a lie".
 I'd rather suggest that everything depends either on Mesa or Xorg
 Libraries, but with a note on these respective pages that Xorg Server
 might be expected to be running at app runtime.

Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/4421#comment:6>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch

More information about the blfs-book mailing list