DOCSLIB.ORG

Red Hat Enterprise Linux 8 Package Manifest

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Red Hat Enterprise Linux 8 Package manifest Package listing for Red Hat Enterprise Linux 8 Last Updated: 2021-04-28 Red Hat Enterprise Linux 8 Package manifest Package listing for Red Hat Enterprise Linux 8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract The Package manifest document provides lists of packages available in Red Hat Enterprise Linux 8.4. Table of Contents Table of Contents .M . A. .K . I.N . .G . .O . P. .E . N. S. .O . U. .R . C. .E . .M . .O . R. .E . .I N. .C . L. .U . S. .I V. .E . 3. .P .R . O. V. .I D. .I N. .G . F. .E .E . D. .B . A. .C . K. O. .N . R. .E .D . .H . .A .T . .D . O. C. .U . M. E. .N . T. .A .T . I.O . .N . .4 . .P .R . E. .F . A. .C . E. 5. .C . H. .A . P. .T .E . R. 1.. .T . H. .E . .B . A. .S . E. O. S. R . E. .P . O. .S . I.T . O. .R . Y. 6. .C . H. .A . P. .T .E . R. 2. T. .H . E. A. .P . P. .S .T . R. .E . A. .M . .R . E. .P . O. .S . I.T . O. .R . Y. .7 . 6. 2.1. APPSTREAM MODULES 283 .C . H. .A . P. .T .E . R. 3. T. .H . E. C. .O . .D . E. .R .E . A. .D . Y. L. .I N. .U . X. B. .U . I. L. D. .E . R. R. .E .P . O. S. .I T. .O . R. .Y . 3. .0 . 5. 3.1. MODULES IN THE CODEREADY LINUX BUILDER REPOSITORY 380 .C . H. .A . P. .T .E . R. 4. .T .H . .E . S. .U . P. .P . L. .E .M . .E . N. .T . A. .R . Y. R . E. .P . O. .S . I.T . O. .R . Y. .3 .8 . 5. .C . H. .A . P. .T .E . R. 5. T. .H . E. H. .I G. H. A. .V . A. .I L. .A . B. .I L. I. T. Y. A. .D . D. -. O. .N . 3. .8 .6 . .C . H. .A . P. .T .E . R. 6. .T .H . .E . R. .E . S. .I L. I. E. N. .T . .S . T. .O . R. .A . G. .E . .A . D. .D . -. O. N. 3. .8 .9 . .A .P . P. .E . N. .D . I. X. A . .R .E . V. .I S. .I O. N. H. .I S. .T . O. .R . Y. .3 .9 . 2. 1 Red Hat Enterprise Linux 8 Package manifest 2 MAKING OPEN SOURCE MORE INCLUSIVE MAKING OPEN SOURCE MORE INCLUSIVE Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message . 3 Red Hat Enterprise Linux 8 Package manifest PROVIDING FEEDBACK ON RED HAT DOCUMENTATION We appreciate your input on our documentation. Please let us know how we could make it better. To do so: For simple comments on specific passages, make sure you are viewing the documentation in the Multi-page HTML format. Highlight the part of text that you want to comment on. Then, click the Add Feedback pop-up that appears below the highlighted text, and follow the displayed instructions. For submitting more complex feedback, create a Bugzilla ticket: 1. Go to the Bugzilla website. 2. As the Component, use Documentation. 3. Fill in the Description field with your suggestion for improvement. Include a link to the relevant part(s) of documentation. 4. Click Submit Bug. 4 PREFACE PREFACE The Package manifest document provides a package listing for Red Hat Enterprise Linux 8.4. Capabilities and limits of RHEL 8 as compared to other versions of the system are available in the Knowledgebase article Red Hat Enterprise Linux technology capabilities and limits . Information regarding the RHEL life cycle is provided in the Red Hat Enterprise Linux Life Cycle document. Detailed changes in each minor release of RHEL are documented in the Release notes. Changes to packages between RHEL 7 and RHEL 8, as well as changes between minor releases of RHEL 8, are listed in Considerations in adopting RHEL 8 . 5 Red Hat Enterprise Linux 8 Package manifest CHAPTER 1. THE BASEOS REPOSITORY Content in the BaseOS repository is intended to provide a core set of the underlying OS functionality that provides the foundation for all installations. This content is available in the RPM format and is subject to support terms similar to those in previous releases of Red Hat Enterprise Linux. For more information, see the Scope of Coverage Details document. The following table lists all the packages in the BaseOS repository along with their license. Package License aajohan-comfortaa-fonts OFL accel-config GPLv2 and LGPLv2 and MIT and CC0 accel-config-libs LGPLv2 and MIT and CC0 acl GPLv2+ acpica-tools GPLv2 adcli LGPLv2+ adcli-doc LGPLv2+ alsa-sof-firmware BSD alsa-sof-firmware-debug BSD arpwatch BSD with advertising at GPLv3+ and GPLv2+ and ISC and MIT and Public Domain atlas BSD atlas-corei2 BSD atlas-corei2-devel BSD atlas-devel BSD atlas-z14 BSD atlas-z14-devel BSD.
Recommended publications
  • Enchant 1300

    Enchant 1300

    ENCHANT 1300 Quick Start Guide For more information, please visit harmankardon.com / 1. WHAT’S IN THE BOX Soundbar Remote Control VOL Power Cables* HDMI Cable AUX cable Optical Cable (4ft, 1200mm) (4ft, 1200mm) (4ft, 1200mm) (4ft, 1200mm) Wall-Mount Brackets Product Information & Wall-mounted guide * Power cable quantities vary by region / 2. PLACE YOUR SOUNDBAR 2a. Place the soundbar on the table TV 2B. Wall mount the soundbar Use tape to stick the wall-mounted paper guide on the wall, push a pen tip through the center to mark the wall-mounted bracket location and remove the paper. 1 TV WALLMOUNTED PAPER GUIDE Using the appropriate anchors, screw the wall mount brackets on the pen mark; Fix the screws at the back of soundbar; then hook the soundbar on the wall. 3 2 x3 4 TV / 3. CONNECT YOUR SOUNDBAR 3a. Connect to your TV Option 1 (Best): HDMI TV HDMI OUT HDMI (ARC) (TV ARC) Option 2: OPTICAL TV OPTICAL OUT OPTICAL IN 3b. Connect to other devices HDMI 1 HDMI 2 HDMI 3 HDMI OUT / 4. POWER YOUR SYSTEM 1 2 3 After the power cord is plugged in, the soundbar will take about 30 seconds to start up and then will enter standby mode, ready to use. / 5. CONNECT TO WI-FI 1 2 3 HK ENCHANT 1300 Once the soundbar connects to the internet for the first time, it may detect a software update to improve performance. This update may take a few minutes to complete. / 6. CONTROL YOUR SOUNDBAR 6a. Top Panel Volume Volume Power Down Up Source Display 6b.
  • Open Source Used in DNAC-Wide Area Bonjour Magneto

    Open Source Used in DNAC-Wide Area Bonjour Magneto

    Open Source Used In DNAC-Wide Area Bonjour Magneto Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-1090203837 Open Source Used In DNAC-Wide Area Bonjour Magneto 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-1090203837 Contents 1.1 javax-activation 1.2.0 1.1.1 Available under license 1.2 metrics-servlets 3.1.0 1.3 mongodb-driver 3.0.4 1.4 jaxb-core 2.3.0 1.4.1 Available under license 1.5 antlr 2.7.6 1.5.1 Available under license 1.6 spring-boot-autoconfigure 1.5.12.RELEASE 1.7 spring-instrument 4.3.19.RELEASE 1.7.1 Available under license 1.8 nimbus-jose-jwt 4.3.1 1.9 javax-inject 1 1.9.1 Available under license 1.10 json-smart 1.3.1 1.11 opentracing-util 0.31.0 1.12 xpp3-min 1.1.3.4.O 1.12.1 Notifications 1.12.2 Available under license 1.13 ojdbc 6 1.14 jax-ws-api 2.3.0 1.15 aspect-j 1.9.2 1.15.1 Available under license 1.16 jetty-util 9.3.27.v20190418 1.17 unirest-java 1.4.5 1.18 jetty-continuation 9.3.27.v20190418 Open Source Used In
  • Source Code Trees in the VALLEY of THE

    Source Code Trees in the VALLEY of THE

    PROGRAMMING GNOME Source code trees IN THE VALLEY OF THE CODETHORSTEN FISCHER So you’ve just like the one in Listing 1. Not too complex, eh? written yet another Unfortunately, creating a Makefile isn’t always the terrific GNOME best solution, as assumptions on programs program. Great! But locations, path names and others things may not be does it, like so many true in all cases, forcing the user to edit the file in other great programs, order to get it to work properly. lack something in terms of ease of installation? Even the Listing 1: A simple Makefile for a GNOME 1: CC=/usr/bin/gcc best and easiest to use programs 2: CFLAGS=`gnome-config —cflags gnome gnomeui` will cause headaches if you have to 3: LDFLAGS=`gnome-config —libs gnome gnomeui` type in lines like this, 4: OBJ=example.o one.o two.o 5: BINARIES=example With the help of gcc -c sourcee.c gnome-config —libs —cflags 6: gnome gnomeui gnomecanvaspixbuf -o sourcee.o 7: all: $(BINARIES) Automake and Autoconf, 8: you can create easily perhaps repeated for each of the files, and maybe 9: example: $(OBJ) with additional compiler flags too, only to then 10: $(CC) $(LDFLAGS) -o $@ $(OBJ) installed source code demand that everything is linked. And at the end, 11: do you then also have to copy the finished binary 12: .c.o: text trees. Read on to 13: $(CC) $(CFLAGS) -c $< manually into the destination directory? Instead, 14: find out how. wouldn’t you rather have an easy, portable and 15: clean: quick installation process? Well, you can – if you 16: rm -rf $(OBJ) $(BINARIES) know how.
  • Dockerdocker

    Dockerdocker

    X86 Exagear Emulation • Android Gaming • Meta Package Installation Year Two Issue #14 Feb 2015 ODROIDMagazine DockerDocker OS Spotlight: Deploying ready-to-use Ubuntu Studio containers for running complex system environments • Interfacing ODROID-C1 with 16 Channel Relay Play with the Weather Board • ODROID-C1 Minimal Install • Device Configuration for Android Development • Remote Desktop using Guacamole What we stand for. We strive to symbolize the edge of technology, future, youth, humanity, and engineering. Our philosophy is based on Developers. And our efforts to keep close relationships with developers around the world. For that, you can always count on having the quality and sophistication that is the hallmark of our products. Simple, modern and distinctive. So you can have the best to accomplish everything you can dream of. We are now shipping the ODROID U3 devices to EU countries! Come and visit our online store to shop! Address: Max-Pollin-Straße 1 85104 Pförring Germany Telephone & Fax phone : +49 (0) 8403 / 920-920 email : [email protected] Our ODROID products can be found at http://bit.ly/1tXPXwe EDITORIAL ow that ODROID Magazine is in its second year, we’ve ex- panded into several social networks in order to make it Neasier for you to ask questions, suggest topics, send article submissions, and be notified whenever the latest issue has been posted. Check out our Google+ page at http://bit.ly/1D7ds9u, our Reddit forum at http://bit. ly/1DyClsP, and our Hardkernel subforum at http://bit.ly/1E66Tm6. If you’ve been following the recent Docker trends, you’ll be excited to find out about some of the pre-built Docker images available for the ODROID, detailed in the second part of our Docker series that began last month.
  • Red Hat Enterprise Linux 6 Developer Guide

    Red Hat Enterprise Linux 6 Developer Guide

    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
  • The Elinks Manual the Elinks Manual Table of Contents Preface

    The Elinks Manual the Elinks Manual Table of Contents Preface

    The ELinks Manual The ELinks Manual Table of Contents Preface.......................................................................................................................................................ix 1. Getting ELinks up and running...........................................................................................................1 1.1. Building and Installing ELinks...................................................................................................1 1.2. Requirements..............................................................................................................................1 1.3. Recommended Libraries and Programs......................................................................................1 1.4. Further reading............................................................................................................................2 1.5. Tips to obtain a very small static elinks binary...........................................................................2 1.6. ECMAScript support?!...............................................................................................................4 1.6.1. Ok, so how to get the ECMAScript support working?...................................................4 1.6.2. The ECMAScript support is buggy! Shall I blame Mozilla people?..............................6 1.6.3. Now, I would still like NJS or a new JS engine from scratch. .....................................6 1.7. Feature configuration file (features.conf).............................................................................7
  • HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014

    HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014

    HTTP cookie - Wikipedia, the free encyclopedia 14/05/2014 Create account Log in Article Talk Read Edit View history Search HTTP cookie From Wikipedia, the free encyclopedia Navigation A cookie, also known as an HTTP cookie, web cookie, or browser HTTP Main page cookie, is a small piece of data sent from a website and stored in a Persistence · Compression · HTTPS · Contents user's web browser while the user is browsing that website. Every time Request methods Featured content the user loads the website, the browser sends the cookie back to the OPTIONS · GET · HEAD · POST · PUT · Current events server to notify the website of the user's previous activity.[1] Cookies DELETE · TRACE · CONNECT · PATCH · Random article Donate to Wikipedia were designed to be a reliable mechanism for websites to remember Header fields Wikimedia Shop stateful information (such as items in a shopping cart) or to record the Cookie · ETag · Location · HTTP referer · DNT user's browsing activity (including clicking particular buttons, logging in, · X-Forwarded-For · Interaction or recording which pages were visited by the user as far back as months Status codes or years ago). 301 Moved Permanently · 302 Found · Help 303 See Other · 403 Forbidden · About Wikipedia Although cookies cannot carry viruses, and cannot install malware on 404 Not Found · [2] Community portal the host computer, tracking cookies and especially third-party v · t · e · Recent changes tracking cookies are commonly used as ways to compile long-term Contact page records of individuals' browsing histories—a potential privacy concern that prompted European[3] and U.S.
  • Avatud Lähtekoodiga Vahendite Kohandamine Microsoft Visual C++ Tarkvaralahenduste Kvaliteedi Analüüsiks Sonarqube Serveris

    Avatud Lähtekoodiga Vahendite Kohandamine Microsoft Visual C++ Tarkvaralahenduste Kvaliteedi Analüüsiks Sonarqube Serveris

    TALLINNA TEHNIKAÜLIKOOL Infotehnoloogia teaduskond Tarkvarateaduse instituut Anton Ašot Roolaid 980774IAPB AVATUD LÄHTEKOODIGA VAHENDITE KOHANDAMINE MICROSOFT VISUAL C++ TARKVARALAHENDUSTE KVALITEEDI ANALÜÜSIKS SONARQUBE SERVERIS Bakalaureusetöö Juhendaja: Juhan-Peep Ernits PhD Tallinn 2019 Autorideklaratsioon Kinnitan, et olen koostanud antud lõputöö iseseisvalt ning seda ei ole kellegi teise poolt varem kaitsmisele esitatud. Kõik töö koostamisel kasutatud teiste autorite tööd, olulised seisukohad, kirjandusallikatest ja mujalt pärinevad andmed on töös viidatud. Autor: Anton Ašot Roolaid 21.05.2019 2 Annotatsioon Käesolevas bakalaureusetöös uuritakse, kuidas on võimalik saavutada suure hulga C++ lähtekoodi kvaliteedi paranemist, kui ettevõttes kasutatakse arenduseks Microsoft Visual Studiot ning koodikaetuse ja staatilise analüüsi ülevaate saamiseks SonarQube serverit (Community Edition). Seejuures SonarSource'i poolt pakutava tasulise SonarCFamily for C/C++ analüsaatori (mille eelduseks on SonarQube serveri Developer Edition) asemel kasutatakse tasuta ja vaba alternatiivi: SonarQube C++ Community pluginat. Analüüsivahenditena eelistatakse avatud lähtekoodiga vabu tarkvaravahendeid. Valituks osutuvad koodi kaetuse analüüsi utiliit OpenCppCoverage ja staatilise analüüsi utiliit Cppcheck. Siiski selgub, et nende utiliitide töö korraldamiseks ja väljundi sobitamiseks SonarQube Scanneri vajadustega tuleb kirjutada paar skripti: üks PowerShellis ja teine Windowsi pakkfailina. Regulaarselt ajastatud analüüside käivitamist tagab QuickBuild,
  • Code Structure by Miklos Vajna Senior Software Engineer at Collabora Productivity 2017-10-11

    Code Structure by Miklos Vajna Senior Software Engineer at Collabora Productivity 2017-10-11

    LibreOffice: Code Structure By Miklos Vajna Senior Software Engineer at Collabora Productivity 2017-10-11 @CollaboraOffice www.CollaboraOffice.com About Miklos ● From Hungary ● More blurb: http://vmiklos.hu/ ● Google Summer of Code 2010/2011 ● Rewrite of the Writer RTF import/export ● Writer developer since 2012 ● Contractor at Collabora since 2013 LibreOffice Conference 2017, Rome | Miklos Vajna 2 / 30 Thanks ● This is an updated version of Michael Meeks’ talk from last year LibreOffice Conference 2017, Rome | Miklos Vajna 3 / 30 Overview ● Code-base overview ● Internal core modules, internal leaf ● Ignoring externals ● Building / packaging: gnumake, scp2 ● Code organisation, git bits ● Keep in mind: this is a 20 years old code-base ● The quality is much better than you would expect after knowing its age ● Things continue to improve over time LibreOffice Conference 2017, Rome | Miklos Vajna 4 / 30 Module overview lowest level Internal non-leaf modules: UNO modules ● Module = toplevel dir ● make dumps-deps-png ● Each module has a README ● e.g. sal/README ● sal: at the bottom ● The system abstraction layer ● tools is an obsolete internal (more or less) duplication of this ● salhelper: wrapper code around sal, also part of the URE LibreOffice Conference 2017, Rome | Miklos Vajna 6 / 30 What is the Uno Runtime Environment (URE)? ● We’ll come to UNO in detail a bit later, but for now: ● Uno Runtime Environment ● See also JRE, Java Runtime Env. ● Belongs to the idea that UNO would be reused somewhere else ● Provides an API/ABI-stable abstraction layer for the suite URE ● Allows writing C++ extensions ● Modify carefully: ● Should not change the ABI ● ABI control via C .map files LibreOffice Conference 2017, Rome | Miklos Vajna 7 / 30 UNO modules ● store: legacy .rdb format ● registry: UNO type regisistry ● unoidl: a .idl file compiler ● cppu: C++ UNO ● Implements basic UNO types and infrastructure for C++, e.g.
  • Reference / Forgerock Identity Cloud 7.2

    Reference / Forgerock Identity Cloud 7.2

    Reference / ForgeRock Identity Cloud 7.2 Latest update: 7.1.0 ForgeRock AS. 201 Mission St., Suite 2900 San Francisco, CA 94105, USA +1 415-599-1100 (US) www.forgerock.com Copyright © 2011-2021 ForgeRock AS. Abstract Reference documentation for ForgeRock® Identity Cloud (Identity Cloud). ForgeRock Identity Cloud provides intelligent authentication, authorization, federation, and single sign-on functionality. This work is licensed under the Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. To view a copy of this license, visit https://creativecommons.org/licenses/by-nc-nd/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. © Copyright 2010–2020 ForgeRock, Inc. All rights reserved. ForgeRock is a registered trademark of ForgeRock, Inc. Other marks appearing herein may be trademarks of their respective owners. This product or document is protected by copyright and distributed under licenses restricting its use, copying, and distribution. No part of this product or document may be reproduced in any form by any means without prior written authorization of ForgeRock and its licensors, if any. DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESSED OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. DejaVu Fonts Bitstream Vera Fonts Copyright Copyright (c) 2003 by Bitstream,
  • Gutenprint 5.0 User's Manual and Release Notes

    Gutenprint 5.0 User's Manual and Release Notes

    Gutenprint 5.0 User's Manual Robert Krawitz March 4, 2007 Gutenprint 5.0 User's Manual Copyright © 2000-2007 Robert Krawitz Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation with no invariant sections, no Front-Cover texts, and no Back-Cover texts. Gutenprint 5.0 is licensed in its entirety under the terms of the GNU General Public License. The CUPS code (in src/cups) is licensed under the terms of the GNU General Public License version 2; the balance of the code is licensed under the terms of the GNU General Public License version 2 or any later version published by the Free Software Foundation. EPSON, ESC/P, and Stylus are registered trademarks of Seiko Epson Corp. ESC/P2 is a trademark of Seiko Epson Corp. All other product names are trademarks and/or registered trademarks of their vendors. 2 Gutenprint 5.0 User's Manual 03/04/2007 Table of Contents 1) Introduction............................................................................................................................................5 1.1) What is Gutenprint?.......................................................................................................................5 1.2) History of Gutenprint.....................................................................................................................5 1.2.1) The early years: Gimp-Print 3.x and 4.0................................................................................5
  • Cups-Filters-Ippusbxd-2018.Pdf

    Cups-Filters-Ippusbxd-2018.Pdf

    cups-filters The non-Apple part of CUPS, maintained by OpenPrinting ippusbxd Standards-conforming support for IPP-over-USB printers Till Kamppeter, OpenPrinting Introduction • cups-filters takes up everything from CUPS which Mac OS X does not need (CUPS 1.6.x) Started end of 2011 by OpenPrinting, overtaking most of CUPS’ filters Switched filters over from PostScript-centric to PDF-centric workflow cups-browsed introduced end of 2012, to introduce browsing of DNS- SD-advertised remote CUPS queues, as CUPS dropped its own broadcasting/browsing • In 7 years of development cups-filters improved a lot Auto-create print queues for IPP network and IPP-over-USB printers, especially driverless printing, not competing with CUPS’ own temporary queues. Mobile printing support: No printer setup tool needed, auto-setup of printers, driverless, cups-browsed auto-shutdown Load-balanced printer clusters, with client-side or server-side queueing of jobs Do legacy CUPS broadcasting/browsing to work with old CUPS on remote machines Filters support Ghostscript, Poppler, and MuPDF as PDF interpreter Filters support all PDLs for driverless printing: PDF, Apple Raster, PWG Raster, and PCLm 2 Role of cups-browsed • CUPS auto-generates its own temporary queues to point to remote IPP/CUPS printers, why continue cups-browsed? Printer clustering (like the former Implicit Classes) . Configurable: Automatic (by equal remote queue names) and manual (by cups-browsed.conf) . Load balancing of clustered queues . Auto-selection of destination printer by job and job settings (planned) Fine-grained filtering of which remote printers are available . Not only servers/IP addresses, but also service names.