Files in a Wigwam Package

List of GNU-style architecture and package-architecture pairs. This lets a package specify exactly which architectures are supported without the package having to know about every GNU type.

For now, you may set WIGWAM_ARCHS_SUPPORTED to a list of package-architectures allowed; this way you can just say WIGWAM_ARCHS_SUPPORTED="i386" and use the standard intel versions; for example:

i686-pc-gnu-linux i386 i586-pc-gnu-linux i386 i486-pc-gnu-linux i386 i386-pc-gnu-linux i386

List of architecture-dependent files. The $ARCH must correspond to the the right-hand column of the archs file. This lets a package specify exactly which architectures are supported without the package having to know about every GNU type.

For now, you may set WIGWAM_ARCHS_SUPPORTED to a list of package-architectures allowed; this way you can just say WIGWAM_ARCHS_SUPPORTED="i386" and use the standard intel versions.

List of files for this package that must be retrieved from the package archive. It should list every file in the source package archive for this package including itself.

This file is mandatory.

What type of package this is. This may be make, service, or raw.

Options specific to this package's build process, see the Section called Configuring the Build and Install Process.

List of md5sums for each file listed in the .files list. This is used to verify that the package is downloaded from the package archive correctly.

This file is mandatory.

This are small scripts that will be run before and after the patches to the package's source are applied. They are rarely used: generally they are used when a file's permission needs changing, or when a file created by a patch needs non-default permissions.

the source code from the upstream maintainer, or from make dist from your CVS repository.

Though .tar.gz is probably the most common archive format, many others are supported.

Note that there is no required naming convention for upstream sources: you should use the exact name of the file as it is downloaded, unless its filename conflicts with a different file from another package. By common convention, the upstream sources are usually named PACKAGE-UPSTREAM_VERSION.tar.gz.

Patches that should be applied to the upstream source code.

Patch files contain changes generated with the diff -u program. The build system automatically tries to guess the flags needed to patch the source code.

Any files ending in .patch.bz2, .patch.gz, and .patch are applied.

The packaging system tries to guess the right patch flags, but if it gets it wrong, you may need to use patch_flags_PATCH_FILE_CANONICALIZED where PATCH_FILE_CANONICALIZED is the patch's base filename with . converted to _ and - converted to _

Wigwam packages this package depends upon at various points in its lifetime. See the Section called Dependencies.

Files or packages that a service provided by a package depends upon. See the Section called Dependencies.

This is a list of packages which may not be installed concurrently with this package. Two packages conflict if either lists the other in its conflict file; there is no difference between A conflicts with B and B conflicts with A.

This file may list specific version numbers, using a SPACE character to separate the package name from the version number, or it may omit the version number to conflict with any version of that package.

This is a list of packages which this package clones. These should act as reasonable substitutes for the packages they provide.

Each line of this file must start with a package name. After a single space character, there may also be a version number. If no version number is specified, the package can act as any version of the package it provides.

list of directories that must be available for this package to be installed.

List of files that this package affects. This file may be automatically computed from your pacakge with the make-installed-files-list script in any package archive.

Each line in this file consists of an action, a space, and a filename. The action may be any of the following characters and should describe what happened to the file.