No edit summary |
Jussilehtola (talk | contribs) (Some spell corrections) |
||
| Line 12: | Line 12: | ||
== When to create filesystem subapckages == | == When to create filesystem subapckages == | ||
If | If two or more packages provide a common set | ||
of files and directories without a | of files and directories without a technical requirement | ||
relationship between each other a filesystem subpackage | |||
that provides this set of common files and directories | |||
files and directories. | <b>MUST</b> be created. | ||
== Naming == | == Naming == | ||
The name of the | The name of the filesystem subpackage has the following form: | ||
<pre> | <pre> | ||
| Line 28: | Line 28: | ||
If you have a collection of packages which provide a common set | If you have a collection of packages which provide a common set | ||
of files and directories and they have a common group name like kde, | of files and directories and they have a common group name like kde, | ||
you can call the filesystem subpackage | you can call the filesystem subpackage | ||
<pre> | <pre> | ||
| Line 35: | Line 35: | ||
== Packaging == | == Packaging == | ||
All files and directories which | All files and directories which are needed by two or more packages | ||
in common, are packaged into the filesystem subpackage. | in common, are packaged into the filesystem subpackage. | ||
Each package which | Each package which wants two provide one of these files or | ||
directories | directories has to include a require statement which refers | ||
to the filesystem subpackage. | to the filesystem subpackage. | ||
| Line 46: | Line 46: | ||
== Sample == | == Sample == | ||
A package which provides the filesystem subpackage: | |||
<pre> | <pre> | ||
| Line 61: | Line 61: | ||
%description filesystem | %description filesystem | ||
This package provides files and directories which are | This package provides files and directories which are common | ||
with other packages | with other packages | ||
%files filesystem | %files filesystem | ||
<List | <List of files, which are common with other packages> | ||
</pre> | </pre> | ||
Latest revision as of 18:06, 5 August 2009
Guidelines for creating filesystem subpackages
Filesystem Subpackages Guidelines
Author: Jochen Schmitt
Revision: 0.01
Initial Draft: Sunday June 28, 2006
Last Revised: Sunday June 28, 2009
When to create filesystem subapckages
If two or more packages provide a common set of files and directories without a technical requirement relationship between each other a filesystem subpackage that provides this set of common files and directories MUST be created.
Naming
The name of the filesystem subpackage has the following form:
<Main package>-filesystem
If you have a collection of packages which provide a common set of files and directories and they have a common group name like kde, you can call the filesystem subpackage
<Group name>-filesystem
Packaging
All files and directories which are needed by two or more packages in common, are packaged into the filesystem subpackage.
Each package which wants two provide one of these files or directories has to include a require statement which refers to the filesystem subpackage.
<package-name>-filesystem
Sample
A package which provides the filesystem subpackage:
Name: foo1
Summary: A Package
Requires foor1 = %{version}-%{release}
%description
Package filesystem
Summary Files and directories common with other packages
%description filesystem
This package provides files and directories which are common
with other packages
%files filesystem
<List of files, which are common with other packages>
Package which want to provides files and directories from the filesystem subpackage:
Name forr2 Requires: foo1-filesystem