diff --git a/DC-concept-zypper b/DC-concept-zypper deleted file mode 100644 index 666aa63fa..000000000 --- a/DC-concept-zypper +++ /dev/null @@ -1,15 +0,0 @@ -# This file originates from the project https://github.com/openSUSE/doc-kit -# This file can be edited downstream. - -MAIN="concept-zypper.xml" -ROOTID="concept-zypper" - -PROFCONDITION="suse-product" -PROFOS="sles" -#PROFCONDITION="suse-product;beta" -#PROFCONDITION="community-project" - -DRAFT=1 - -STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" -FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" diff --git a/DC-reference-zypper-install b/DC-reference-zypper-install deleted file mode 100644 index d10292e5a..000000000 --- a/DC-reference-zypper-install +++ /dev/null @@ -1,15 +0,0 @@ -# This file originates from the project https://github.com/openSUSE/doc-kit -# This file can be edited downstream. - -MAIN="reference-zypper-install.xml" -ROOTID="reference-zypper-install" - -PROFCONDITION="suse-product" -PROFOS="sles" -#PROFCONDITION="suse-product;beta" -#PROFCONDITION="community-project" - -DRAFT=1 - -STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" -FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" diff --git a/DC-zypper b/DC-zypper new file mode 100644 index 000000000..fad4f4280 --- /dev/null +++ b/DC-zypper @@ -0,0 +1,21 @@ +# This file originates from the project https://github.com/openSUSE/doc-kit +# This file can be edited downstream. + +MAIN="zypper.asm.xml" +# Point to the ID of the of your assembly +ROOTID="zypper" +SRC_DIR="articles" +IMG_SRC_DIR="images" + +## Profiling +PROFOS="PRODUCT" +#PROFCONDITION="PRODUCTNUMBER" +# Use the STRUCTID if there are several structures in one assembly file +#STRUCTID="STRUCTURE-ID" +#PROFARCH="x86_64;zseries;power;aarch64" + +DOCBOOK5_RNG_URI="urn:x-suse:rng:v2:geekodoc-flat" + +STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" +FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse-ns" + diff --git a/articles/zypper.asm.xml b/articles/zypper.asm.xml new file mode 100644 index 000000000..c35ffa45b --- /dev/null +++ b/articles/zypper.asm.xml @@ -0,0 +1,261 @@ + + + + + %entities; +]> + + + + + + + + + + Glue topic to introduce packages and zypper + + + Glue for more information + + + Glue what's next + + + + + &zypper; concept + + + &zypper; subcommands concept + + + + + + Finding software to install + + + &zypper; install reference + + + &zypper; update/patch reference + + + &zypper; remove reference + + + &zypper; repository management reference + + + + Legal Notice + + + GNU Free Documentation License + + + + + + Managing software packages with &zypper; + Software management in &suselinux; &productnumber; + + + + 2025-23-05 + + + + Updated for the initial release of &productname; &productnumber; + + + + 2024-10-10 + + + Added updating and removing packages and repository management. + + + + 2023-11-11 + + + Initial draft version + + + + + + + + + &x86-64; + &power; + + + + &sles; + &sles; + + + Managing software packages with &zypper; + + How to manage software packages with &zypper; + + Manage software with &zypper; + + Systems Management + + + + + Configuration + Installation + + Products & Solutions + + + https://bugzilla.suse.com/enter_bug.cgi + Documentation + SUSE Linux Enterprise Server &productnumber; + + cwickert@suse.com + + + yes + + + + + WHAT? + + + This article explains how to use the &zypper; package manager. + + + + + WHY? + + + Read this article to understand how software is managed in &sle;. + + + + + EFFORT + + + &zypper; is straight forward and very powerful. Understanding the basics only takes + a few minutes of reading. As &zypper; is very comprehensive, learning all options + can take a while. + + + + + GOAL + + + Learn how to manage software and repositories on &sle;. + + + + + REQUIREMENTS + + + + + Your system is up and running. + + + + + A network connection to access the package repositories. + + + + + + + + + + + + + + + + + Concept + + + + + Searching software packages + + + + + Installing packages + + + + + Updating packages + + + + + Removing packages + + + + + Managing package repositories + + + + + Extending &zypper; + + + + + + + + + + + diff --git a/common/generic-entities.ent b/common/generic-entities.ent index c1131e4cf..00121be83 100644 --- a/common/generic-entities.ent +++ b/common/generic-entities.ent @@ -68,10 +68,17 @@ + + + + + + + @@ -216,8 +223,11 @@ use &deng;! --> + + + @@ -233,6 +243,17 @@ use &deng;! --> + + + + + + + + + + + @@ -246,6 +267,8 @@ use &deng;! --> + + @@ -267,6 +290,7 @@ use &deng;! --> + @@ -370,8 +394,9 @@ use &deng;! --> - - + +crmsh"> + @@ -380,7 +405,7 @@ use &deng;! --> - + @@ -454,6 +479,7 @@ use &deng;! --> + @@ -592,6 +618,7 @@ use &deng;! --> + diff --git a/common/legal.xml b/common/legal.xml index 26577a028..ddb10d5f7 100644 --- a/common/legal.xml +++ b/common/legal.xml @@ -13,8 +13,11 @@ Legal Notice - Copyright© 2006– SUSE LLC and contributors. - All rights reserved. + + Copyright© 2006– + + SUSE LLC and contributors. All rights reserved. + Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant @@ -29,7 +32,7 @@ All information found in this book has been compiled with utmost attention to detail. However, - this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors, nor + this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors, nor the translators shall be held liable for possible errors or the consequences thereof. diff --git a/common/license_gfdl1.2.xml b/common/license_gfdl1.2.xml index ac12722de..bd1aa1b3b 100644 --- a/common/license_gfdl1.2.xml +++ b/common/license_gfdl1.2.xml @@ -6,7 +6,6 @@ %entities; ]> - - - - GNU Free Documentation License - - - - Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, - Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and - distribute verbatim copies of this license document, but changing it is not - allowed. - - - + + GNU Free Documentation License + + + Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, + Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this + license document, but changing it is not allowed. + + 0. PREAMBLE - - - The purpose of this License is to make a manual, textbook, or other - functional and useful document "free" in the sense of freedom: to assure - everyone the effective freedom to copy and redistribute it, with or without - modifying it, either commercially or non-commercially. Secondarily, this - License preserves for the author and publisher a way to get credit for their - work, while not being considered responsible for modifications made by - others. - - - - This License is a kind of "copyleft", which means that derivative works of - the document must themselves be free in the same sense. It complements the - GNU General Public License, which is a copyleft license designed for free - software. - - - - We have designed this License to use it for manuals for free software, - because free software needs free documentation: a free program should come - with manuals providing the same freedoms that the software does. But this - License is not limited to software manuals; it can be used for any textual - work, regardless of subject matter or whether it is published as a printed - book. We recommend this License principally for works whose purpose is - instruction or reference. - - - + + The purpose of this License is to make a manual, textbook, or other functional and useful + document "free" in the sense of freedom: to assure everyone the effective freedom to copy and + redistribute it, with or without modifying it, either commercially or non-commercially. + Secondarily, this License preserves for the author and publisher a way to get credit for their + work, while not being considered responsible for modifications made by others. + + + This License is a kind of "copyleft", which means that derivative works of the document must + themselves be free in the same sense. It complements the GNU General Public License, which is a + copyleft license designed for free software. + + + We have designed this License to use it for manuals for free software, because free software + needs free documentation: a free program should come with manuals providing the same freedoms + that the software does. But this License is not limited to software manuals; it can be used for + any textual work, regardless of subject matter or whether it is published as a printed book. We + recommend this License principally for works whose purpose is instruction or reference. + + 1. APPLICABILITY AND DEFINITIONS - - - This License applies to any manual or other work, in any medium, that - contains a notice placed by the copyright holder saying it can be distributed - under the terms of this License. Such a notice grants a world-wide, - royalty-free license, unlimited in duration, to use that work under the - conditions stated herein. The "Document", below, refers to any such manual or - work. Any member of the public is a licensee, and is addressed as "you". You - accept the license if you copy, modify or distribute the work in a way - requiring permission under copyright law. - - - - A "Modified Version" of the Document means any work containing the Document - or a portion of it, either copied verbatim, or with modifications and/or - translated into another language. - - - - A "Secondary Section" is a named appendix or a front-matter section of the - Document that deals exclusively with the relationship of the publishers or - authors of the Document to the Document's overall subject (or to related - matters) and contains nothing that could fall directly within that overall - subject. (Thus, if the Document is in part a textbook of mathematics, a - Secondary Section may not explain any mathematics.) The relationship could be - a matter of historical connection with the subject or with related matters, - or of legal, commercial, philosophical, ethical or political position - regarding them. - - - - The "Invariant Sections" are certain Secondary Sections whose titles are - designated, as being those of Invariant Sections, in the notice that says - that the Document is released under this License. If a section does not fit - the above definition of Secondary then it is not allowed to be designated as - Invariant. The Document may contain zero Invariant Sections. If the Document - does not identify any Invariant Sections then there are none. - - - - The "Cover Texts" are certain short passages of text that are listed, as - Front-Cover Texts or Back-Cover Texts, in the notice that says that the - Document is released under this License. A Front-Cover Text may be at most 5 - words, and a Back-Cover Text may be at most 25 words. - - - - A "Transparent" copy of the Document means a machine-readable copy, - represented in a format whose specification is available to the general - public, that is suitable for revising the document straightforwardly with - generic text editors or (for images composed of pixels) generic paint - programs or (for drawings) some widely available drawing editor, and that is - suitable for input to text formatters or for automatic translation to a - variety of formats suitable for input to text formatters. A copy made in an - otherwise Transparent file format whose markup, or absence of markup, has - been arranged to thwart or discourage subsequent modification by readers is - not Transparent. An image format is not Transparent if used for any - substantial amount of text. A copy that is not "Transparent" is called - "Opaque". - - - - Examples of suitable formats for Transparent copies include plain ASCII - without markup, Texinfo input format, LaTeX input format, SGML or XML using a - publicly available DTD, and standard-conforming simple HTML, PostScript or - PDF designed for human modification. Examples of transparent image formats - include PNG, XCF and JPG. Opaque formats include proprietary formats that can - be read and edited only by proprietary word processors, SGML or XML for which - the DTD and/or processing tools are not generally available, and the - machine-generated HTML, PostScript or PDF produced by some word processors - for output purposes only. - - - - The "Title Page" means, for a printed book, the title page itself, plus such - following pages as are needed to hold, legibly, the material this License - requires to appear in the title page. For works in formats which do not have - any title page as such, "Title Page" means the text near the most prominent - appearance of the work's title, preceding the beginning of the body of the - text. - - - - A section "Entitled XYZ" means a named subunit of the Document whose title - either is precisely XYZ or contains XYZ in parentheses following text that - translates XYZ in another language. (Here XYZ stands for a specific section - name mentioned below, such as "Acknowledgements", "Dedications", - "Endorsements", or "History".) To "Preserve the Title" of such a section when - you modify the Document means that it remains a section "Entitled XYZ" - according to this definition. - - - - The Document may include Warranty Disclaimers next to the notice which states - that this License applies to the Document. These Warranty Disclaimers are - considered to be included by reference in this License, but only as regards - disclaiming warranties: any other implication that these Warranty Disclaimers - may have is void and has no effect on the meaning of this License. - - - + + This License applies to any manual or other work, in any medium, that contains a notice placed + by the copyright holder saying it can be distributed under the terms of this License. Such a + notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under + the conditions stated herein. The "Document", below, refers to any such manual or work. Any + member of the public is a licensee, and is addressed as "you". You accept the license if you + copy, modify or distribute the work in a way requiring permission under copyright law. + + + A "Modified Version" of the Document means any work containing the Document or a portion of it, + either copied verbatim, or with modifications and/or translated into another language. + + + A "Secondary Section" is a named appendix or a front-matter section of the Document that deals + exclusively with the relationship of the publishers or authors of the Document to the + Document's overall subject (or to related matters) and contains nothing that could fall + directly within that overall subject. (Thus, if the Document is in part a textbook of + mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a + matter of historical connection with the subject or with related matters, or of legal, + commercial, philosophical, ethical or political position regarding them. + + + The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being + those of Invariant Sections, in the notice that says that the Document is released under this + License. If a section does not fit the above definition of Secondary then it is not allowed to + be designated as Invariant. The Document may contain zero Invariant Sections. If the Document + does not identify any Invariant Sections then there are none. + + + The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or + Back-Cover Texts, in the notice that says that the Document is released under this License. A + Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. + + + A "Transparent" copy of the Document means a machine-readable copy, represented in a format + whose specification is available to the general public, that is suitable for revising the + document straightforwardly with generic text editors or (for images composed of pixels) generic + paint programs or (for drawings) some widely available drawing editor, and that is suitable for + input to text formatters or for automatic translation to a variety of formats suitable for + input to text formatters. A copy made in an otherwise Transparent file format whose markup, or + absence of markup, has been arranged to thwart or discourage subsequent modification by readers + is not Transparent. An image format is not Transparent if used for any substantial amount of + text. A copy that is not "Transparent" is called "Opaque". + + + Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo + input format, LaTeX input format, SGML or XML using a publicly available DTD, and + standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of + transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats + that can be read and edited only by proprietary word processors, SGML or XML for which the DTD + and/or processing tools are not generally available, and the machine-generated HTML, PostScript + or PDF produced by some word processors for output purposes only. + + + The "Title Page" means, for a printed book, the title page itself, plus such following pages as + are needed to hold, legibly, the material this License requires to appear in the title page. + For works in formats which do not have any title page as such, "Title Page" means the text near + the most prominent appearance of the work's title, preceding the beginning of the body of the + text. + + + A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely + XYZ or contains XYZ in parentheses following text that translates XYZ in another language. + (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", + "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when + you modify the Document means that it remains a section "Entitled XYZ" according to this + definition. + + + The Document may include Warranty Disclaimers next to the notice which states that this License + applies to the Document. These Warranty Disclaimers are considered to be included by reference + in this License, but only as regards disclaiming warranties: any other implication that these + Warranty Disclaimers may have is void and has no effect on the meaning of this License. + + 2. VERBATIM COPYING - - - You may copy and distribute the Document in any medium, either commercially - or non-commercially, provided that this License, the copyright notices, and - the license notice saying this License applies to the Document are reproduced - in all copies, and that you add no other conditions whatsoever to those of - this License. You may not use technical measures to obstruct or control the - reading or further copying of the copies you make or distribute. However, you - may accept compensation in exchange for copies. If you distribute a large - enough number of copies you must also follow the conditions in section 3. - - - - You may also lend copies, under the same conditions stated above, and you may - publicly display copies. - - - + + You may copy and distribute the Document in any medium, either commercially or + non-commercially, provided that this License, the copyright notices, and the license notice + saying this License applies to the Document are reproduced in all copies, and that you add no + other conditions whatsoever to those of this License. You may not use technical measures to + obstruct or control the reading or further copying of the copies you make or distribute. + However, you may accept compensation in exchange for copies. If you distribute a large enough + number of copies you must also follow the conditions in section 3. + + + You may also lend copies, under the same conditions stated above, and you may publicly display + copies. + + 3. COPYING IN QUANTITY - - - If you publish printed copies (or copies in media that commonly have printed - covers) of the Document, numbering more than 100, and the Document's license - notice requires Cover Texts, you must enclose the copies in covers that - carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the - front cover, and Back-Cover Texts on the back cover. Both covers must also - clearly and legibly identify you as the publisher of these copies. The front - cover must present the full title with all words of the title equally - prominent and visible. You may add other material on the covers in addition. - Copying with changes limited to the covers, as long as they preserve the - title of the Document and satisfy these conditions, can be treated as - verbatim copying in other respects. - - - - If the required texts for either cover are too voluminous to fit legibly, you - should put the first ones listed (as many as fit reasonably) on the actual - cover, and continue the rest onto adjacent pages. - - - - If you publish or distribute Opaque copies of the Document numbering more - than 100, you must either include a machine-readable Transparent copy along - with each Opaque copy, or state in or with each Opaque copy a - computer-network location from which the general network-using public has - access to download using public-standard network protocols a complete - Transparent copy of the Document, free of added material. If you use the - latter option, you must take reasonably prudent steps, when you begin - distribution of Opaque copies in quantity, to ensure that this Transparent - copy will remain thus accessible at the stated location until at least one - year after the last time you distribute an Opaque copy (directly or through - your agents or retailers) of that edition to the public. - - - - It is requested, but not required, that you contact the authors of the - Document well before redistributing any large number of copies, to give them - a chance to provide you with an updated version of the Document. - - - + + If you publish printed copies (or copies in media that commonly have printed covers) of the + Document, numbering more than 100, and the Document's license notice requires Cover Texts, you + must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: + Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must + also clearly and legibly identify you as the publisher of these copies. The front cover must + present the full title with all words of the title equally prominent and visible. You may add + other material on the covers in addition. Copying with changes limited to the covers, as long + as they preserve the title of the Document and satisfy these conditions, can be treated as + verbatim copying in other respects. + + + If the required texts for either cover are too voluminous to fit legibly, you should put the + first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto + adjacent pages. + + + If you publish or distribute Opaque copies of the Document numbering more than 100, you must + either include a machine-readable Transparent copy along with each Opaque copy, or state in or + with each Opaque copy a computer-network location from which the general network-using public + has access to download using public-standard network protocols a complete Transparent copy of + the Document, free of added material. If you use the latter option, you must take reasonably + prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this + Transparent copy will remain thus accessible at the stated location until at least one year + after the last time you distribute an Opaque copy (directly or through your agents or + retailers) of that edition to the public. + + + It is requested, but not required, that you contact the authors of the Document well before + redistributing any large number of copies, to give them a chance to provide you with an updated + version of the Document. + + 4. MODIFICATIONS - - - You may copy and distribute a Modified Version of the Document under the - conditions of sections 2 and 3 above, provided that you release the Modified - Version under precisely this License, with the Modified Version filling the - role of the Document, thus licensing distribution and modification of the - Modified Version to whoever possesses a copy of it. In addition, you must do - these things in the Modified Version: - - - - - - Use in the Title Page (and on the covers, if any) a title distinct from - that of the Document, and from those of previous versions (which should, if - there were any, be listed in the History section of the Document). You may - use the same title as a previous version if the original publisher of that - version gives permission. - - - - - List on the Title Page, as authors, one or more persons or entities - responsible for authorship of the modifications in the Modified Version, - together with at least five of the principal authors of the Document (all - of its principal authors, if it has fewer than five), unless they release - you from this requirement. - - - - - State on the Title page the name of the publisher of the Modified Version, - as the publisher. - - - - - Preserve all the copyright notices of the Document. - - - - - Add an appropriate copyright notice for your modifications adjacent to the - other copyright notices. - - - - - Include, immediately after the copyright notices, a license notice giving - the public permission to use the Modified Version under the terms of this - License, in the form shown in the Addendum below. - - - - - Preserve in that license notice the full lists of Invariant Sections and - required Cover Texts given in the Document's license notice. - - - - - Include an unaltered copy of this License. - - - - - Preserve the section Entitled "History", Preserve its Title, and add to it - an item stating at least the title, year, new authors, and publisher of the - Modified Version as given on the Title Page. If there is no section - Entitled "History" in the Document, create one stating the title, year, - authors, and publisher of the Document as given on its Title Page, then add - an item describing the Modified Version as stated in the previous sentence. - - - - - Preserve the network location, if any, given in the Document for public - access to a Transparent copy of the Document, and likewise the network - locations given in the Document for previous versions it was based on. - These may be placed in the "History" section. You may omit a network - location for a work that was published at least four years before the - Document itself, or if the original publisher of the version it refers to - gives permission. - - - - - For any section Entitled "Acknowledgements" or "Dedications", Preserve the - Title of the section, and preserve in the section all the substance and - tone of each of the contributor acknowledgements and/or dedications given - therein. - - - - - Preserve all the Invariant Sections of the Document, unaltered in their - text and in their titles. Section numbers or the equivalent are not - considered part of the section titles. - - - - - Delete any section Entitled "Endorsements". Such a section may not be - included in the Modified Version. - - - - - Do not retitle any existing section to be Entitled "Endorsements" or to - conflict in title with any Invariant Section. - - - - - Preserve any Warranty Disclaimers. - - - - - - If the Modified Version includes new front-matter sections or appendices that - qualify as Secondary Sections and contain no material copied from the - Document, you may at your option designate some or all of these sections as - invariant. To do this, add their titles to the list of Invariant Sections in - the Modified Version's license notice. These titles must be distinct from any - other section titles. - - - - You may add a section Entitled "Endorsements", provided it contains nothing - but endorsements of your Modified Version by various parties--for example, - statements of peer review or that the text has been approved by an - organization as the authoritative definition of a standard. - - - - You may add a passage of up to five words as a Front-Cover Text, and a - passage of up to 25 words as a Back-Cover Text, to the end of the list of - Cover Texts in the Modified Version. Only one passage of Front-Cover Text and - one of Back-Cover Text may be added by (or through arrangements made by) any - one entity. If the Document already includes a cover text for the same cover, - previously added by you or by arrangement made by the same entity you are - acting on behalf of, you may not add another; but you may replace the old - one, on explicit permission from the previous publisher that added the old - one. - - - - The author(s) and publisher(s) of the Document do not by this License give - permission to use their names for publicity for or to assert or imply - endorsement of any Modified Version. - - - + + You may copy and distribute a Modified Version of the Document under the conditions of sections + 2 and 3 above, provided that you release the Modified Version under precisely this License, + with the Modified Version filling the role of the Document, thus licensing distribution and + modification of the Modified Version to whoever possesses a copy of it. In addition, you must + do these things in the Modified Version: + + + + + Use in the Title Page (and on the covers, if any) a title distinct from that of the + Document, and from those of previous versions (which should, if there were any, be listed + in the History section of the Document). You may use the same title as a previous version + if the original publisher of that version gives permission. + + + + + List on the Title Page, as authors, one or more persons or entities responsible for + authorship of the modifications in the Modified Version, together with at least five of the + principal authors of the Document (all of its principal authors, if it has fewer than + five), unless they release you from this requirement. + + + + + State on the Title page the name of the publisher of the Modified Version, as the + publisher. + + + + + Preserve all the copyright notices of the Document. + + + + + Add an appropriate copyright notice for your modifications adjacent to the other copyright + notices. + + + + + Include, immediately after the copyright notices, a license notice giving the public + permission to use the Modified Version under the terms of this License, in the form shown + in the Addendum below. + + + + + Preserve in that license notice the full lists of Invariant Sections and required Cover + Texts given in the Document's license notice. + + + + + Include an unaltered copy of this License. + + + + + Preserve the section Entitled "History", Preserve its Title, and add to it an item stating + at least the title, year, new authors, and publisher of the Modified Version as given on + the Title Page. If there is no section Entitled "History" in the Document, create one + stating the title, year, authors, and publisher of the Document as given on its Title Page, + then add an item describing the Modified Version as stated in the previous sentence. + + + + + Preserve the network location, if any, given in the Document for public access to a + Transparent copy of the Document, and likewise the network locations given in the Document + for previous versions it was based on. These may be placed in the "History" section. You + may omit a network location for a work that was published at least four years before the + Document itself, or if the original publisher of the version it refers to gives permission. + + + + + For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the + section, and preserve in the section all the substance and tone of each of the contributor + acknowledgements and/or dedications given therein. + + + + + Preserve all the Invariant Sections of the Document, unaltered in their text and in their + titles. Section numbers or the equivalent are not considered part of the section titles. + + + + + Delete any section Entitled "Endorsements". Such a section may not be included in the + Modified Version. + + + + + Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title + with any Invariant Section. + + + + + Preserve any Warranty Disclaimers. + + + + + If the Modified Version includes new front-matter sections or appendices that qualify as + Secondary Sections and contain no material copied from the Document, you may at your option + designate some or all of these sections as invariant. To do this, add their titles to the list + of Invariant Sections in the Modified Version's license notice. These titles must be distinct + from any other section titles. + + + You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of + your Modified Version by various parties--for example, statements of peer review or that the + text has been approved by an organization as the authoritative definition of a standard. + + + You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 + words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only + one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through + arrangements made by) any one entity. If the Document already includes a cover text for the + same cover, previously added by you or by arrangement made by the same entity you are acting on + behalf of, you may not add another; but you may replace the old one, on explicit permission + from the previous publisher that added the old one. + + + The author(s) and publisher(s) of the Document do not by this License give permission to use + their names for publicity for or to assert or imply endorsement of any Modified Version. + + 5. COMBINING DOCUMENTS - - - You may combine the Document with other documents released under this - License, under the terms defined in section 4 above for modified versions, - provided that you include in the combination all of the Invariant Sections of - all of the original documents, unmodified, and list them all as Invariant - Sections of your combined work in its license notice, and that you preserve - all their Warranty Disclaimers. - - - - The combined work need only contain one copy of this License, and multiple - identical Invariant Sections may be replaced with a single copy. If there are - multiple Invariant Sections with the same name but different contents, make - the title of each such section unique by adding at the end of it, in - parentheses, the name of the original author or publisher of that section if - known, or else a unique number. Make the same adjustment to the section - titles in the list of Invariant Sections in the license notice of the - combined work. - - - - In the combination, you must combine any sections Entitled "History" in the - various original documents, forming one section Entitled "History"; likewise - combine any sections Entitled "Acknowledgements", and any sections Entitled - "Dedications". You must delete all sections Entitled "Endorsements". - - - + + You may combine the Document with other documents released under this License, under the terms + defined in section 4 above for modified versions, provided that you include in the combination + all of the Invariant Sections of all of the original documents, unmodified, and list them all + as Invariant Sections of your combined work in its license notice, and that you preserve all + their Warranty Disclaimers. + + + The combined work need only contain one copy of this License, and multiple identical Invariant + Sections may be replaced with a single copy. If there are multiple Invariant Sections with the + same name but different contents, make the title of each such section unique by adding at the + end of it, in parentheses, the name of the original author or publisher of that section if + known, or else a unique number. Make the same adjustment to the section titles in the list of + Invariant Sections in the license notice of the combined work. + + + In the combination, you must combine any sections Entitled "History" in the various original + documents, forming one section Entitled "History"; likewise combine any sections Entitled + "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections + Entitled "Endorsements". + + 6. COLLECTIONS OF DOCUMENTS - - - You may make a collection consisting of the Document and other documents - released under this License, and replace the individual copies of this - License in the various documents with a single copy that is included in the - collection, provided that you follow the rules of this License for verbatim - copying of each of the documents in all other respects. - - - - You may extract a single document from such a collection, and distribute it - individually under this License, provided you insert a copy of this License - into the extracted document, and follow this License in all other respects - regarding verbatim copying of that document. - - - + + You may make a collection consisting of the Document and other documents released under this + License, and replace the individual copies of this License in the various documents with a + single copy that is included in the collection, provided that you follow the rules of this + License for verbatim copying of each of the documents in all other respects. + + + You may extract a single document from such a collection, and distribute it individually under + this License, provided you insert a copy of this License into the extracted document, and + follow this License in all other respects regarding verbatim copying of that document. + + 7. AGGREGATION WITH INDEPENDENT WORKS - - - A compilation of the Document or its derivatives with other separate and - independent documents or works, in or on a volume of a storage or - distribution medium, is called an "aggregate" if the copyright resulting from - the compilation is not used to limit the legal rights of the compilation's - users beyond what the individual works permit. When the Document is included - in an aggregate, this License does not apply to the other works in the - aggregate which are not themselves derivative works of the Document. - - - - If the Cover Text requirement of section 3 is applicable to these copies of - the Document, then if the Document is less than one half of the entire - aggregate, the Document's Cover Texts may be placed on covers that bracket - the Document within the aggregate, or the electronic equivalent of covers if - the Document is in electronic form. Otherwise they must appear on printed - covers that bracket the whole aggregate. - - - + + A compilation of the Document or its derivatives with other separate and independent documents + or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if + the copyright resulting from the compilation is not used to limit the legal rights of the + compilation's users beyond what the individual works permit. When the Document is included in + an aggregate, this License does not apply to the other works in the aggregate which are not + themselves derivative works of the Document. + + + If the Cover Text requirement of section 3 is applicable to these copies of the Document, then + if the Document is less than one half of the entire aggregate, the Document's Cover Texts may + be placed on covers that bracket the Document within the aggregate, or the electronic + equivalent of covers if the Document is in electronic form. Otherwise they must appear on + printed covers that bracket the whole aggregate. + + 8. TRANSLATION - - - Translation is considered a kind of modification, so you may distribute - translations of the Document under the terms of section 4. Replacing - Invariant Sections with translations requires special permission from their - copyright holders, but you may include translations of some or all Invariant - Sections in addition to the original versions of these Invariant Sections. - You may include a translation of this License, and all the license notices in - the Document, and any Warranty Disclaimers, provided that you also include - the original English version of this License and the original versions of - those notices and disclaimers. In case of a disagreement between the - translation and the original version of this License or a notice or - disclaimer, the original version will prevail. - - - - If a section in the Document is Entitled "Acknowledgements", "Dedications", - or "History", the requirement (section 4) to Preserve its Title (section 1) - will typically require changing the actual title. - - - + + Translation is considered a kind of modification, so you may distribute translations of the + Document under the terms of section 4. Replacing Invariant Sections with translations requires + special permission from their copyright holders, but you may include translations of some or + all Invariant Sections in addition to the original versions of these Invariant Sections. You + may include a translation of this License, and all the license notices in the Document, and any + Warranty Disclaimers, provided that you also include the original English version of this + License and the original versions of those notices and disclaimers. In case of a disagreement + between the translation and the original version of this License or a notice or disclaimer, the + original version will prevail. + + + If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the + requirement (section 4) to Preserve its Title (section 1) will typically require changing the + actual title. + + 9. TERMINATION - - - You may not copy, modify, sublicense, or distribute the Document except as - expressly provided for under this License. Any other attempt to copy, modify, - sublicense or distribute the Document is void, and will automatically - terminate your rights under this License. However, parties who have received - copies, or rights, from you under this License will not have their licenses - terminated so long as such parties remain in full compliance. - - - + + You may not copy, modify, sublicense, or distribute the Document except as expressly provided + for under this License. Any other attempt to copy, modify, sublicense or distribute the + Document is void, and will automatically terminate your rights under this License. However, + parties who have received copies, or rights, from you under this License will not have their + licenses terminated so long as such parties remain in full compliance. + + 10. FUTURE REVISIONS OF THIS LICENSE - - - The Free Software Foundation may publish new, revised versions of the GNU - Free Documentation License from time to time. Such new versions will be - similar in spirit to the present version, but may differ in detail to address - new problems or concerns. See - . - - - - Each version of the License is given a distinguishing version number. If the - Document specifies that a particular numbered version of this License "or any - later version" applies to it, you have the option of following the terms and - conditions either of that specified version or of any later version that has - been published (not as a draft) by the Free Software Foundation. If the - Document does not specify a version number of this License, you may choose - any version ever published (not as a draft) by the Free Software Foundation. - - - + + The Free Software Foundation may publish new, revised versions of the GNU Free Documentation + License from time to time. Such new versions will be similar in spirit to the present version, + but may differ in detail to address new problems or concerns. See + . + + + Each version of the License is given a distinguishing version number. If the Document specifies + that a particular numbered version of this License "or any later version" applies to it, you + have the option of following the terms and conditions either of that specified version or of + any later version that has been published (not as a draft) by the Free Software Foundation. If + the Document does not specify a version number of this License, you may choose any version ever + published (not as a draft) by the Free Software Foundation. + + ADDENDUM: How to use this License for your documents - Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 @@ -523,24 +419,19 @@ or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. - - - If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, - replace the “with...Texts.” line with this: - - + + If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the + “with...Texts.” line with this: + with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. - - - If you have Invariant Sections without Cover Texts, or some other combination - of the three, merge those two alternatives to suit the situation. - - - - If your document contains nontrivial examples of program code, we recommend - releasing these examples in parallel under your choice of free software - license, such as the GNU General Public License, to permit their use in free - software. - + + If you have Invariant Sections without Cover Texts, or some other combination of the three, + merge those two alternatives to suit the situation. + + + If your document contains nontrivial examples of program code, we recommend releasing these + examples in parallel under your choice of free software license, such as the GNU General Public + License, to permit their use in free software. + diff --git a/common/product-entities.ent b/common/product-entities.ent index 5d9ec7a91..ba47473d7 100644 --- a/common/product-entities.ent +++ b/common/product-entities.ent @@ -5,9 +5,12 @@ -&suseai;&slm;&slem;&sles;&sles4sap;&sleha;"> -&suseaia;&slm;&slema;&slsa;&sles4sapa;&slehaa;"> -1.05.45.56.216.016.016.0"> +&suseai;&slm;&slm;&sles;&sles4sap;&sleha;"> +&slm;&slm;&slsa;&sles4sapa;&slehaa;"> + + + + @@ -19,8 +22,66 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +clone-master-clean-up"> +systemd"> +saptune"> +sapconf"> +tuned"> + + + + + + + + + + + + + + + + + + + +crm(live)configure# "> + + +ARCH-GM-media1.iso"> +ARCH-GM-media1.iso"> diff --git a/concepts/packages.xml b/concepts/packages.xml new file mode 100644 index 000000000..5b0fc7e83 --- /dev/null +++ b/concepts/packages.xml @@ -0,0 +1,135 @@ + + + %entities; +]> + + + + + + + Packages Concept + + + + + + + The following sections describe RPM, a command line tool for managing software. + + + +
+ What is RPM? + + The RPM package manager is a powerful package management system used in &suselinux; and other + Linux distributions. It provides a standardized way to distribute, install, update, and manage + software packages. + + + + + Simplified software management: RPM streamlines the process of installing, updating, and + removing software. + + + + + Dependency management: RPM supports dependencies, preventing conflicts and ensuring + software compatibility. + + + + + Security: RPM uses digital signatures to verify the integrity and authenticity of + packages. + + + + + Flexibility: RPM can handle a wide range of software, from small utilities to complex + applications. + + + + + Consistency: RPM provides a consistent way to manage software across different systems. + + + + + In summary, RPM simplifies software management in &sle; by providing a standardized and + efficient way to package, distribute, and install software. Its dependency management, + security features, and repository support make it a powerful tool for users, system + administrators and packagers. + + + It does however have some limitations: + + + + + It only works locally, means it cannot query or download packages from the internet. + + + + + It ensures that all dependencies of a package are fulfilled, but cannot resolve them and + select the necessary packages. + + + + + This is where &zypper; comes into play. + + +
+ diff --git a/concepts/zypper-subcommands.xml b/concepts/zypper-subcommands.xml new file mode 100644 index 000000000..9091cbdde --- /dev/null +++ b/concepts/zypper-subcommands.xml @@ -0,0 +1,86 @@ + + + + + %entities; +]> + + + + + + + &zypper; subcommands + + + + + + &zypper; can be extended with subcommands. + + + +
+ What are &zypper; subcommands? + + &zypper; subcommands are executables that are stored in the directory + /usr/lib/zypper/commands. If a subcommand is not found in this directory, + &zypper; automatically searches the rest of your $PATH for it. This enables + writing custom local extensions and storing them in userspace. + +
+
+ How do &zypper; subcommands work? + + &zypper; subcommands work like regular zypper commands. The only exception is that executing + subcommands in the &zypper; shell, and using global &zypper; options are not supported. + +
+
+ Using Zypper subcommands + + To list available subcommands, run: + +&prompt.user;zypper subcommand help +<subcommand> [--command-options] [arguments] + +Zypper subcommands are standalone executables that live in the +zypper_execdir ('/usr/lib/zypper/commands'). + +For subcommands zypper provides a wrapper that knows where the +subcommands live, and runs them by passing command-line arguments +to them. + +If a subcommand is not found in the zypper_execdir, the wrapper +will look in the rest of your $PATH for it. Thus, it's possible +to write local zypper extensions that don't live in system space. + +Using zypper global-options together with subcommands, as well as +executing subcommands in 'zypper shell' is currently not supported. + +Available zypper subcommands in '/usr/lib/zypper/commands': + + lifecycle products and packages lifecycle information + + +Zypper subcommands available from elsewhere on your $PATH: + + <none> + + +Type 'zypper help <subcommand>' to get subcommand-specific help if available. + + + View the help screen for a subcommand: + +&prompt.user;zypper help appstream-cache +
+ diff --git a/concepts/zypper.xml b/concepts/zypper.xml new file mode 100644 index 000000000..e8e4db705 --- /dev/null +++ b/concepts/zypper.xml @@ -0,0 +1,207 @@ + + + + + %entities; +]> + + + + + + + &zypper; concept + + + + + + The following sections describe &zypper; a command line tool for managing software. It + works on top of RPM. + + + +
+ What is &zypper;? + + &zypper; is a command-line package manager for installing, updating and removing packages and + managing package repositories. + +
+
+ How does &zypper; work? + + &zypper; works and behaves as a regular command-line tool. It features subcommmands, + arguments, and options that can be used to perform specific tasks. + +
+
+ Benefits of &zypper; + + &zypper; offers several benefits compared to graphical package managers. + + + + + Being a command-line tool, &zypper; is faster in use and light on resources. + + + + + &zypper; actions can be scripted. + + + + + &zypper; can be used on systems that do not have graphical desktop environments. This + makes it suitable for use with servers and remote machines. + + + +
+ +
+ &zypper; package manager + + Zypper is a command-line package management tool specifically designed for &sle; and &osuse;. + It's built on top of the ZYpp library (libzypp), which provides the core + functionalities for package management. + + + &zypper; key concepts + + Repositories + + + &zypper; integrates with repositories, providing a centralized source for software + packages. + + + + + Dependencies + + + &zypper; automatically handles package dependencies, ensuring that required libraries + and software are installed. + + + + + Solver + + + &zypper; incorporates a powerful solver that analyzes dependencies and resolves + conflicts, ensuring a smooth installation process. + + + + + Patches + + + Zypper supports patch management, allowing for the application of updates that address + security issues or bugs without necessarily updating the entire package. + + + + +
+
+ General usage + + The general syntax of &zypper; is: + +zypper [GLOBAL_OPTIONS] SUBCOMMAND [SUBCOMMAND_OPTIONS] [ARGUMENTS] + + The components enclosed in brackets are not required. See zypper help for + a list of general options and all subcommands. To get help for a specific subcommand, type + zypper help SUBCOMMAND. + + + + Zypper subcommands + + + The simplest way to execute &zypper; is to type its name, followed by a command. For + example, to apply all needed patches to the system, use: + +&prompt.sudo;zypper patch + + + + Global options + + + Additionally, you can choose from one or more global options by typing them immediately + before the command. For example, to patch the system without any + user input and applying the default answers instead, use: + +&prompt.sudo;zypper --non-interactive patch + + + + Command-specific options + + + To use options that are specific to a particular command, type them immediately + after the command. + +&prompt.sudo;zypper patch --auto-agree-with-licenses + + In the above example, is used to apply all + needed patches to a system without you being asked to confirm any licenses. Instead, + license will be accepted automatically. + + + + + Arguments + + + Some commands require one or more arguments. For example, when using the command + install, you need to specify one or more packages you want to + install: + +&prompt.sudo;zypper install MozillaFirefox + + Some options also require a single argument. The following command will list all known + patterns: + +&prompt.user;zypper search --type pattern + + + + + You can combine all of the above. For example, the following command will install the + mc and vim packages from the factory + repository while being verbose: + +&prompt.sudo;zypper --verbose install --from factory mc vim + + The option keeps all repositories enabled (for solving any + dependencies) while requesting the package from the specified repository. The option + is an alias for , and you may use either one. + + + Most &zypper; commands have a dry-run option that does a simulation of the + given command. It can be used for test purposes: + +&prompt.sudo;zypper remove --dry-run MozillaFirefox + + &zypper; supports the global + option. You can specify a string with this option, which gets written to &zypper;'s log files + and plug-ins (such as the Btrfs plug-in). It can be used to mark and identify transactions in + log files. + +&prompt.sudo;zypper --userdata STRING patch +
+ diff --git a/glues/zypper-intro.xml b/glues/zypper-intro.xml new file mode 100644 index 000000000..3d726e1a7 --- /dev/null +++ b/glues/zypper-intro.xml @@ -0,0 +1,67 @@ + + + %entities; +]> + + + + + + + Managing software with &zypper; + + + + + + The following sections describe how to manage software with &zypper;. They are arranged in the + sequence of a common workflow, but you can also perform most of them independently, if the + prerequisites are in place. + + + Software in &suselinux; is distributed in packages. + + + + + + Search for software to install + () + + + + + Install software packages + () + + + + + update packages () + + + + + remove packages () + + + + + manage package repositories () + + + + + extent &zypper; () + + + + diff --git a/glues/zypper-more-info.xml b/glues/zypper-more-info.xml new file mode 100644 index 000000000..88071949e --- /dev/null +++ b/glues/zypper-more-info.xml @@ -0,0 +1,22 @@ + + + %entities; +]> + + + For more information + + + + + Add web links to external sources or other SUSE articles. + + diff --git a/glues/zypper-whats-next.xml b/glues/zypper-whats-next.xml new file mode 100644 index 000000000..667a15ea3 --- /dev/null +++ b/glues/zypper-whats-next.xml @@ -0,0 +1,22 @@ + + + %entities; +]> + + What's next? + + + + + + Add list of web links to articles relating to this topic that the user might need. + + diff --git a/references/zypper-install.xml b/references/zypper-install.xml new file mode 100644 index 000000000..c782994b3 --- /dev/null +++ b/references/zypper-install.xml @@ -0,0 +1,119 @@ + + + + + %entities; +]> + + + + + + + &zypper; reference + + + + + + Introductory text + + + +
+ Install packages with &zypper; + + To install a package, run: + +&prompt.sudo;zypper install PACKAGE_NAME + + There are multiple ways to specify the package name: + + + + By exact name + +&prompt.sudo;zypper install MozillaFirefox + + + + By exact name and version number + +&prompt.sudo;zypper install MozillaFirefox-128.11 + + Versions must be + appended to the end of the string and must be preceded by an operator: + < (lesser than), <= (lesser than or equal), + = (equal), >= (greater than or equal), + > (greater than): + + + + + By exact name and repository + +&prompt.sudo;zypper install mozilla:MozillaFirefox + + This is useful of a package is available in more than one repository. In this example, + the MozillaFirefox package from the mozilla + repository is installed. + + + + + By the capability it provides + +&prompt.sudo;zypper install firefox + + In this example, the firefox capability is provided by the + MozillaFirefox package, thus running the command installs this + specific package. + + For more information on the concept of capability, refer to "FIXME". + + + + + By its capability, hardware architecture and version + +&prompt.sudo;zypper install 'firefox.x86_64' + + Install a package by its capability, hardware architecture and version. + +&prompt.sudo;zypper install 'firefox>=128.11' + + You can also combine a hardware architecture and version requirement: + +&prompt.sudo;zypper install 'firefox.x86_64>=128.11' + + + + using wild cards in its name. + +&prompt.sudo;zypper install 'Moz*' + + The example command above installs all packages which names start with Moz. + + + + + Install a package using a local or remote RPM file. + +&prompt.sudo;zypper install /tmp/install/MozillaFirefox.rpm + + zypper install /tmp/install/MozillaFirefox.rpm and zypper + install http://download.&exampledomain;/MozillaFirefox.rpm + + + + +
+ diff --git a/references/zypper-remove.xml b/references/zypper-remove.xml new file mode 100644 index 000000000..170a7b195 --- /dev/null +++ b/references/zypper-remove.xml @@ -0,0 +1,114 @@ + + + + + %entities; +]> + + + + + + + Removing package with &zypper; + + + + + + + Removing packages is as easy as installing them. + + + +
+ Removing packages + + To remove a package, run: + +&prompt.sudo;zypper remove PACKAGE_NAME + + To specify the package name, you can use the same methods as for installation. + (). + + + Note that only the specified package(s) will be removed. Use the option + to also remove packages that were installed as dependencies and that are no longer required: + +&prompt.sudo;zypper remove -u PACKAGE_NAME + +
+
+ Replacing packages + +
+
+ Removing unused packages + + Use zypper packages to check for orphaned and unneeded packages. + + + Orphaned Packages are no longer available in any of the configured package repositories. They + can no longer get updated and become unsupported. + + + For a list of orphaned packages, run: + +&prompt.user;zypper packages --orphaned + + Unneeded packages are dependencies of packages that have been installed either explicitly by + the user or implicitly as part a pattern or product, and that have been removed in the + meantime. They are usually no longer needed and should be removed, too. + + + For a list of unneeded packages, run: + +&prompt.user;zypper packages --unneeded + + + To avoid unneeded packages, use zypper rm with the + option or &yast; with + OptionsClean up when deleting packages + enabled. + + + + You can combine both lists into one: + +&prompt.user;zypper packages --orphaned --unneeded + + Use these lists to determine which packages are still needed and which can be safely removed. + + + Do not remove packages you need + + If packages are renamed or removed from a pattern or product, zypper may + no longer consider them explicitly installed and mark them as unneeded, even though they + are still crucial for your installation. + + + Carefully review the list of packages you are removing. + + + + To remove all orphaned and unneeded packages with a single command, run: + +&prompt.sudo;zypper rm $(zypper --no-refresh packages --orphaned --unneeded | gawk '{print $5}' | tail -n +5) + + Exclude a single package or pattern from being uninstalled: + +&prompt.sudo;zypper rm $(zypper --no-refresh packages --orphaned --unneeded | gawk '{print $5}' | tail -n +5 | grep -v PACKAGE_TO_EXCLUDE) + + Exclude multiple packages defined in a text file, separated by a newline: + +&prompt.sudo;zypper rm $(zypper --no-refresh packages --orphaned --unneeded | gawk '{print $5}' | tail -n +5 | grep -v -f /PACKAGES/TO/KEEP.txt) +
+ diff --git a/references/zypper-repos.xml b/references/zypper-repos.xml new file mode 100644 index 000000000..e1e7a9dd9 --- /dev/null +++ b/references/zypper-repos.xml @@ -0,0 +1,140 @@ + + + + + %entities; +]> + + + + + + + &zypper; reference + + + + + + Introductory text + + + +
+ Managing repositories with Zypper + + All installation or patch commands of Zypper rely on a list of known repositories. To list + all repositories known to the system, use the command: + +&prompt.user;zypper repos + + The result will look similar to the following output: + + + Zypper—list of known repositories +&prompt.user;zypper repos +# | Alias | Name | Enabled | GPG Check | Refresh +--+-----------------------------------------------+------------------------------+---------+-----------+-------- +1 | SLES_16.0_x86_64:SLE-Product-SLES-16.0 | SLE-Product-SLES-16.0 | Yes | (r ) Yes | Yes +2 | SLES_16.0_x86_64:SLE-Product-SLES-16.0-Debug | SLE-Product-SLES-16.0-Debug | No | ---- | ---- +3 | SLES_16.0_x86_64:SLE-Product-SLES-16.0-Source | SLE-Product-SLES-16.0-Source | No | ---- | ---- + + + When specifying repositories in various commands, an alias, URI or repository number from the + zypper repos command output can be used. A repository alias is a short + version of the repository name for use in repository handling commands. Note that the + repository numbers can change after modifying the list of repositories. The alias will never + change by itself. + + + By default, details such as the URI or the priority of the repository are not displayed. Use + the following command to list all details: + +&prompt.user;zypper repos -d +
+ Adding repositories + + To add a repository, run + +&prompt.sudo;zypper addrepo URI ALIAS + + URI can either be an Internet repository, a network resource, a + directory or a CD or DVD (see + for details). The + ALIAS is a shorthand and unique identifier of the repository. + You can freely choose it, with the only exception that it needs to be unique. Zypper will + issue a warning if you specify an alias that is already in use. + +
+
+ Refreshing repositories + + zypper enables you to fetch changes in packages from configured + repositories. To fetch the changes, run: + +&prompt.sudo;zypper refresh + + Default behavior of <command>zypper</command> + + By default, some commands perform refresh automatically, so you do not + need to run the command explicitly. + + + + The refresh command enables you to view changes also in disabled + repositories, by using the --plus-content option: + +&prompt.sudo;zypper --plus-content refresh + + This option fetches changes in repositories, but keeps the disabled repositories in the + same state—disabled. + +
+
+ Removing repositories + + To remove a repository from the list, use the command zypper removerepo + together with the alias or number of the repository you want to delete. For example, to + remove the repository SLEHA-12-GEO from + , use one of the following commands: + +&prompt.sudo;zypper removerepo 1 +&prompt.sudo;zypper removerepo "SLEHA-12-GEO" +
+
+ Modifying repositories + + Enable or disable repositories with zypper modifyrepo. You can also + alter the repository's properties (such as refreshing behavior, name or priority) with this + command. The following command will enable the repository named updates, + turn on auto-refresh and set its priority to 20: + +&prompt.sudo;zypper modifyrepo -er -p 20 'updates' + + Modifying repositories is not limited to a single repository—you can also operate on + groups: + + : all repositories: local repositories: remote repositories: repositories + of a certain type (where TYPE can be one of the + following: http, https, ftp, + cd, dvd, dir, file, + cifs, smb, nfs, hd, + iso) + + + To rename a repository alias, use the renamerepo command. The following + example changes the alias from Mozilla Firefox to + firefox: + +&prompt.sudo;zypper renamerepo 'Mozilla Firefox' firefox +
+
+ diff --git a/references/zypper-search.xml b/references/zypper-search.xml new file mode 100644 index 000000000..743a5b559 --- /dev/null +++ b/references/zypper-search.xml @@ -0,0 +1,169 @@ + + + + + %entities; +]> + + + + + + + Searching software packages with &zypper; + + + + + + Introductory text + + + +
+ Introduction + + A paragraph of text. + +
+
+ Querying repositories and packages with Zypper + + Zypper offers various methods to query repositories or packages. To get lists of all + products, patterns, packages or patches available, use the following commands: + +&prompt.user;zypper products +&prompt.user;zypper patterns +&prompt.user;zypper packages +&prompt.user;zypper patches + + To query all repositories for certain packages, use search. To get + information regarding particular packages, use the info command. + +
+ Searching for software + + The zypper search command works on package names, or, optionally, on + package summaries and descriptions. Strings wrapped in / are interpreted + as regular expressions. By default, the search is not case-sensitive. + + + + Simple search for a package name containing fire + +&prompt.user;zypper search "fire" + + + + Simple search for the exact package MozillaFirefox + +&prompt.user;zypper search --match-exact "MozillaFirefox" + + + + Also search in package descriptions and summaries + +&prompt.user;zypper search -d fire + + + + Only display packages not already installed + +&prompt.user;zypper search -u fire + + + + Display packages containing the string fir not followed be e + +&prompt.user;zypper se "/fir[^e]/" + + + +
+
+ Searching for packages across all &slea; modules + + To search for packages both within and outside of currently enabled repositories, use the + search-packages subcommand. This command contacts the &scc; and searches + all modules for matching packages, for example: + +&prompt.user;zypper search-packages package1 package2 + + zypper search-packages provides the following options: + + + + + Search for an exact match of your search string: , + + + + + + Group the results by module (default: group by package): + + + + + + Display more detailed information about packages: , + + + + + + Output search results in XML: + + + +
+
+ Searching for specific capability + + To search for packages which provide a special capability, use the command + what-provides. For example, if you want to know which package provides + the Perl module SVN::Core, use the following command: + +&prompt.user;zypper what-provides 'perl(SVN::Core)' + + Command 'what-provides' is replaced by 'search --provides --match-exact'. + See 'help search' for all available options. + + + Unlike rpm -q --whatprovides, which can only query the local RPM database + of installed packages, zypper what-provides will tell you about + providers of the capability from any repository, not only those that are installed. + +
+
+ Showing package information + + To query single packages, use info with an exact package name as an + argument. This displays detailed information about a package. In case the package name does + not match any package name from repositories, the command outputs detailed information for + non-package matches. If you request a specific type (by using the -t + option) and the type does not exist, the command outputs other available matches but + without detailed information. + + + If you specify a source package, the command displays binary packages built from the source + package. If you specify a binary package, the command outputs the source packages used to + build the binary package. + + + To also show what is required/recommended by the package, use the options + and : + +&prompt.user;zypper info --requires MozillaFirefox +
+
+ diff --git a/references/zypper-update.xml b/references/zypper-update.xml new file mode 100644 index 000000000..24056c477 --- /dev/null +++ b/references/zypper-update.xml @@ -0,0 +1,363 @@ + + + + + %entities; +]> + + + + + + + Updating software with &zypper; + + + + + + + Introductory text + + + +
+ Updating software with &zypper; + + There are two different ways to update software with &zypper;: by installing patches or by + installing a new version of a package. + +
+ Installing all needed patches + + Patching &sle; is the most reliable way to install new versions of + installed packages. It guarantees that all required packages with correct versions are + installed and ensures that package versions considered as conflicting + are omitted. + + + To install all officially released patches that apply to your system, run: + +&prompt.sudo;zypper patch + + All patches available from repositories configured on your computer are checked for their + relevance to your installation. If they are relevant (and not classified as + optional or feature), they are installed immediately. + If zypper patch succeeds, it is guaranteed that no vulnerable version + package is installed unless you confirm the exception. Note that the + official update repository is only available after registering your &productname; + installation. + + + If a patch that is about to be installed includes changes that require a system reboot, you + will be warned before. + + + The plain zypper patch command does not apply patches from third party + repositories. To update also the third party repositories, use the + with-update command option as follows: + +&prompt.sudo;zypper patch --with-update + + To install also optional patches, use: + +&prompt.sudo;zypper patch --with-optional + + The structure here is a bit unfortunate: We explain how to use the + --cve/--bugzilla options in more detail below ("Listing Patches"). + However, the first bit people get is the very brief intro immediately below. + Not sure whether to replicate all the information from "Listing Patches" + here. + - sknorr, 2016-04-25 + + + To install all patches relating to a specific Bugzilla issue, use: + +&prompt.sudo;zypper patch --bugzilla=NUMBER + + To install all patches relating to a specific CVE database entry, use: + +&prompt.sudo;zypper patch --cve=NUMBER + + For example, to install a security patch with the CVE number + CVE-2010-2713, execute: + +&prompt.sudo;zypper patch --cve=CVE-2010-2713 + + To install only patches which affect Zypper and the package management itself, use: + +&prompt.sudo;zypper patch --updatestack-only + + Bear in mind that other command options that would also update other repositories will be + dropped if you use the updatestack-only command option. + +
+
+ Listing patches + + To find out whether patches are available, Zypper allows viewing the following information: + + + + Number of needed patches + + + To list the number of needed patches (patches that apply to your system but are not + yet installed), use patch-check: + +&prompt.user;zypper patch-check + Loading repository data... + Reading installed packages... + 5 patches needed (1 security patch) + + This command can be combined with the option to + list only the patches which affect Zypper and the package management itself. + + + + + List of needed patches + + + To list all needed patches (patches that apply to your system but are not yet + installed), use zypper list-patches. + + + + + List of all patches + + + To list all patches available for &productname;, regardless of whether they are + already installed or apply to your installation, use zypper + patches. + + + + + + It is also possible to list and install patches relevant to specific issues. To list + specific patches, use the zypper list-patches command with the following + options: + + + + By Bugzilla issues + + + To list all needed patches that relate to Bugzilla issues, use the option + . + + + To list patches for a specific bug, you can also specify a bug number: + . To search for patches + relating to multiple Bugzilla issues, add commas between the bug numbers, for + example: + +&prompt.user;zypper list-patches --bugzilla=972197,956917 + + + + By CVE number + + + To list all needed patches that relate to an entry in the CVE database (Common + Vulnerabilities and Exposures), use the option . + + + To list patches for a specific CVE database entry, you can also specify a CVE number: + . To search for patches + relating to multiple CVE database entries, add commas between the CVE numbers, for + example: + +&prompt.user;zypper list-patches --cve=CVE-2016-2315,CVE-2016-2324 + + + + List retracted patches + + + In the &sle; 15 codestream, some patches are automatically retracted. + Maintenance updates are carefully tested, because there is a risk that an update + contains a new bug. If an update proves to contain a bug, a new update (with a higher + version number) is issued to revert the buggy update, and the buggy update is blocked + from being installed again. You can list retracted patches with + zypper: + +&prompt.user;zypper lp --all |grep retracted + SLE-Module-Basesystem15-SP3-Updates | SUSE-SLE-Module-Basesystem-15-SP3-2021-1965 + | recommended | important | --- | retracted | Recommended update for multipath-tools + SLE-Module-Basesystem15-SP3-Updates | SUSE-SLE-Module-Basesystem-15-SP3-2021-2689 + | security | important | --- | retracted | Security update for cpio + SLE-Module-Basesystem15-SP3-Updates | SUSE-SLE-Module-Basesystem-15-SP3-2021-3655 + | security | important | reboot | retracted | Security update for the Linux Kernel + + See complete information on a retracted (or any) patch: + +&prompt.user;zypper patch-info SUSE-SLE-Product-SLES-15-2021-2689 + Loading repository data... + Reading installed packages... + + Information for patch SUSE-SLE-Product-SLES-15-2021-2689: + --------------------------------------------------------- + Repository : SLE-Product-SLES15-LTSS-Updates + Name : SUSE-SLE-Product-SLES-15-2021-2689 + Version : 1 + Arch : noarch + Vendor : maint-coord@suse.de + Status : retracted + Category : security + Severity : important + Created On : Mon 16 Aug 2021 03:44:00 AM PDT + Interactive : --- + Summary : Security update for cpio + Description : + This update for cpio fixes the following issues: + + It was possible to trigger Remote code execution due to a integer overflow + (CVE-2021-38185, bsc#1189206) + + UPDATE: + This update was buggy and could lead to hangs, so it has been retracted. + There will be a follow up update. + [...] + + + + Patch with conflicting packages + + + Information for patch openSUSE-SLE-15.3-2022-333: + ------------------------------------------------- + Repository : Update repository with updates from SUSE Linux Enterprise 15 + Name : openSUSE-SLE-15.3-2022-333 + Version : 1 + Arch : noarch + Vendor : maint-coord@suse.de + Status : needed + Category : security + Severity : important + Created On : Fri Feb 4 09:30:32 2022 + Interactive : reboot + Summary : Security update for xen + Description : + This update for xen fixes the following issues: + + - CVE-2022-23033: Fixed guest_physmap_remove_page not removing the p2m mappings. (XSA-393) (bsc#1194576) + - CVE-2022-23034: Fixed possible DoS by a PV guest Xen while unmapping a grant. (XSA-394) (bsc#1194581) + - CVE-2022-23035: Fixed insufficient cleanup of passed-through device IRQs. (XSA-395) (bsc#1194588) + Provides : patch:openSUSE-SLE-15.3-2022-333 = 1 + Conflicts : [22] + xen.src < 4.14.3_06-150300.3.18.2 + xen.noarch < 4.14.3_06-150300.3.18.2 + xen.x86_64 < 4.14.3_06-150300.3.18.2 + xen-devel.x86_64 < 4.14.3_06-150300.3.18.2 + xen-devel.noarch < 4.14.3_06-150300.3.18.2 + [...] + + + The above patch conflicts with the affected or vulnerable versions of 22 packages. If + any of these affected or vulnerable packages are installed, it triggers a conflict, + and the patch is classified as needed. zypper + patch tries to install all available patches. If it encounters problems, it + reports them, thus informing you that not all updates are installed. The conflict can + be resolved by either updating the affected or vulnerable packages or by removing + them. Because &suse; update repositories also ship fixed packages, updating is a + standard way to resolve conflicts. If the package cannot be updated—for + example, because of dependency issues or package locks—it is deleted after the + user's approval. + + + + + + To list all patches regardless of whether they are needed, use the option + additionally. For example, to list all patches with a CVE number + assigned, use: + +&prompt.user;zypper list-patches --all --cve + Issue | No. | Patch | Category | Severity | Status + ------+---------------+-------------------+-------------+-----------+---------- + cve | CVE-2019-0287 | SUSE-SLE-Module.. | recommended | moderate | needed + cve | CVE-2019-3566 | SUSE-SLE-SERVER.. | recommended | moderate | not needed + [...] +
+
+ Installing new package versions + + If a repository contains only new packages, but does not provide patches, + zypper patch does not show any effect. To update all installed + packages with newer available versions, use the following command: + +&prompt.sudo;zypper update + + + zypper update ignores problematic packages. For example, if a package + is locked, zypper update omits the package, even if a higher version + of it is available. Conversely, zypper patch reports a conflict if the + package is considered vulnerable. + + + + To update individual packages, specify the package with either the update or install + command: + +&prompt.sudo;zypper update PACKAGE_NAME + &prompt.sudo;zypper install PACKAGE_NAME + + A list of all new installable packages can be obtained with the command: + +&prompt.user;zypper list-updates + + Note that this command only lists packages that match the following criteria: + + + + + has the same vendor like the already installed package, + + + + + is provided by repositories with at least the same priority than the already installed + package, + + + + + is installable (all dependencies are satisfied). + + + + + A list of all new available packages (regardless whether installable + or not) can be obtained with: + +&prompt.sudo;zypper list-updates --all + + To find out why a new package cannot be installed, use the zypper + install or zypper update command as described above. + +
+
+ Identifying orphaned packages + + Whenever you remove a repository from Zypper or upgrade your system, some packages can get + in an orphaned state. These orphaned packages belong to + no active repository anymore. The following command gives you a list of these: + +&prompt.sudo;zypper packages --orphaned + + With this list, you can decide if a package is still needed or can be removed safely. + +
+
+ diff --git a/templates/README.md b/templates/README.md index 4f3865cea..bc1c85fe3 100644 --- a/templates/README.md +++ b/templates/README.md @@ -37,6 +37,15 @@ Typical glue topics include the intro section to your article, the "For more inf "What's next" sections. Also use glue topics to add an additional layer of navigation to your article. This is outlined in the `glue.xml` example file. +## Abstracts +Use the fixed abstract structure defined in the style guide to keep abstracts consistent across all articles: + +WHAT? — An objective definition of the product, feature, or solution. +WHY? — The benefit or motivation: why the reader should care. +EFFORT — Expected time investment and required background knowledge. +GOAL — The concrete outcome after completing the article. + +Write abstracts as factual summaries. Avoid procedural language, promises or marketing phrasing. ## Naming and directory conventions @@ -83,7 +92,7 @@ Where the particular parts have the following meaning: * `x86` - for x86-64 * `ppc` - for IBM Power PC * `s390`- for IBM Z -* `aarch` - for AArch64 +* `arm` - for Arm AArch64 `` is the assembly file name without the asm.xml part. @@ -177,7 +186,7 @@ you keep both docs in sync. This is done using a plain XML comment. Add some search engine-related information to your file: 1. `title`- 29-55 characters -1. `description` - max. 150 characters +1. `description` - max. 155 characters ### Search diff --git a/templates/_DC-article b/templates/_DC-article index 78ec5b183..35f701448 100644 --- a/templates/_DC-article +++ b/templates/_DC-article @@ -16,3 +16,4 @@ DOCBOOK5_RNG_URI="urn:x-suse:rng:v2:geekodoc-flat" STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse-ns" + diff --git a/templates/articles/assembly.asm.xml b/templates/articles/assembly.asm.xml index cfbdfeb7e..e6d75b758 100644 --- a/templates/articles/assembly.asm.xml +++ b/templates/articles/assembly.asm.xml @@ -60,7 +60,7 @@ - Your title (title style), limit to 55 chars, if possible + Your title (spelling: title style, length: 29-55 chars incl. whitespace) Subtitle if necessary + Updated CONTENT, extended CONTENT, removed CONTENT + YYYY-MM-DD @@ -92,11 +97,11 @@ - &productname; + &productname; - title for SEO and social media, max. 55 chars, keep in sync with article title - short description, max. 150 chars, no full stop: How to perform task xyz - ultrashort description for social media, max. 55 chars, no full stop: Perform task xyz + title for SEO/social media, max. 55 chars (incl. whitespace), keep in sync with article title + short description, max. 155 chars (incl. whitespace), no full stop: How to perform task xyz + ultrashort description for social media, max. 55 chars (incl. whitespace), no full stop: Perform task xyz Systems Management @@ -107,16 +112,16 @@ Configuration Installation - Products & Solutions + Products & Solutions https://bugzilla.suse.com/enter_bug.cgi Documentation - + SUSE Linux Enterprise Server &productnumber; MAINTAINER@suse.com diff --git a/xml/concept-zypper.xml b/xml/concept-zypper.xml deleted file mode 100644 index 5d64386a6..000000000 --- a/xml/concept-zypper.xml +++ /dev/null @@ -1,258 +0,0 @@ - - - - - - %entities; -]> -
- - Zypper package manager - - - https://bugzilla.suse.com/enter_bug.cgi - Smart Docs - Documentation - dmitri.popov@suse.com - - no - - &zypper; is a command-line tool - for installing, updating and removing software packages and for managing - repositories. - -
- Environment - - This document applies to the following products and product versions: - - - - - &sles; 15 SP5, 15 SP4, 15 SP3, 15 SP2, 12 SP5 - - - - - &sles4sap; 15 SP5, 15 SP4, 15 SP3, 15 SP2, 12 SP5 - - - - - &sleha; 15 SP5, 15 SP4, 15 SP3, 15 SP2, 12 SP5 - - - - - &slehpc; 15 SP5, 15 SP4, 15 SP3, 15 SP2 - - - - - &sled; 15 SP5 - - - - - &slert; 15 SP5 - - - -
-
- What is &zypper;? - - &zypper; is a command-line package manager for installing, updating and - removing packages. It can also be used to manage repositories. - -
-
- How does &zypper; work? - - &zypper; works and behaves as a regular command-line tool. It features - subcommmands, arguments, and options that can be used to perform specific - tasks. - -
-
- Benefits of &zypper; - - &zypper; offers several benefits compared to graphical package managers. - - - - - Being a command-line tool, &zypper; is faster in use and light on - resources. - - - - - &zypper; actions can be scripted. - - - - - &zypper; can be used on systems that do not have graphical desktop - environments. This makes it suitable for use with servers and remote - machines. - - - -
-
- General usage - - The general syntax of &zypper; is: - -zypper [GLOBAL_OPTIONS] SUBCOMMAND [SUBCOMMAND_OPTIONS] [ARGUMENTS] - - The components enclosed in brackets are not required. See zypper - help for a list of general options and all subcommands. To get help - for a specific subcommand, type zypper help - SUBCOMMAND. - - - - Zypper subcommands - - - The simplest way to execute &zypper; is to type its name, followed by a - command. For example, to apply all needed patches to the system, use: - -&prompt.sudo;zypper patch - - - - Global options - - - Additionally, you can choose from one or more global options by typing - them immediately before the command: - -&prompt.sudo;zypper --non-interactive patch - - In the above example, the option means - that the command is run without asking anything (automatically applying - the default answers). - - - - - Command-specific options - - - To use options that are specific to a particular command, type them - immediately after the command: - -&prompt.sudo;zypper patch --auto-agree-with-licenses - - In the above example, is used - to apply all needed patches to a system without you being asked to - confirm any licenses. Instead, license will be accepted automatically. - - - - - Arguments - - - Some commands require one or more arguments. For example, when using the - command install, you need to specify one or more packages - you want to install: - -&prompt.sudo;zypper install mplayer - - Some options also require a single argument. The following command will - list all known patterns: - -&prompt.user;zypper search --type pattern - - - - - You can combine all of the above. For example, the following command will - install the mc and vim packages from - the factory repository while being verbose: - -&prompt.sudo;zypper --verbose install --from factory mc vim - - The option keeps all repositories enabled (for - solving any dependencies) while requesting the package from the specified - repository. The option is an alias for , - and you may use either one. - - - Most &zypper; commands have a dry-run option that does a - simulation of the given command. It can be used for test purposes: - -&prompt.sudo;zypper remove --dry-run MozillaFirefox - - &zypper; supports the global option. You can specify a string - with this option, which gets written to &zypper;'s log files and plug-ins - (such as the Btrfs plug-in). It can be used to mark and identify - transactions in log files. - -&prompt.sudo;zypper --userdata STRING patch -
-
- Using Zypper subcommands - - &zypper; subcommands are executables that are stored in the directory - /usr/lib/zypper/commands. If a subcommand is not found - in this directory, &zypper; automatically searches the rest of your $PATH - for it. This enables writing your own local extensions and storing them in - userspace. - - - Executing subcommands in the &zypper; shell, and using global &zypper; options - are not supported. - - - List your available subcommands: - -&prompt.user;zypper help subcommand -[...] -Available zypper subcommands in '/usr/lib/zypper/commands' - - appstream-cache - lifecycle - migration - search-packages - -Zypper subcommands available from elsewhere on your $PATH - - <none> - - View the help screen for a subcommand: - -&prompt.user;zypper help appstream-cache -
-
- Related topics - - - - - - Installing and removing software with &zypper; - - - - - Updating software with &zypper; - - - -
-
diff --git a/xml/reference-zypper-install.xml b/xml/reference-zypper-install.xml deleted file mode 100644 index f1b1ee5bb..000000000 --- a/xml/reference-zypper-install.xml +++ /dev/null @@ -1,150 +0,0 @@ - - - - - - %entities; -]> -
- - Installing and removing software with &zypper; reference - - - https://bugzilla.suse.com/enter_bug.cgi - Smart Docs - Documentation - dmitri.popov@suse.com - - no - - Learn how to perform package and - repository management tasks using the &zypper; command-line. - -
- Environment - - This document applies to the following products and product versions: - - - - - &sles; 15 SP5, 15 SP4, 15 SP3, 15 SP2, 12 SP5 - - - - - &sles4sap; 15 SP5, 15 SP4, 15 SP3, 15 SP2, 12 SP5 - - - - - &sleha; 15 SP5, 15 SP4, 15 SP3, 15 SP2, 12 SP5 - - - - - &slehpc; 15 SP5, 15 SP4, 15 SP3, 15 SP2 - - - - - &sled; 15 SP5 - - - - - &slert; 15 SP5 - - - -
-
- - Install and remove packages with &zypper; - - The following two basic commands can be used to install and remove packages: - -&prompt.sudo;zypper install PACKAGE_NAME -&prompt.sudo;zypper remove PACKAGE_NAME - - Selecting packages to install or remove - - zypper install MozillaFirefox - - - Install a package using its exact name. - - - - - zypper install MozillaFirefox-92 - - - Install a package by its exact name and version number. - - - - - zypper install mozilla:MozillaFirefox - - - Install a package by its exact name from a specific repository (where - mozilla refers to the desired repository). - - - - - zypper install 'Moz*' - - - Install a package using wild cards in its name. The example command above - installs all packages which names start with Moz. - - - - - zypper install firefox - - - Install a package by the capability it provides. In this example, the firefox capability is provided by the MozillaFirefox package, thus running the command installs this specific package. For more information on the concept of capability, refer to "Capability concept". - - - - - zypper install 'firefox.x86_64' - - - Install a package by its capability, hardware architecture and version. - Versions must be appended to the end of the string and must be preceded - by an operator: < (lesser than), - <= (lesser than or equal), = - (equal), >= (greater than or equal), - > (greater than): - -&prompt.sudo;zypper install 'firefox>=74.2' - - You can also combine a hardware architecture and version requirement: - -&prompt.sudo;zypper install 'firefox.x86_64>=74.2' - - - - zypper install /tmp/install/MozillaFirefox.rpm and zypper install http://download.&exampledomain;/MozillaFirefox.rpm - - - Install a package using a local or remote RPM file. - - - - -
-