|PACKINIT(1)||General Commands Manual||PACKINIT(1)|
packinit - initialize or update your .package file
Packinit will create (or update) a .package file, so that all the dist tools can be smart and know some basic things about your package, such as its revision number, or the e-mail address of its maintainer.
Packinit should be run from the top level directory of your package, before using any other dist tool. Later on, you may rerun it to update some of its values. Packinit will create a single file and leave the remaining of your directory undisturbed.
Packinit defines the following variables in your .package file:
- The baseline revision number.
- The list (space separated) of file extensions identifying potential holders of C symbols. This is added to the default .[chyl] extension lookup. Shell-style patterns may be used.
- The name of the ChangeLog file managed by patlog.
- Boolean stating whether RCS logs are to be made part of ChangeLog.
- Name of the file used for Copyright expansion.
- Directory where patches are located on the FTP site.
- Name of the FTP site where patches may be retrieved from.
- Address of the package mailing list where users may post messages to.
- Type of list manager attached to the list administrative request address.
- Name of the package users mailing list.
- Address where subscribe and unsubscribe requests for the package mailing list should be sent to.
- Format of the subscribe requests.
- Format of the unsubscribe requests.
- A boolean string set to 'true' when there is a mailing list set up for discussion about the package.
- A boolean string set to 'true' when people are allowed to retrieve patches via mailagent @SH mailpatch commands.
- E-mail address of the package maintainer, preferably in Internet format.
- Full name of the package maintainer.
- Name of the diff program to be used when computing a patch.
- Newsgroup list where new patches should be posted to, empty for no postings.
- Full name of the organization where the package maitainer resides, or path to a file containing that name.
- Name of the package.
- Version of the packinit program that built the .package file.
- Name of the RCS branch used to store subsequent updates of a file after a baseline has been released.
- People who should be sent newly issued patches.
- The list (space separated) of file extensions identifying potential holders of shell symbols. This is added to the default .SH extension lookup. Shell-style patterns may be used. Note that only .SH extensions are looked up by Configure for automatic shell extraction with variable substitutions, no matter what this variable is set to.
- File holding all the package-related values
Larry Wall <firstname.lastname@example.org> (version 2.0)
Raphael Manfredi <Raphael.Manfredi@pobox.com>