If no paths are specified on the command line, standard input is assumed to be a list of paths. If the path listed on the command line is a directory, the contents of the directory are searched. However, if input is read from stdin, a directory specified as a path will not be searched.
The prototype file attributes mac, fixed, and inherited, cannot be determined by pkgproto; to add these attributes to the prototype file, you must add them to the file manually. See prototype(F).
$ pkgproto /usr/bin=bin /usr/usr/bin=usrbin /etc=etc f none bin/sed=/bin/sed 0775 bin bin f none bin/sh=/bin/sh 0755 bin daemon f none bin/sort=/bin/sort 0755 bin bin d none etc/master.d 0755 root daemon f none etc/master.d/kernel=/etc/master.d/kernel 0644 root daemon f none etc/rc=/etc/rc 0744 root daemon
$ find / -type d -print | pkgproto d none / 755 root root d none /usr/bin 755 bin bin d none /usr 755 root root d none /usr/bin 775 bin bin d none /etc 755 root root d none /tmp 777 root root
Identical to the previous example, but with the output captured in a file for later processing with pkgmk. Entries added for the required pkginfo file, and, for instance, a postinstall script that might be executed after the files are copied into the correct locations.
$ find / -type d -print | pkgproto >prototype $ (edit the file to add entries for pkginfo and postinstall) $ cat prototype i pkginfo i postinstall d none / 755 root root d none /usr/bin 755 bin bin d none /usr 755 root root d none /usr/bin 775 bin bin d none /etc 755 root root d none /tmp 777 root root
The output from this command is sent to standard output. You must redirect standard output to a file if you wish to use the result as a prototype file when invoking pkgmk. Since pkgmk uses prototype as the default filename for the prototype file, we suggest you direct the output of pkgproto to the file name prototype.
Note that you must add entries to the prototype file produced by this command for any installation scripts and files your package may need. At minimum, you will need an entry for the pkginfo file; see pkginfo(F) for more information. You may also need entries for any of the following files you use in your package: copyright, compver, depend, setinfo,space, any installation or removal scripts you define for the package and/or any classes you define. (e.g., postinstall).