Dr. Werner Fink
WernerFink
Involved Projects and Packages
The xsession program is a session manager. It is normally executed by
your ~/.xinitrc (or ~/.xsession) script and controls your X Window
session. As soon as it is started, xsession launches a window manager
and some applications of your choice. At anytime during your session,
you may switch to another window manager or execute some other
applications from the xsession menus.
Examples may be found under /usr/share/doc/packages/xsession/examples.
`xtexit` sends an request to all clients to shut down. If the
application still needs an user interaction (e.g., if a file should be
saved) this is possible.
If you answer by the affirmative, all applications will be closed. This
method is not fully waterproof, but better than killing each and every
client without being able to interfere.
xterm applications anyway are killed immediately!
If this package is installed, it will be automatically integrated into
the sample user fvwm menu.
The "Printing" project is the development project
for packages which provide the base functionality
of the printing system.
The main intent of the "Printing" project is
to provide the newest kind of base printing software for
upcoming openSUSE and SUSE Linux Enterprise versions
and at the same time with same priority to provide the
same newest base printing software also for as many
released openSUSE and SUSE Linux Enterprise versions
as far as possible with reasonable effort.
Base printing software packages are in particular
print spooler software like CUPS,
printing filters like cups-filters,
printer drivers like HPLIP or Gutenprint,
printer driver related software like Ghostscript,
plain PPD files packages like OpenPrintingPPDs,
and other software which directly
belongs to the base printing system
like special backends for CUPS.
In contrast software which does not directly
belong to the base printing system like
user frontends (e.g. printer setup tools,
printing dialog GUIs, or other printing
related GUIs) or applications with a major
focus on printing (e.g. LaTeX or Scribus)
do usually not belong to the "Printing" project.
Of course only really free software can be
accepted in the "Printing" project.
In particular printer driver software which
is not 100% free software cannot be accepted
regardless how nice it would be when this
or that awkward printer model would work.
We will not risk any legal issue for openSUSE
and SUSE Linux Enterprise and our users and
contributors when software where the legal state
is not clear would be accepted.
An obvious precondition for any software is
that it is by default reasonably secure.
In particular for software that is run as root
(e.g. a setup tool or a special CUPS backend)
a security audit is usually required.
The "Printing" development project may contain
new software or work-in-progress changes of
existing software that might neither be in
a stable state nor fit well into currently
installed systems.
Have this in mind if you think about to install
packages from the "Printing" project into your
currently running system.
Do not use "Factory" if your system is not "Factory".
Use the matching packages for your particular system.
The packages in the "Printing" project are without
any guarantee or warranty and without any support.
As an extreme example, this means if your
complete computer center crashes because
of those packages, it is only your problem.
On the other hand this does not mean that those
packages are known to be terrible broken but
they are not thoroughly tested so that any
unexpected issue can happen.
In the end all software in the "Printing" project
are only applications which means that your system
should not "explode" when you upgrade with packages
from the "Printing" project (provided you use the
matching packages for your particular system).
If a new version does not work it should usually
help to downgrade (and to reconfigure as needed)
to get it working again.
When there are issues with the packages in the
"Printing" project we appreciate issue reports.
Regarding how to report a printing issue see
https://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue
For developers:
In general see
https://en.opensuse.org/Portal:Factory_contribution
and
https://en.opensuse.org/openSUSE:How_to_contribute_to_Factory
In particular regarding how to contribute
to the "Printing" project see
https://en.opensuse.org/openSUSE:How_to_contribute_to_the_Printing_project
If you like to contribute major changes
for a package in the "Printing" project
first and foremost get in contact with the
maintainers of the particular package or
the maintainers of the "Printing" project.
This avoids that you do major work on your own
which might not be accepted by the package
maintainers.
The openSUSE Build Service (OBS) web pages
show maintainers of a particular package and
the maintainers of the "Printing" project.
The RPM changelog shows e-mail addresses of
those who had worked on an installed package:
"rpm -q --changelog package_name"
Lpdfilter is a collection of scripts used for
printing various data with lpr(1) and lpd(8).
An entry for lpdfilter in /etc/printcap
is required (see printcap(5)) to enable
these scripts. This can be done by using
the lprsetup script.
Authors:
--------
Werner Fink
The LPRng software is an enhanced, extended,
and portable implementation of the Berkeley LPR
print spooler functionality. While providing
the same interface and meeting RFC1179 requirements,
the implementation is completely new and provides
support for the following features: lightweight
(no databases needed) lpr, lpc, and lprm programs;
dynamic redirection of print queues; automatic
job holding; highly verbose diagnostics; multiple
printers serving a single queue; and a greatly
improved permission and authorization mechanism.
LPRng provides emulation packages for the SVR4 lp
and lpstat programs, eliminating the need for
another print spooler package. These emulation
packages can be modified according to local
requirements to support vintage printing systems.
Attention: Interoperability with older LPD
implementations requires privileged access
to ports. Therefore all affected client-programs
ship with SUID root privileges.
Authors:
--------
Patrick Powell
A driver for Lexmark printers 7000, 7200,
and 5700. This driver translates PBM
(Portable Bitmap) into the printer protocol.
This is the Publishing project. Its main purpose is to serve as development project for packages around the topic of publishing in the openSUSE:Factory distribution. If you want to participate you can contact us individually. Please report bugs to the respective bugowners as set.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
NOTE: Automatically created during Factory devel project migration by admin.
Texinfo is a documentation system that uses a single source file to
produce both online information and printed output. Using Texinfo, you
can create a printed document with the normal features of a book,
including chapters, sections, cross-references, and indices. From the
same Texinfo source file, you can create a menu-driven, online info
file with nodes, menus, cross-references, and indices using the included
makeinfo tool.
NOTE: Automatically created during Factory devel project migration by admin.
Currently do not use this tree as it has problems!
Build Environment for fetching data from TeX Live servers and creating the appropriate spec files as well as then building with those spec files the TeX Live binary rpms from scratch if possible as well as repacking the TeX Live texmf tar balls into rpms.
WARNING:
Please do not mix upstream TeX Live installation with rpm based TeX Live packages. The dependencies base on rpm data base can not be fulfilled with those of the upstream TeX Live packages.
The script environment for fetching data from the TeX Live Network and creating spec files. The perl script `generate' will read the data base `texlive.tlpdb.xz' from TeX Live and will generate the spec file to the basesystem. This spec file is used in the package `texlive' to e.g. build `texlive-filesystem', the various
collections and scheme packages as well as the binary packages. Also `generate' generates the spec files for most noarch TeX Live package found in `texlive.tlpdb.xz'. With this as a tarball `texlive-specs.tar.xz' and the spec file `texlive-specs.spec' more than 4200 packages will build.
The `generate' requires the package `avfs' from the project `Archiving' as otherwise it is not able to fix various problems like wrong script permissions or wrong she-bang lines.
After installing texlive and the package texlive-latex, find a large selection of documentation for TeX, LaTeX, and various layout styles in /usr/share/texmf/doc.
TeX (pronounced tech) is an interpreter for text formatting and was developed by Donald E. Knuth. It works with control and macro commands on a text file. Working with TeX is similar to typesetting methods. LaTeX is a complex macro package that removes the cryptical TeX interface and does most of the work for the user.
TeX uses special fonts produced by the MetaFont program. Various printer drivers and an X11 viewer are also included in this package. The teTeX package is based on the standard TeX package of Karl Berry, which makes configuration much easier. It is also possible to use PostScript fonts. A real PostScript printer is required, however. If the ghostscript (gs) package is installed, all drivers for printing and viewing can use these fonts. Note, however, that the fonts included in the ghostscript package are not identical to Adobe's PostScript fonts. The copyright prohibids us to include them on the CD.
Besides these features, the programs MakeIndex (for producing indexes) and BibTeX (for literature data processing) exist.
The texlive package includes a full texmf tree, many programs like tex, dvips, etc., shell script configuration, and a big collection of documentations. This package is easily configured by the script texconfig and has multilanguage options.
The basic file system layout for TeX Live installation.