kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Document that the upload script takes care of vulnerable

Browse source 
and restricted packages automatically.
Use more man page entities, now that we have them.
This commit is contained in:
wiz 2005-05-08 13:52:17 +00:00
parent 56dffda7c7
commit 70eff6e059
1 changed files with 7 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/guide/files/binary.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: binary.xml,v 1.10 2005/05/07 22:28:15 wiz Exp $ -->
<!-- $NetBSD: binary.xml,v 1.11 2005/05/08 13:52:17 wiz Exp $ -->
<chapter id="binary">
<title>Creating binary packages</title>
@ -102,7 +102,7 @@ _ACCEPTABLE= yes</programlisting>
stage. If the file
<filename>pre-build.local</filename> exists in
<filename>/usr/pkgsrc/mk/bulk</filename>, it will be executed
(as a sh(1) script) at the end of the usual pre-build
(as a &man.sh.1; script) at the end of the usual pre-build
stage. An example use of
<filename>pre-build.local</filename> is to have the line:</para>
@ -527,8 +527,11 @@ chroot-&rprompt; <userinput>cat $HOME/.ssh/id-dsa.pub</userinput> </screen>
&rprompt; <userinput>sh mk/bulk/do-sandbox-upload</userinput> </screen>
<para>
The upload process may take quite some time. Use "ls" or "du"
on the FTP server to monitor progress of the upload.
The upload process may take quite some time. Use &man.ls.1; or
&man.du.1; on the FTP server to monitor progress of the
upload. The upload script will take care of not uploading
restricted packages and putting vulnerable packages into the
<filename>vulnerable</filename> subdirectory.
</para>
<para>