CVS commit: pkgsrc/doc/guide/files

["Nia Alarie" <nia%netbsd.org@localhost>]

Module Name:    pkgsrc
Committed By:   nia
Date:           Fri Feb 11 08:02:05 UTC 2022

Modified Files:
        pkgsrc/doc/guide/files: hardening.xml submit.xml

Log Message:
Advise against using eencoded email attachments.


To generate a diff of this commit:
cvs rdiff -u -r1.6 -r1.7 pkgsrc/doc/guide/files/hardening.xml
cvs rdiff -u -r1.37 -r1.38 pkgsrc/doc/guide/files/submit.xml

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: pkgsrc/doc/guide/files/hardening.xml
diff -u pkgsrc/doc/guide/files/hardening.xml:1.6 pkgsrc/doc/guide/files/hardening.xml:1.7
--- pkgsrc/doc/guide/files/hardening.xml:1.6    Mon Nov  8 22:16:21 2021
+++ pkgsrc/doc/guide/files/hardening.xml        Fri Feb 11 08:02:05 2022
@@ -1,4 +1,4 @@
-<!-- $NetBSD: hardening.xml,v 1.6 2021/11/08 22:16:21 gutteridge Exp $ -->
+<!-- $NetBSD: hardening.xml,v 1.7 2022/02/11 08:02:05 nia Exp $ -->
 
 <appendix id="hardening">
 <title>Security hardening</title>
@@ -195,8 +195,8 @@ precede the program's own data sections,
 <listitem>
 <para>
 full: in addition to partial RELRO, every relocation is performed immediately
-when starting the program (with a slight performance impact), allowing the
-entire GOT to be read-only.
+when starting the program, allowing the entire GOT to be read-only.  This
+can greatly slow down startup of large programs.
 </para>
 </listitem>
 </itemizedlist>

Index: pkgsrc/doc/guide/files/submit.xml
diff -u pkgsrc/doc/guide/files/submit.xml:1.37 pkgsrc/doc/guide/files/submit.xml:1.38
--- pkgsrc/doc/guide/files/submit.xml:1.37      Sat Jun 20 05:31:10 2020
+++ pkgsrc/doc/guide/files/submit.xml   Fri Feb 11 08:02:05 2022
@@ -1,4 +1,4 @@
-<!-- $NetBSD: submit.xml,v 1.37 2020/06/20 05:31:10 rillig Exp $ -->
+<!-- $NetBSD: submit.xml,v 1.38 2022/02/11 08:02:05 nia Exp $ -->
 
 <chapter id="submit"> <?dbhtml filename="submit.html"?>
 <title>Submitting and Committing</title>
@@ -19,11 +19,17 @@
 <sect1 id="submitting-your-package">
 <title>Submitting source packages (for non-NetBSD-developers)</title>
 
-       <para>First, check that your package is complete, compiles and
+       <para>Firstly, you can import new packages into
+       pkgsrc-wip (<quote>pkgsrc work-in-progress</quote>); see the
+       homepage at <ulink url="https://pkgsrc.org/wip/"/>
+       for details.</para>
+
+       <para>Next, check that your package is complete, compiles and
        runs well; see <xref linkend="creating"/> and the rest of this
-       document. Next, generate an uuencoded gzipped &man.tar.1;
-       archive that contains all files that make up the package.
-       Finally, send this package to the pkgsrc bug tracking system,
+       document. Run the <filename role="pkg">pkgtools/pkglint</filename>
+       tool and fix any errors that appear.</para>
+
+       <para>Finally, send a report to the pkgsrc bug tracking system,
        either with the &man.send-pr.1; command, or if you don't have
        that, go to the web page
        <ulink url="https://www.NetBSD.org/support/send-pr.html"/>,
@@ -37,18 +43,7 @@
        <quote>pkg</quote>, the synopsis should include the package name
        and version number, and the description field should contain a
        short description of your package (contents of the COMMENT
-       variable or DESCR file are OK). The uuencoded package data should
-       go into the <quote>fix</quote> field.</para>
-
-       <para>If you want to submit several packages, please send a
-       separate PR for each one, it's easier for us to track things
-       that way.</para>
-
-       <para>Alternatively, you can also import new packages into
-       pkgsrc-wip (<quote>pkgsrc work-in-progress</quote>); see the
-       homepage at <ulink url="https://pkgsrc.org/wip/"/>
-       for details.</para>
-
+       variable or DESCR file are OK).</para>
 </sect1>
 
 <sect1 id="general-notes-for-changes">