Difference between revisions of "User:Kr/Packaging"
From Apache OpenOffice Wiki
< User:Kr
m |
m |
||
Line 1: | Line 1: | ||
− | === | + | ==Terms== |
− | + | ===Product=== | |
+ | A Product is a set of bits, e.g. an ISO image or a self extracting exe. | ||
− | + | A product may be described by | |
+ | * the source code to be used (e.g. a CVS repository and a CVS tag), this is the products '''code base''', | ||
+ | * it's features, as well as the brand and the localization to be included, and the configuration used while building, this is the products '''variant''', | ||
+ | * it's relationship to previous products, this may be something as "patch", "update", "respin" or "add-on", this is the products '''type''', | ||
+ | * the format of its bits, e.g. "ISO image", "self extracting archive" or "APT repository", this is the products '''format'''. | ||
+ | * the target platform (architecture and Operating System), e.g. Solaris Sparc, Linux x86 or Windows x64, this is the products '''platform'''. | ||
− | + | E.g. | |
− | + | SO8u9Solx86-CD = SRC680_m236, [{StarOffice}, {Writer, Calc, Impress, Draw}, {English, German}], Update-to(SO8u1), ISO, Solaris/x86 | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
+ | ===Version=== | ||
+ | Software provided to a customer typically has a version, describing timely variant. Typically older variants have smaller version the younger variants. Versions may be differentiated into '''Major''', '''Minor''' and '''Micro'''. | ||
+ | ==Requirements== | ||
+ | ===Development=== | ||
Support for Changes: | Support for Changes: | ||
* updated package(s) | * updated package(s) | ||
Line 27: | Line 28: | ||
* move file(s) | * move file(s) | ||
+ | ===Program Management=== | ||
+ | In a perfect world, program management would be able to create any kind of product, only depending on business needs, not at all restricted by technical constraints. | ||
− | + | Program Management basically mediates between marketing / market requirements and the pool available technologies. | |
+ | |||
+ | ==Package Systems== | ||
====.deb/apt==== | ====.deb/apt==== | ||
Line 67: | Line 72: | ||
Links: | Links: | ||
http://msdn2.microsoft.com/en-us/library/aa372866.aspx | http://msdn2.microsoft.com/en-us/library/aa372866.aspx | ||
+ | |||
+ | ==Constraints== |
Revision as of 10:11, 8 November 2007
Contents
Terms
Product
A Product is a set of bits, e.g. an ISO image or a self extracting exe.
A product may be described by
- the source code to be used (e.g. a CVS repository and a CVS tag), this is the products code base,
- it's features, as well as the brand and the localization to be included, and the configuration used while building, this is the products variant,
- it's relationship to previous products, this may be something as "patch", "update", "respin" or "add-on", this is the products type,
- the format of its bits, e.g. "ISO image", "self extracting archive" or "APT repository", this is the products format.
- the target platform (architecture and Operating System), e.g. Solaris Sparc, Linux x86 or Windows x64, this is the products platform.
E.g.
SO8u9Solx86-CD = SRC680_m236, [{StarOffice}, {Writer, Calc, Impress, Draw}, {English, German}], Update-to(SO8u1), ISO, Solaris/x86
Version
Software provided to a customer typically has a version, describing timely variant. Typically older variants have smaller version the younger variants. Versions may be differentiated into Major, Minor and Micro.
Requirements
Development
Support for Changes:
- updated package(s)
- (automatically) remove package(s)
- add package(s)
- rename package(s)
- remove file(s)
- add file(s)
- move file(s)
Program Management
In a perfect world, program management would be able to create any kind of product, only depending on business needs, not at all restricted by technical constraints.
Program Management basically mediates between marketing / market requirements and the pool available technologies.
Package Systems
.deb/apt
Relations:
- "depends"
- "recommends"
- "conflicts"
- "suggests"
- "replaces"
- "pre-depends"
- "breaks"
Tags:
- "priority"
- "section"
Features:
- "manual install"
.rpm
Relations:
- "provides"
- "requires"
.msi
Features:
- installation on demand
- advertisement ("assigning" / "publishing")
- customization
- patching / updating
- usage metrics on features - automagic de-installation
- Incorporated installations == ? "dependencies" ?
- Resiliency
- User / Machine wide installation
- Installer functions (API for MSI)
- Administrative Installation
Links: http://msdn2.microsoft.com/en-us/library/aa372866.aspx