pkg_create.1 (50479) | pkg_create.1 (50741) |
---|---|
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 9.\" notice, this list of conditions and the following disclaimer. 10.\" 2. Redistributions in binary form must reproduce the above copyright 11.\" notice, this list of conditions and the following disclaimer in the 12.\" documentation and/or other materials provided with the distribution. 13.\" 14.\" Jordan K. Hubbard 15.\" 16.\" 17.\" @(#)pkg_create.1 | 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 9.\" notice, this list of conditions and the following disclaimer. 10.\" 2. Redistributions in binary form must reproduce the above copyright 11.\" notice, this list of conditions and the following disclaimer in the 12.\" documentation and/or other materials provided with the distribution. 13.\" 14.\" Jordan K. Hubbard 15.\" 16.\" 17.\" @(#)pkg_create.1 |
18.\" $FreeBSD: head/usr.sbin/pkg_install/create/pkg_create.1 50479 1999-08-28 01:35:59Z peter $ | 18.\" $FreeBSD: head/usr.sbin/pkg_install/create/pkg_create.1 50741 1999-09-01 10:04:47Z jkh $ |
19.\" 20.\" hacked up by John Kohl for NetBSD--fixed a few bugs, extended keywords, 21.\" added dependency tracking, etc. 22.\" 23.\" [jkh] Took John's changes back and made some additional extensions for 24.\" better integration with FreeBSD's new ports collection. 25.\" 26.Dd April 21, 1995 --- 31 unchanged lines hidden (view full) --- 58really meant to be human-generated, though it is easy enough to 59do so. It is more expected that you will use a front-end tool for 60the job rather than muddling through it yourself. Nonetheless, a short 61description of the input syntax is included in this document. 62.Sh OPTIONS 63The following command line options are supported: 64.Bl -tag -width indent 65.It Fl f Ar packinglist | 19.\" 20.\" hacked up by John Kohl for NetBSD--fixed a few bugs, extended keywords, 21.\" added dependency tracking, etc. 22.\" 23.\" [jkh] Took John's changes back and made some additional extensions for 24.\" better integration with FreeBSD's new ports collection. 25.\" 26.Dd April 21, 1995 --- 31 unchanged lines hidden (view full) --- 58really meant to be human-generated, though it is easy enough to 59do so. It is more expected that you will use a front-end tool for 60the job rather than muddling through it yourself. Nonetheless, a short 61description of the input syntax is included in this document. 62.Sh OPTIONS 63The following command line options are supported: 64.Bl -tag -width indent 65.It Fl f Ar packinglist |
66Fetch ``packing list'' for package from the file | 66Fetch 67.Dq packing list 68for package from the file |
67.Ar packinglist 68or 69.Cm stdin 70if 71.Ar packinglist 72is a 73.Cm - 74(dash). 75.It Fl c Ar [-]desc | 69.Ar packinglist 70or 71.Cm stdin 72if 73.Ar packinglist 74is a 75.Cm - 76(dash). 77.It Fl c Ar [-]desc |
76Fetch package ``one line description'' from file | 78Fetch package 79.Dq one line description 80from file |
77.Ar desc 78or, if preceded by 79.Cm - , 80the argument itself. This string should also 81give some idea of which version of the product (if any) the package 82represents. 83.It Fl d Ar [-]desc 84Fetch long description for package from file --- 46 unchanged lines hidden (view full) --- 131.Ar pkgs . 132This is assumed to be a whitespace separated list of package names 133and is meant as a convenient shorthand for specifying multiple 134.Cm @pkgdep 135directives in the packing list (see PACKING LIST DETAILS section below). 136.It Fl p Ar prefix 137Set 138.Ar prefix | 81.Ar desc 82or, if preceded by 83.Cm - , 84the argument itself. This string should also 85give some idea of which version of the product (if any) the package 86represents. 87.It Fl d Ar [-]desc 88Fetch long description for package from file --- 46 unchanged lines hidden (view full) --- 135.Ar pkgs . 136This is assumed to be a whitespace separated list of package names 137and is meant as a convenient shorthand for specifying multiple 138.Cm @pkgdep 139directives in the packing list (see PACKING LIST DETAILS section below). 140.It Fl p Ar prefix 141Set 142.Ar prefix |
139as the initial directory ``base'' to start from in selecting files for | 143as the initial directory 144.Dq base 145to start from in selecting files for |
140the package. 141.It Fl k Ar dscript 142Set 143.Ar dscript 144to be the de-install procedure for the package. This can be any executable 145program (or shell script). It will be invoked automatically when the 146package is later (if ever) de-installed. It will be passed the package's 147name as the first argument. --- 14 unchanged lines hidden (view full) --- 162to be the post-deinstall procedure for the package. This can be any 163executable program (or shell script). It will be invoked automatically when 164the package is later de-installed. It will be passed the package's name as 165the first argument. 166 167.It Fl r Ar rscript 168Set 169.Ar rscript | 146the package. 147.It Fl k Ar dscript 148Set 149.Ar dscript 150to be the de-install procedure for the package. This can be any executable 151program (or shell script). It will be invoked automatically when the 152package is later (if ever) de-installed. It will be passed the package's 153name as the first argument. --- 14 unchanged lines hidden (view full) --- 168to be the post-deinstall procedure for the package. This can be any 169executable program (or shell script). It will be invoked automatically when 170the package is later de-installed. It will be passed the package's name as 171the first argument. 172 173.It Fl r Ar rscript 174Set 175.Ar rscript |
170to be the ``requirements'' procedure for the package. This can be any | 176to be the 177.Dq requirements 178procedure for the package. This can be any |
171executable program (or shell script). It will be invoked automatically 172at installation/deinstallation time to determine whether or not 173installation/deinstallation should proceed. 174.It Fl s Ar srcdir 175.Ar srcdir 176will override the value of 177.Cm @cwd 178during package creation. --- 46 unchanged lines hidden (view full) --- 225where 226.Pa prefix 227is the name of the first directory named by a 228.Cm @cwd 229directive. 230.El 231.Pp 232.Sh PACKING LIST DETAILS | 179executable program (or shell script). It will be invoked automatically 180at installation/deinstallation time to determine whether or not 181installation/deinstallation should proceed. 182.It Fl s Ar srcdir 183.Ar srcdir 184will override the value of 185.Cm @cwd 186during package creation. --- 46 unchanged lines hidden (view full) --- 233where 234.Pa prefix 235is the name of the first directory named by a 236.Cm @cwd 237directive. 238.El 239.Pp 240.Sh PACKING LIST DETAILS |
233The ``packing list'' format (see | 241The 242.Dq packing list 243format (see |
234.Fl f ) 235is fairly simple, being 236nothing more than a single column of filenames to include in the 237package. However, since absolute pathnames are generally a bad idea 238for a package that could be installed potentially anywhere, there is 239another method of specifying where things are supposed to go 240and, optionally, what ownership and mode information they should be 241installed with. This is done by imbeding specialized command sequences --- 29 unchanged lines hidden (view full) --- 271Expands to the last filename extracted (as specified), in the example case 272.Pa bin/emacs 273.It Cm "%D" 274Expand to the current directory prefix, as set with 275.Cm @cwd , 276in the example case 277.Pa /usr/local . 278.It Cm "%B" | 244.Fl f ) 245is fairly simple, being 246nothing more than a single column of filenames to include in the 247package. However, since absolute pathnames are generally a bad idea 248for a package that could be installed potentially anywhere, there is 249another method of specifying where things are supposed to go 250and, optionally, what ownership and mode information they should be 251installed with. This is done by imbeding specialized command sequences --- 29 unchanged lines hidden (view full) --- 281Expands to the last filename extracted (as specified), in the example case 282.Pa bin/emacs 283.It Cm "%D" 284Expand to the current directory prefix, as set with 285.Cm @cwd , 286in the example case 287.Pa /usr/local . 288.It Cm "%B" |
279Expand to the ``basename'' of the fully qualified filename, that | 289Expand to the 290.Dq basename 291of the fully qualified filename, that |
280is the current directory prefix, plus the last filespec, minus 281the trailing filename. In the example case, that would be 282.Pa /usr/local/bin . 283.It Cm "%f" | 292is the current directory prefix, plus the last filespec, minus 293the trailing filename. In the example case, that would be 294.Pa /usr/local/bin . 295.It Cm "%f" |
284Expand to the ``filename'' part of the fully qualified name, or | 296Expand to the 297filename 298part of the fully qualified name, or |
285the converse of 286.Cm %B , 287being in the example case, 288.Pa emacs . 289.El 290.It Cm @unexec Ar command 291Execute 292.Ar command --- 4 unchanged lines hidden (view full) --- 297This command is not executed during the package add, as 298.Cm @exec 299is, but rather when the package is deleted. This is useful 300for deleting links and other ancillary files that were created 301as a result of adding the package, but not directly known to 302the package's table of contents (and hence not automatically 303removable). The advantage of using 304.Cm @unexec | 299the converse of 300.Cm %B , 301being in the example case, 302.Pa emacs . 303.El 304.It Cm @unexec Ar command 305Execute 306.Ar command --- 4 unchanged lines hidden (view full) --- 311This command is not executed during the package add, as 312.Cm @exec 313is, but rather when the package is deleted. This is useful 314for deleting links and other ancillary files that were created 315as a result of adding the package, but not directly known to 316the package's table of contents (and hence not automatically 317removable). The advantage of using 318.Cm @unexec |
305over a deinstallation script is that you can use the ``special 306sequence expansion'' to get at files regardless of where they've | 319over a deinstallation script is that you can use the 320.Dq special sequence expansion 321to get at files regardless of where they've |
307been potentially redirected (see 308.Fl p ) . 309.It Cm @mode Ar mode 310Set default permission for all subsequently extracted files to 311.Ar mode . 312Format is the same as that used by the 313.Cm chmod 314command (well, considering that it's later handed off to it, that's --- 148 unchanged lines hidden --- | 322been potentially redirected (see 323.Fl p ) . 324.It Cm @mode Ar mode 325Set default permission for all subsequently extracted files to 326.Ar mode . 327Format is the same as that used by the 328.Cm chmod 329command (well, considering that it's later handed off to it, that's --- 148 unchanged lines hidden --- |