CNT-2311-Chapter 2 Notes: Difference between revisions
| Line 17: | Line 17: | ||
Redhat developed RPM for it's own personal distribution, but released freely thereafter. It soon became widely used as a cross platform tool. RPM packages look like the following example. | Redhat developed RPM for it's own personal distribution, but released freely thereafter. It soon became widely used as a cross platform tool. RPM packages look like the following example. | ||
'''Coolpackage'''- | '''Coolpackage'''-3.1.5-'''V'''.i368.rpm | ||
So that would be | So that would be | ||
'''Packagename'''-Versionnumber-'''Build'''.Architecture.rpm | |||
Revision as of 19:50, 11 February 2011
Overview
This is where we actually do an overview
Package Concepts
Packages - A package consists of usually many files, with information about the file, including information that aids in the package management system.
Installed file database - A database of the installed files. All installed files should appear here.
Dependencies - Dependency information is the requirements of packages for one another. Ala, one package needs the other to work, and vice versa.
Checksums - checksums are information about files. they can be used to tell the validity of software, disk errors, accidental overwriting of and non-sinister files. It's not a subtle in detecting intrusions.
Binary Package Creation - RPM and Debian packages systems provide tools to create binary packages.
RPM Packaging
Redhat developed RPM for it's own personal distribution, but released freely thereafter. It soon became widely used as a cross platform tool. RPM packages look like the following example.
Coolpackage-3.1.5-V.i368.rpm So that would be Packagename-Versionnumber-Build.Architecture.rpm
Yum
Debian Packaging
Debian Notes
APT Get
Converting Packages
Overview of Converting
Alien
Alien Overview