Software Management

Preface

Understand Compiling Software from Source

Compile From Source Code

• Linux Source Code Build Tools
• Works well for a single box
• Many Linux open source projects utilize
• Common GNU build tools
• Two common GNU build tools
  • Automake
  • Autoconf
• Developers use Automake and Autoconf with…
  • makefile.am
  • configure.in
• To create the automatic configuration file
  • configure

Compiling Process

• The general process for building source code
  • ./configure
  • make
  • make install
• Make supports combining last two steps
  • ./configure
  • make install
• Performs a make and then a make install automatically

Build Process Step-By-Step

• Specific actions for building source code
• Download tarball from source code download page
  • .tar.gz .tgz .tar.bz2
• Extract contents in safe location
  • tar -zxvf sourcecode-1.0.tar.bz2
• Change to extracted directory
  • cd sourcecode-1.0/
• Read the included Documentation
• Autoconfigure
  • ./configure
• Compile and install
  • make install

Understand Makefile Targets

• The make command uses what are called “targets”
• Target Actions:
  • clean
    • Clean up: remove compiled binaries and objects
  • distclean
    • clean + remove files that ./configure created
  • make
    • Actually compile the source code
  • install
    • Copy binaries and shared objects to filesystem
• uninstall
  • Uninstall the components created during install
  • Does not always remove all components
  • Only as good as creator of the Automake components
  • Not always provided as target in Makefile
  • May abandon software throughout filesystem

Use make to Compile the Source Code

Disadvantages Of Unpackaged Software

• Software dependencies are not readily apparent
• Hard to duplicate effort across enterprises (難以跨企業重複工作)
• Upgrading very difficult
• Updating nearly(幾乎) impossible
• Slow security responses (安全問題的回應速度緩慢)
• Duplication of effort(工作重複)
• Uneven results(結果可能會不一樣)
• Support and troubleshooting problems
  • Tarball management is fine for a single computer
  • Unmanageable across hundreds or thousands of computers
• Difficult to track installed files without work
  • Manual tracking after each install
  • Linux command line tools
    • find
    • tar
    • md5sum
    • vimdiff
• Uses some disk space for tracking
• Non-filesystem tracking requires reading install control files(非檔案系統的追蹤需要讀取安裝控制的文件)
  • configure
  • Makefile

Understand Management of RPM Packages

RPM Basics

RPM Package Components

Install RPM Packages

• Command: rpm -i <package>.rpm
  • 當您安裝一個 RPM 軟體包時，執行檔、DOC 文件、設定檔以及啟動腳本會被複製到檔案系統中適當的目錄下。
• Additional Options:
  • -v ，(verbose) for more information ，顯示更多資訊
  • -h ，(hash) for a progress bar，在軟體包安裝期間產生一個由#符號組成的進度條。
• In case of dependency conflicts or file problems:
  • --nodeps ，to ignore dependencies ，忽略相依檔產生的問題
  • --force ，to overwrite existing files，覆蓋已存在的檔案
  • 如果強制安裝而沒有滿足相依性要求，安裝的軟體很可能無法正常運作

Update RPM Packages

• Update: rpm -U <package>.rpm
  • Works even if no previous version is installed
  • 即使未安裝以前的版本 也會安裝新版本
• Freshen: rpm -F <package>.rpm
  • Work only if a previous version is installed
  • 僅在安裝了早期版本時才有效 (如果沒有安裝過先前的版本，則不會安裝新的軟體包。)
  • 會刪除舊版本的文件，並立即安裝新的文件。
• 注意 ! -U 選項並不等同於使用 -e 選項進行卸載並使用 -i 選項進行安裝。更新軟體包時，盡可能使用 -U 選項

Uninstall RPM Packages

• Command: rpm -e <package>
• Additional Options:
  • --nodeps to ignore dependencies

Query RPM Database and Packages

• -q，Query RPM database
• Common query options:
  • -a，List all installed packages
  • -i，List package information
  • -l，Display file list
    • --dump，Display a file list with complete details Used with -l, -c or -d
  • -f <file>，找出檔案屬於哪個包，在查詢的時候，必須指定完整路徑
  • -d，List only documentation files (implies -l)
  • -c，List only configuration files (implies -l)
• -p ，Inspect not installed RPM archives
• --provides，List features of the package that another package can request with –requires
  • 列出一個套件可以透過 --requires 的方式要求另一個套件提供哪些功能特色。
• --requires, -R，List capabilities the package requires
• --scripts，List installation scripts Pre-install, post-install and un-install
• --changelog，Display detailed list of information about a specific package Updates, configuration, modifications, etc.

RPM Package Verification

• Verify that the package has not changed since it was created:
  • rpm --checksig <package>.rpm
• Verify integrity (完整性) of files installed by an RPM package:
  • rpm -V <package>

• Character，Description
  • S，List package information
  • M，Mode has change
  • 5，Size is different
  • D，Device major/minor numbers are different
  • L，Readlink (symbolic link) path mismatch
  • U，User ownership differs
  • G，Group ownership differs
  • T，mtime differs
  • P，Capabilities differ

Understand Software Management with Libzypp

Libzypp

What Are Software Repositories?

Software repositories (often called catalogs)

• Directories that contain RPM software packages and meta-data files that describe the packages.
• Can be accessed by RPM meta-managers
• Can be accessed from different media and local file systems
  • different media such as the network (HTTP, FTP, NFS, SMB, etc.), DROM/DVD disks

Software repositories provide many benefits such as:

• They provide catalogs(目錄) for RPM Meta-managers to use when doing RPM dependency resolution
• They provide centrally(集中的) managed and accessible sources(可存取的來源) for installing software and updates
• They provide a framework for tracking and finding different versions of software

Libzypp and Software Repositories


The 4 “P"s of Libzypp

• Packages
  • RPM packages (including patch/delta RPMS)
  • Contain files to be installed in file system
• Patterns
  • Reference 1 or more packages
  • Typically install all packages needed for a certain sever “role”
• Products
  • Contain 1 or more Patterns
  • Associated with a product with its own support and maintenance such
  • as an Extension/Add-on
• Patches
  • Reference 1 or more update packages
  • (packages provided as both full and patch/delta RPMs)

Libzypp Utilities

Definition of Terms

Manage Repositories with zypper

• List software repositories:
  • zypper lr
• Add repositories:
  • zypper ar <uri> <alias>
• Remove repositories:
  • zypper rr <alias|#|uri>
• Modify repositories:
  • zypper mr [options] <alias|#|uri>

~> zypper lr

# | Alias | Name | Enabled | Refresh
--+-------------+-------------+---------+--------
1 | SLES15-15-0 | SLES15-15-0 | Yes | No

~> zypper lr -d

# | Alias | Name | Enabled | Refresh | Priority | Type | URI
 | Service
--+-------------+-------------+---------+---------+----------+-------
+----------------------------------------------------------------------------------------+--------
1 | SLES15-15-0 | SLES12-15-0 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ataVMware_Virtual_IDE_CDROM_Drive_10000000000000000001 |

~> zypper ar [options] <uri> <alias>

~> zypper addrepo [options] <uri> <alias>

~> zypper addrepo http://172.17.8.100/sles15/CD1 sles12

zypper rr <alias|#|uri>

zypper removerepo <alias|#|uri>

zypper mr [options] <alias|#|uri>

zypper modifyrepo [options] <alias|#|uri>