Lines Matching full:package

29 .Nd create binary software package for distribution
57 command is normally used to create a binary package named
79 can also be used to recreate a binary package from an existing installation.
81 During package creation,
86 .Xr package 5
102 the package to build correctly, and thus be reachable through the
109 Register a list of architectures for which this package should install.
118 as the prefix to prepend to any file to select for the package.
131 .Xr package 5
139 Set package
161 annotations in the generated package, rely on the normal
167 .Xr package 5
171 package creation.
177 catch a few errors in package naming.
180 Fetch long description for package from file
188 for package from the file
195 as the localbase used in the package
207 after installing the package.
215 Don't actually create a package.
217 Declare a dependency on a package matching
220 An appropriate package must be installed before this package may be
221 installed, and that package must be deinstalled before this package
231 package name, in case there is no listing of available packages.
246 the package, and to record as the base for installing the package.
248 Print out the files in the actual packing-list of the package being
252 Print out the actual packing-list of the package being generated
257 Print the update signature of the package.
263 when deinstalling the package.
284 of the package
286 .Xr package 5
294 Package needs a shared library to work.
300 The package won't be installed unless a library with the same name,
318 can also be invoked with only the packing-list from an installed package.
319 It will recreate the corresponding binary package in the current directory
324 package:
334 to include in the package.
351 If the new package is installed as part of an update matching
388 will be recorded in the package, it can be altered after installation, and
407 package can
409 be installed if a package
415 Set the package current directory.
468 As a special case, deleting the package that contains the
473 is present in the same package as the
480 since the package has been deleted from the file system,
731 uses some simplified information to decide whether an installed package
733 With this option, the package will be updated whenever anything changes.
745 By default, a package conflicts with other versions of the same package.
746 With this option, the older package version will still be noticed, but the
759 for the package.
765 embedded in the package corresponds to the old package,
804 Each binary package contains a set of pkgpaths: the primary pkgpath that
805 was used to build the package, recorded as
811 a secondary pkgpath must match the other package's primary pkgpath.
903 and not while removing an old package during updates.
908 except it only gets executed while removing an old package during updates,
922 but global to the package ecosystem in general, and thus make it into
923 the package locate database by default
936 .Xr package 5
938 package tools.
1015 .Xr package 5 ,