Chapter 11. Customized programs

97

regarded as deprecated for all packages except the X Window System itself, and those which

use the

imake

program it provides, in which case the packages may transition out of the

/usr

/X11R6/

directory at the maintainer's discretion.

10

Programs that use GNU

autoconf

and

automake

are usually easily configured at compile

time to use

/usr/

instead of

/usr/X11R6/

, and this should be done whenever possible. Con 

figuration files for window managers and display managers should be placed in a subdirectory

of

/etc/X11/

corresponding to the package name due to these programs' tight integration

with the mechanisms of the X Window System. Application level programs should use the

/etc/

directory unless otherwise mandated by policy.

The installation of files into subdirectories of

/usr/X11R6/include/X11/

and

/usr/X11R6

/lib/X11/

is permitted but discouraged; package maintainers should determine if subdirec 

tories of

/usr/lib/

and

/usr/share/

can be used instead. (The use of symbolic links from

the

X11R6

directories to other FHS compliant locations is encouraged if the program is not

easily configured to look elsewhere for its files.)

Packages must not provide or install files into the directories

/usr/bin/X11/

,

/usr

/include/X11/

or

/usr/lib/X11/

. Files within a package should, however, make ref 

erence to these directories, rather than their

X11R6

 named counterparts

/usr/X11R6/bin/

,

/usr/X11R6/include/X11/

and

/usr/X11R6/lib/X11/

, if the resources being referred

to have not been moved to other FHS compliant locations.

11.8.8 The OSF/Motif and OpenMotif libraries

Programs that require the non DFSG compliant OSF/Motif or OpenMotif libraries

11

should be com 

piled against and tested with LessTif (a free re implementation of Motif) instead. If the main 

tainer judges that the program or programs do not work sufficiently well with LessTif to be

distributed and supported, but do so when compiled against Motif, then two versions of the

package should be created; one linked statically against Motif and with

 smotif

appended to

the package name, and one linked dynamically against Motif and with

 dmotif

appended to

the package name.

Both Motif linked versions are dependent upon non DFSG compliant software and thus can 

not be uploaded to the main distribution; if the software is itself DFSG compliant it may be

uploaded to the contrib distribution. While known existing versions of Motif permit unlimited

redistribution of binaries linked against the library (whether statically or dynamically), it is the

package maintainer's responsibility to determine whether this is permitted by the license of

the copy of Motif in their possession.

10

Imake

 using programs are exempt because, as long as they are written correctly, the pathnames they use to

locate resources and install themselves are derived wholly from the X Window System configuration. Thus, in the

event that the X Window System moves to

/usr/X11R7/

,

/usr/X12/

, or just plain

/usr/

, all that is required for

these programs is a recompile against the corresponding X Window System library development packages.

11

OSF/Motif and OpenMotif are collectively referred to as  Motif  in this policy document.