| pkg_create.1 (379) | pkg_create.1 (383) |
|---|---|
| 1.\" 2.\" FreeBSD install - a package for the installation and maintainance 3.\" of non-core utilities. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" 1. Redistributions of source code must retain the above copyright --- 92 unchanged lines hidden (view full) --- 101.BI "\-r\ " script 102Sets 103.I script 104to be the "requirements" procedure for the package. This can be any 105executable program (or shell script). It will be invoked automatically 106at installation/deinstallation time to determine whether or not 107installation/deinstallation should proceed. 108.B "Optional." | 1.\" 2.\" FreeBSD install - a package for the installation and maintainance 3.\" of non-core utilities. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" 1. Redistributions of source code must retain the above copyright --- 92 unchanged lines hidden (view full) --- 101.BI "\-r\ " script 102Sets 103.I script 104to be the "requirements" procedure for the package. This can be any 105executable program (or shell script). It will be invoked automatically 106at installation/deinstallation time to determine whether or not 107installation/deinstallation should proceed. 108.B "Optional." |
| 109.TP 110.BI "\-t\ " template 111Use 112.I template 113as the input to mktemp(3). By default, this is the string 114.B /tmp/instmp.XXXXXX, 115but it may be necessary to override it in the situation where 116space in your 117.B /tmp 118directory is limited. Be sure to leave some number of `X' characters 119for mktemp(3) to fill in with a unique ID. 120.B "Optional." |
|
| 109.PP 110.SH "TECHNICAL DETAILS" 111The "packing list" format (see \fB-f\fR) is fairly simple, being 112nothing more than a single column of filenames to include in the 113package. However, since absolute pathnames are generally a bad idea 114for a package that could be installed potentially anywhere, there is 115another method of specifying where things are supposed to go 116and, optionally, what ownership and mode information they should be --- 52 unchanged lines hidden (view full) --- 169ignore it. 170.TP 171.BI "@name\ " name 172Sets the name of the package. This is mandatory and is usually 173put at the top. This name is potentially different than the name of 174the file it came in, and is used when keeping track of the package 175for later deinstallation. Note that 176.B pkg_create | 121.PP 122.SH "TECHNICAL DETAILS" 123The "packing list" format (see \fB-f\fR) is fairly simple, being 124nothing more than a single column of filenames to include in the 125package. However, since absolute pathnames are generally a bad idea 126for a package that could be installed potentially anywhere, there is 127another method of specifying where things are supposed to go 128and, optionally, what ownership and mode information they should be --- 52 unchanged lines hidden (view full) --- 181ignore it. 182.TP 183.BI "@name\ " name 184Sets the name of the package. This is mandatory and is usually 185put at the top. This name is potentially different than the name of 186the file it came in, and is used when keeping track of the package 187for later deinstallation. Note that 188.B pkg_create |
| 177currently derives this field from the package name and adds it 178automatically. | 189will derive this field from the package name and add it automatically 190if none is given. |
| 179 180.SH BUGS 181Sure to be some. 182.SH "SEE ALSO" 183.BR pkg_add "(" 1 ")," 184.BR pkg_info "(" 1 ")," 185.BR pkg_delete "(" 1 ")," 186.SH AUTHORS 187Jordan Hubbard 188 | 191 192.SH BUGS 193Sure to be some. 194.SH "SEE ALSO" 195.BR pkg_add "(" 1 ")," 196.BR pkg_info "(" 1 ")," 197.BR pkg_delete "(" 1 ")," 198.SH AUTHORS 199Jordan Hubbard 200 |