pkgsrc-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[pkgsrc/trunk]: pkgsrc/doc regen
details: https://anonhg.NetBSD.org/pkgsrc/rev/5fedb6a71b6c
branches: trunk
changeset: 495678:5fedb6a71b6c
user: wiz <wiz%pkgsrc.org@localhost>
date: Fri Jun 17 13:00:04 2005 +0000
description:
regen
diffstat:
doc/pkgsrc.html | 38 ++++++++++++++++++--------------------
doc/pkgsrc.txt | 23 +++++++++++++----------
2 files changed, 31 insertions(+), 30 deletions(-)
diffs (112 lines):
diff -r 8ecbfae838ca -r 5fedb6a71b6c doc/pkgsrc.html
--- a/doc/pkgsrc.html Fri Jun 17 12:57:54 2005 +0000
+++ b/doc/pkgsrc.html Fri Jun 17 13:00:04 2005 +0000
@@ -10682,29 +10682,27 @@
<p>When a vulnerability is found, this should be noted
in <code class=
"filename">localsrc/security/advisories/pkg-vulnerabilities</code>,
- and after the commit of that file, it should be copied
- to both <code class=
- "filename">/pub/NetBSD/packages/distfiles/pkg-vulnerabilities</code>
- and <code class=
- "filename">/pub/NetBSD/packages/distfiles/vulnerabilities</code>
- on ftp.NetBSD.org using <code class=
- "filename">localsrc/security/advisories/Makefile</code>.
- In addition, if a <code class=
+ and after committing that file, use
+ <span><strong class="command">make
+ upload</strong></span> in the same directory to update
+ the file on ftp.NetBSD.org.</p>
+
+ <p>After fixing the vulnerability by a patch, its
+ <code class="varname">PKGREVISION</code> should be
+ increased (this is of course not necessary if the
+ problem is fixed by using a newer release of the
+ software). In addition, if a <code class=
"filename">buildlink3.mk</code> file exists for an
- affected package, bumping <code class=
- "varname">PKGREVISION</code> and creating a
- corresponding <code class=
+ affected package, a corresponding <code class=
"varname">BUILDLINK_RECOMMENDED.<em class=
"replaceable"><code>pkg</code></em></code> entry should
- be considered. See <a href="#buildlink" title=
- "Chapter 11. Buildlink methodology">Chapter 11,
- <i>Buildlink methodology</i></a> for more information
- about writing <code class=
- "filename">buildlink3.mk</code> files and <code class=
- "varname">BUILDLINK_*</code> definitions.</p>
+ be added or updated in it.</p>
<p>Also, if the fix should be applied to the stable
pkgsrc branch, be sure to submit a pullup request!</p>
+
+ <p>Binary packages already on ftp.NetBSD.org will be
+ handled semi-automatically by a weekly cron job.</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
@@ -10865,9 +10863,6 @@
"varname">${ECHO}</code>). As of this writing, the
following packages use this: <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional"; href=
- "ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/audio/realplayer/README.html";
- class="pkgname">audio/realplayer</a>, <a xmlns=
- "http://www.w3.org/TR/xhtml1/transitional"; href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/cad/simian/README.html";
class="pkgname">cad/simian</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional"; href=
@@ -10880,6 +10875,9 @@
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/fonts/acroread-jpnfont/README.html";
class="pkgname">fonts/acroread-jpnfont</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional"; href=
+ "ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/multimedia/realplayer/README.html";
+ class="pkgname">multimedia/realplayer</a>, <a xmlns=
+ "http://www.w3.org/TR/xhtml1/transitional"; href=
"ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/sysutils/storage-manager/README.html";
class="pkgname">sysutils/storage-manager</a>, <a xmlns=
"http://www.w3.org/TR/xhtml1/transitional"; href=
diff -r 8ecbfae838ca -r 5fedb6a71b6c doc/pkgsrc.txt
--- a/doc/pkgsrc.txt Fri Jun 17 12:57:54 2005 +0000
+++ b/doc/pkgsrc.txt Fri Jun 17 13:00:04 2005 +0000
@@ -4325,18 +4325,21 @@
15.1.8. Handling packages with security problems
When a vulnerability is found, this should be noted in localsrc/security/
-advisories/pkg-vulnerabilities, and after the commit of that file, it should be
-copied to both /pub/NetBSD/packages/distfiles/pkg-vulnerabilities and /pub/
-NetBSD/packages/distfiles/vulnerabilities on ftp.NetBSD.org using localsrc/
-security/advisories/Makefile. In addition, if a buildlink3.mk file exists for
-an affected package, bumping PKGREVISION and creating a corresponding
-BUILDLINK_RECOMMENDED.pkg entry should be considered. See Chapter 11, Buildlink
-methodology for more information about writing buildlink3.mk files and
-BUILDLINK_* definitions.
+advisories/pkg-vulnerabilities, and after committing that file, use make upload
+in the same directory to update the file on ftp.NetBSD.org.
+
+After fixing the vulnerability by a patch, its PKGREVISION should be increased
+(this is of course not necessary if the problem is fixed by using a newer
+release of the software). In addition, if a buildlink3.mk file exists for an
+affected package, a corresponding BUILDLINK_RECOMMENDED.pkg entry should be
+added or updated in it.
Also, if the fix should be applied to the stable pkgsrc branch, be sure to
submit a pullup request!
+Binary packages already on ftp.NetBSD.org will be handled semi-automatically by
+a weekly cron job.
+
15.1.9. How to handle compiler bugs
Some source files trigger bugs in the compiler, based on combinations of
@@ -4396,8 +4399,8 @@
you can set _FETCH_MESSAGE to a macro which displays a message explaining the
situation. _FETCH_MESSAGE must be executable shell commands, not just a
message. (Generally, it executes ${ECHO}). As of this writing, the following
-packages use this: audio/realplayer, cad/simian, devel/ipv6socket, emulators/
-vmware-module, fonts/acroread-jpnfont, sysutils/storage-manager, www/
+packages use this: cad/simian, devel/ipv6socket, emulators/vmware-module, fonts
+/acroread-jpnfont, multimedia/realplayer, sysutils/storage-manager, www/
ap-aolserver, www/openacs. Try to be consistent with them.
15.2.2. How to handle modified distfiles with the 'old' name
Home |
Main Index |
Thread Index |
Old Index