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

doc/guide: migrate from http to https

Browse source
This commit is contained in:
rillig 2020-02-24 21:13:56 +00:00
parent d95a60f17a
commit dc870f2ad4
13 changed files with 62 additions and 62 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/guide/files/build.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: build.xml,v 1.79 2019/05/05 18:36:05 rillig Exp $ -->
<!-- $NetBSD: build.xml,v 1.80 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="build">
<title>The build process</title>
@ -210,8 +210,8 @@ DISTFILES= ${DEFAULT_DISTFILES} additional-files.tar.gz
DISTFILES= ${DISTNAME}${EXTRACT_SUFX}
DISTFILES+= foo-file.tar.gz
SITES.foo-file.tar.gz= \
http://www.somewhere.com/somehow/ \
http://www.somewhereelse.com/mirror/somehow/
https://www.somewhere.com/somehow/ \
https://www.somewhereelse.com/mirror/somehow/
</programlisting>
<para>When actually fetching the distfiles, each item from
@ -225,7 +225,7 @@ http://www.somewhereelse.com/mirror/somehow/
case, the definition would look like:</para>
<programlisting>
MASTER_SITES= http://www.example.com/download.cgi?file=
MASTER_SITES= https://www.example.com/download.cgi?file=
</programlisting>
<para> The exception to this rule are URLs starting with a dash.
@ -241,7 +241,7 @@ MASTER_SITES= http://www.example.com/download.cgi?file=
<programlisting>
DISTNAME= foo-1.0.0
MASTER_SITES= -http://www.example.com/archive/v1.0.0.tar.gz
MASTER_SITES= -https://www.example.com/archive/v1.0.0.tar.gz
</programlisting>
<para>There are some predefined values for

4
doc/guide/files/debug.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: debug.xml,v 1.7 2007/08/15 06:33:44 rillig Exp $ -->
<!-- $NetBSD: debug.xml,v 1.8 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="debug">
<title>Debugging</title>
@ -20,7 +20,7 @@
<screen>&cprompt; <userinput>mkdir /usr/pkgsrc/<replaceable>category</replaceable>/<replaceable>examplepkg</replaceable></userinput>
&cprompt; <userinput>cd /usr/pkgsrc/<replaceable>category</replaceable>/<replaceable>examplepkg</replaceable></userinput>
&cprompt; <userinput>url2pkg http://www.example.com/path/to/distfile.tar.gz</userinput></screen>
&cprompt; <userinput>url2pkg https://www.example.com/path/to/distfile.tar.gz</userinput></screen>
</listitem>
<listitem>

10
doc/guide/files/devfaq.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: devfaq.xml,v 1.15 2020/02/23 17:43:20 rillig Exp $ -->
<!-- $NetBSD: devfaq.xml,v 1.16 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="devfaq"> <?dbhtml filename="devfaq.html"?>
<title>Frequently Asked Questions</title>
@ -105,7 +105,7 @@
<answer><variablelist>
<varlistentry><term><ulink
url="http://www.NetBSD.org/mailinglists/index.html#tech-pkg">tech-pkg</ulink></term>
url="https://www.NetBSD.org/mailinglists/index.html#tech-pkg">tech-pkg</ulink></term>
<listitem><para>This is a list for technical discussions related
to pkgsrc development, e.g. soliciting feedback for changes to
@ -116,7 +116,7 @@
etc.</para></listitem></varlistentry>
<varlistentry><term><ulink
url="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs">pkgsrc-bugs</ulink></term>
url="https://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs">pkgsrc-bugs</ulink></term>
<listitem><para>All bug reports in category "pkg" sent with
&man.send-pr.1; appear here. Please do not report your bugs here
@ -142,7 +142,7 @@
say.</para></listitem>
<listitem><para>On the mailing list archives (see <ulink
url="http://mail-index.NetBSD.org/"/>), you can find discussions
url="https://mail-index.NetBSD.org/"/>), you can find discussions
about certain features, announcements of new parts of the pkgsrc
infrastructure and sometimes even announcements that a certain
feature has been marked as obsolete. The benefit here is that
@ -199,7 +199,7 @@ anyway.</para>
have.</para></listitem>
<listitem><para>Review packages for which review was requested on
the <ulink url="http://www.NetBSD.org/mailinglists/index.html#tech-pkg">tech-pkg</ulink>
the <ulink url="https://www.NetBSD.org/mailinglists/index.html#tech-pkg">tech-pkg</ulink>
mailing list.</para></listitem>
</itemizedlist>
</answer></qandaentry>

8
doc/guide/files/editing.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: editing.xml,v 1.15 2013/03/26 20:21:38 wiz Exp $ -->
<!-- $NetBSD: editing.xml,v 1.16 2020/02/24 21:13:56 rillig Exp $ -->
<appendix id="editing">
<title>Editing guidelines for the pkgsrc guide</title>
@ -20,14 +20,14 @@
<listitem><para><filename>pkgsrc/doc/pkgsrc.html</filename></para></listitem>
<listitem><para><ulink
url="http://www.NetBSD.org/docs/pkgsrc/"/></para></listitem>
url="https://www.NetBSD.org/docs/pkgsrc/"/></para></listitem>
<listitem><para><ulink
url="http://www.NetBSD.org/docs/pkgsrc/pkgsrc.pdf"/>:
url="https://www.NetBSD.org/docs/pkgsrc/pkgsrc.pdf"/>:
The PDF version of the pkgsrc guide.</para></listitem>
<listitem><para><ulink
url="http://www.NetBSD.org/docs/pkgsrc/pkgsrc.ps"/>:
url="https://www.NetBSD.org/docs/pkgsrc/pkgsrc.ps"/>:
PostScript version of the pkgsrc guide.</para></listitem>
</itemizedlist>

4
doc/guide/files/examples.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: examples.xml,v 1.18 2020/02/15 10:29:49 rillig Exp $ -->
<!-- $NetBSD: examples.xml,v 1.19 2020/02/24 21:13:56 rillig Exp $ -->
<appendix id="examples">
<title>A simple example package: bison</title>
@ -24,7 +24,7 @@ CATEGORIES= devel
MASTER_SITES= ${MASTER_SITE_GNU:=bison/}
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= http://www.gnu.org/software/bison/bison.html
HOMEPAGE= https://www.gnu.org/software/bison/bison.html
COMMENT= GNU yacc clone
GNU_CONFIGURE= yes

8
doc/guide/files/faq.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: faq.xml,v 1.56 2020/02/09 00:44:25 rillig Exp $ -->
<!-- $NetBSD: faq.xml,v 1.57 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="faq"> <?dbhtml filename="faq.html"?>
<title>Frequently Asked Questions</title>
@ -31,14 +31,14 @@ it contains items for both pkgsrc users and developers.</para>
<listitem>
<para><ulink
url="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bulk">pkgsrc-bulk</ulink>:
url="https://www.NetBSD.org/mailinglists/index.html#pkgsrc-bulk">pkgsrc-bulk</ulink>:
A list where the results of pkgsrc bulk builds are sent and
discussed.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-changes">pkgsrc-changes</ulink>:
url="https://www.NetBSD.org/mailinglists/index.html#pkgsrc-changes">pkgsrc-changes</ulink>:
This list is for those who are interested in getting a
commit message for every change committed to pkgsrc. It is
also available in digest form, meaning one daily message
@ -55,7 +55,7 @@ it contains items for both pkgsrc users and developers.</para>
</programlisting>
<para>Archives for all these mailing lists are available from
<ulink url="http://mail-index.NetBSD.org/"/>.</para>
<ulink url="https://mail-index.NetBSD.org/"/>.</para>
</sect1>

8
doc/guide/files/fixes.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: fixes.xml,v 1.153 2020/02/23 17:27:29 rillig Exp $ -->
<!-- $NetBSD: fixes.xml,v 1.154 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="fixes"> <?dbhtml filename="fixes.html"?>
<title>Making your package work</title>
@ -823,7 +823,7 @@ FETCH_MESSAGE+= "manually from "${MASTER_SITES:Q}"."
<title>Fetch based on a tagged release</title>
<para>If your distfile URL looks similar to
<literal>http://github.com/username/exampleproject/archive/v1.0.zip</literal>,
<literal>https://github.com/username/exampleproject/archive/v1.0.zip</literal>,
then you are packaging a tagged release.</para>
<programlisting>
@ -840,7 +840,7 @@ EXTRACT_SUFX= .zip
<title>Fetch based on a specific commit</title>
<para>If your distfile URL looks similar to
<literal>http://github.com&#x200B;/example&#x200B;/example&#x200B;/archive&#x200B;/988881adc9fc3655077dc2d4d757d480b5ea0e11.tar.gz</literal>,
<literal>https://github.com&#x200B;/example&#x200B;/example&#x200B;/archive&#x200B;/988881adc9fc3655077dc2d4d757d480b5ea0e11.tar.gz</literal>,
then you are packaging a specific commit not tied to a
release.</para>
@ -857,7 +857,7 @@ GITHUB_TAG= 988881adc9fc3655077dc2d4d757d480b5ea0e11
<title>Fetch based on release</title>
<para>If your distfile URL looks similar to
<literal>http://github.com&#x200B;/username/exampleproject&#x200B;/releases&#x200B;/download&#x200B;/rel-1.6&#x200B;/offensive-1.6.zip</literal>,
<literal>https://github.com&#x200B;/username/exampleproject&#x200B;/releases&#x200B;/download&#x200B;/rel-1.6&#x200B;/offensive-1.6.zip</literal>,
then you are packaging a release.</para>
<programlisting>

4
doc/guide/files/getting.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: getting.xml,v 1.37 2019/05/03 10:35:37 sevan Exp $ -->
<!-- $NetBSD: getting.xml,v 1.38 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="getting">
<title>Where to get pkgsrc and how to keep it up-to-date</title>
@ -102,7 +102,7 @@ and dashes.</para>
<screen>&uprompt; <userinput>cd /usr &amp;&amp; cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc</userinput>
</screen>
<para>Refer to the <ulink url="http://www.NetBSD.org/mirrors/#anoncvs">list of available mirrors</ulink> to choose a faster CVS mirror, if needed.</para>
<para>Refer to the <ulink url="https://www.NetBSD.org/mirrors/#anoncvs">list of available mirrors</ulink> to choose a faster CVS mirror, if needed.</para>
<!-- FIXME: All this CVS magic should move into appendix or so. -->
<para>If you get error messages from <literal>rsh</literal>, you need to set CVS_RSH variable. E.g.:</para>

14
doc/guide/files/gnome.xml
View file

@ -1,9 +1,9 @@
<!-- $NetBSD: gnome.xml,v 1.10 2016/07/09 16:07:35 rillig Exp $ -->
<!-- $NetBSD: gnome.xml,v 1.11 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="gnome"> <?dbhtml filename="gnome.html"?>
<title>GNOME packaging and porting</title>
<para>Quoting <ulink url="http://www.gnome.org/">GNOME's web
<para>Quoting <ulink url="https://www.gnome.org/">GNOME's web
site</ulink>:</para>
<blockquote>
@ -23,10 +23,10 @@ achieving a completely clean deinstallation of installed software
components.</para>
<para>Given that pkgsrc is <ulink
url="http://www.NetBSD.org/">NetBSD</ulink>'s official packaging system,
url="https://www.NetBSD.org/">NetBSD</ulink>'s official packaging system,
the above also means that great efforts are put into making GNOME work
under this operating system. Recently, <ulink
url="http://www.dragonflybsd.org/">DragonFly BSD</ulink> also adopted
url="https://www.dragonflybsd.org/">DragonFly BSD</ulink> also adopted
pkgsrc as its preferred packaging system, contributing lots of
portability fixes to make GNOME build and install under it.</para>
@ -41,7 +41,7 @@ important information regarding their internals.</para>
<para>Should you have some spare cycles to devote to NetBSD, pkgsrc
and GNOME and are willing to learn new exciting stuff, please jump
straight to the <ulink
url="http://www.NetBSD.org/contrib/projects.html#gnome">pending
url="https://www.NetBSD.org/contrib/projects.html#gnome">pending
work</ulink> list! There is still a long way to go to get a
fully-functional GNOME desktop under NetBSD and we need your help to
achieve it!</para>
@ -355,8 +355,8 @@ pkgsrc, the easier further updates are. Those developers in charge of
issuing major GNOME updates will be grateful if you do that.</para>
<para>The most common places to report bugs are the <ulink
url="http://bugzilla.gnome.org/">GNOME's Bugzilla</ulink> and the <ulink
url="http://bugzilla.freedesktop.org/">freedesktop.org's
url="https://bugzilla.gnome.org/">GNOME's Bugzilla</ulink> and the <ulink
url="https://bugzilla.freedesktop.org/">freedesktop.org's
Bugzilla</ulink>. Not all components use these to track bugs, but most
of them do. Do not be short on your reports: always provide detailed
explanations of the current failure, how it can be improved to achieve

32
doc/guide/files/introduction.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: introduction.xml,v 1.43 2019/04/03 23:49:07 sevan Exp $ -->
<!-- $NetBSD: introduction.xml,v 1.44 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="introduction">
<title>What is pkgsrc?</title>
@ -128,7 +128,7 @@ minutes!</para>
</thead>
<tbody>
<row>
<entry><ulink url="http://www.NetBSD.org/">NetBSD</ulink></entry>
<entry><ulink url="https://www.NetBSD.org/">NetBSD</ulink></entry>
<entry align="center">Aug 1997</entry>
</row>
<row>
@ -137,7 +137,7 @@ minutes!</para>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Solaris">README.Solaris</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.kernel.org/">Linux</ulink></entry>
<entry><ulink url="https://www.kernel.org/">Linux</ulink></entry>
<entry align="center">Jun 1999</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Linux">README.Linux</ulink></entry>
</row>
@ -149,17 +149,17 @@ minutes!</para>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.MacOSX">README.MacOSX</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.freebsd.org/">FreeBSD</ulink></entry>
<entry><ulink url="https://www.freebsd.org/">FreeBSD</ulink></entry>
<entry align="center">Nov 2002</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.FreeBSD">README.FreeBSD</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.openbsd.org/">OpenBSD</ulink></entry>
<entry><ulink url="https://www.openbsd.org/">OpenBSD</ulink></entry>
<entry align="center">Nov 2002</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.OpenBSD">README.OpenBSD</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.sgi.com/software/irix/">IRIX</ulink></entry>
<entry><ulink url="https://www.sgi.com/software/irix/">IRIX</ulink></entry>
<entry align="center">Dec 2002</entry>
<entry>
<ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.IRIX">README.IRIX</ulink>
@ -171,20 +171,20 @@ minutes!</para>
<entry align="center">Dec 2003</entry>
</row>
<row>
<entry><ulink url="http://www-1.ibm.com/servers/aix/">AIX</ulink></entry>
<entry><ulink url="https://www-1.ibm.com/servers/aix/">AIX</ulink></entry>
<entry align="center">Dec 2003</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.AIX">README.AIX</ulink></entry>
</row>
<row>
<entry>
<ulink url="http://www.microsoft.com/windows/sfu/">Interix</ulink>
<ulink url="https://www.microsoft.com/windows/sfu/">Interix</ulink>
(Microsoft Windows Services for Unix)
</entry>
<entry align="center">Mar 2004</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Interix">README.Interix</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.dragonflybsd.org/">DragonFlyBSD</ulink></entry>
<entry><ulink url="https://www.dragonflybsd.org/">DragonFlyBSD</ulink></entry>
<entry align="center">Oct 2004</entry>
</row>
<row>
@ -193,36 +193,36 @@ minutes!</para>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.OSF1">README.OSF1</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.hp.com/products1/unix/">HP-UX</ulink></entry>
<entry><ulink url="https://www.hp.com/products1/unix/">HP-UX</ulink></entry>
<entry align="center">Apr 2007</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.HPUX">README.HPUX</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.haiku-os.org/">Haiku</ulink></entry>
<entry><ulink url="https://www.haiku-os.org/">Haiku</ulink></entry>
<entry align="center">Sep 2010</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Haiku">README.Haiku</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.mirbsd.org/">MirBSD</ulink></entry>
<entry><ulink url="https://www.mirbsd.org/">MirBSD</ulink></entry>
<entry align="center">Jan 2011</entry>
</row>
<row>
<entry><ulink url="http://www.minix3.org/">Minix3</ulink></entry>
<entry><ulink url="https://www.minix3.org/">Minix3</ulink></entry>
<entry align="center">Nov 2011</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Minix3">README.Minix3</ulink></entry>
</row>
<row>
<entry><ulink url="http://cygwin.com/">Cygwin</ulink></entry>
<entry><ulink url="https://cygwin.com/">Cygwin</ulink></entry>
<entry align="center">Mar 2013</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Cygwin">README.Cygwin</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.debian.org/ports/kfreebsd-gnu/">GNU/kFreeBSD</ulink></entry>
<entry><ulink url="https://www.debian.org/ports/kfreebsd-gnu/">GNU/kFreeBSD</ulink></entry>
<entry align="center">Jul 2013</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.GNUkFreeBSD">README.GNUkFreeBSD</ulink></entry>
</row>
<row>
<entry><ulink url="http://www.bitrig.org/">Bitrig</ulink></entry>
<entry><ulink url="https://www.bitrig.org/">Bitrig</ulink></entry>
<entry align="center">Jun 2014</entry>
<entry><ulink url="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Bitrig">README.Bitrig</ulink></entry>
</row>

4
doc/guide/files/regression.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: regression.xml,v 1.8 2020/01/11 11:50:51 rillig Exp $ -->
<!-- $NetBSD: regression.xml,v 1.9 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="regression"> <?dbhtml filename="regression.html"?>
<title>Regression tests</title>
@ -39,7 +39,7 @@
<para>These functions do not take any parameters. Although they
are called in <quote>set -e</quote> mode, they don't stop at the
first failing command. See <ulink
url="http://stackoverflow.com/q/4072984">this Stack Overflow
url="https://stackoverflow.com/q/4072984">this Stack Overflow
question</ulink> for details.</para>
<variablelist>

8
doc/guide/files/submit.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: submit.xml,v 1.34 2020/01/05 21:35:33 rillig Exp $ -->
<!-- $NetBSD: submit.xml,v 1.35 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="submit"> <?dbhtml filename="submit.html"?>
<title>Submitting and Committing</title>
@ -26,7 +26,7 @@
Finally, send this package 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="http://www.NetBSD.org/support/send-pr.html"/>,
<ulink url="https://www.NetBSD.org/support/send-pr.html"/>,
which contains some instructions and a link to a form where you
can submit packages. The
<filename role="pkg">sysutils/gtk-send-pr</filename> package is
@ -46,7 +46,7 @@
<para>Alternatively, you can also import new packages into
pkgsrc-wip (<quote>pkgsrc work-in-progress</quote>); see the
homepage at <ulink url="http://pkgsrc.org/wip/"/>
homepage at <ulink url="https://pkgsrc.org/wip/"/>
for details.</para>
</sect1>
@ -59,7 +59,7 @@
important to keep this file up to date and conforming to the
existing format, because it will be used by scripts to
automatically update pages on <ulink
url="http://www.NetBSD.org/">www.NetBSD.org</ulink> and other
url="https://www.NetBSD.org/">www.NetBSD.org</ulink> and other
sites. Additionally, check the
<filename>pkgsrc/doc/TODO</filename> file and remove the entry
for the package you updated or removed, in case it was mentioned

10
doc/guide/files/using.xml
View file

@ -1,4 +1,4 @@
<!-- $NetBSD: using.xml,v 1.49 2020/01/19 13:38:42 rillig Exp $ -->
<!-- $NetBSD: using.xml,v 1.50 2020/02/24 21:13:56 rillig Exp $ -->
<chapter id="using"> <?dbhtml filename="using.html"?>
<title>Using pkgsrc</title>
@ -67,7 +67,7 @@ and you can still use binary packages from someone else.</para>
<screen>
&rprompt; <userinput>PATH="/usr/pkg/sbin:$PATH"</userinput>
&rprompt; <userinput>PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages"</userinput>
&rprompt; <userinput>PKG_PATH="https://cdn.NetBSD.org/pub/pkgsrc/packages"</userinput>
&rprompt; <userinput>PKG_PATH="$PKG_PATH/<replaceable>OPSYS</replaceable>/<replaceable>ARCH</replaceable>/<replaceable>VERSIONS</replaceable>/All/"</userinput>
&rprompt; <userinput>export PATH PKG_PATH</userinput>
</screen>
@ -143,7 +143,7 @@ and you can still use binary packages from someone else.</para>
The pkgsrc Security Team and Packages Groups maintain a list of
known security vulnerabilities to packages which are (or have been)
included in pkgsrc. The list is available from the NetBSD
FTP site at <ulink url="http://ftp.NetBSD.org/pub/NetBSD/packages/vulns/pkg-vulnerabilities"/>.
FTP site at <ulink url="https://ftp.NetBSD.org/pub/NetBSD/packages/vulns/pkg-vulnerabilities"/>.
</para>
<para>
@ -164,11 +164,11 @@ and you can still use binary packages from someone else.</para>
</para>
<screen>Package samba-2.0.9 has a local-root-shell vulnerability, see
http://www.samba.org/samba/whatsnew/macroexploit.html</screen>
https://www.samba.org/samba/whatsnew/macroexploit.html</screen>
<para>
You may wish to have the
<ulink url="http://ftp.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities">vulnerabilities</ulink>
<ulink url="https://ftp.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities">vulnerabilities</ulink>
file downloaded daily so that
it remains current. This may be done by adding an appropriate entry
to the root users &man.crontab.5; entry. For example the entry