alternate way to perform basic package installation on a running
system, in addition to the pkg_* tools.
PR: docs/128128
Submitted by: Boris Hollas <boris.hollas@gmx.de>
- s/Pentium IV/Pentium 4 to match Intel syntax;
- Some rewordings for clarification of some points;
- Add reference to sha256(1).
PR: docs/114272
Submitted by: Ben Kaduk <minimarmot@gmail.com>
- Use the word of package instead of port when we talk about
pkg_add(1)
- Mention that recent versions of Portsnap do not require the user to
create manually /usr/ports
- Punctuation fix
- Remove the whole make deinstall business. Tell people to run pkg_delete
directly
- Move Ports and Disk Space after Upgrading Ports; count on people installing
Portupgrade in Upgrading text, I'm showing some portupgrade utilities there.
The section is rewritten anyway.
- Start Upgrading text with mention of pkg_version -v
- Cut the awfully informal chatter at the beginning of Upgrading text
- Reword the rest of Upgrading text, add examples in there
- Mention pkgdb -F earlier, kill <note>
- Suggest portsclean -C for mass cleaning
- Suggest portsclean -D for distfile cleanup
- Mention pkg_cutleaves tool
- Collapse the CD-ROM and Internet instructions into single text; assume
people have Internet access.
- Suggest people using `make clean' after each installation
- Remove bash from the text about using `rehash', recent bash does not need it
- Move the interesting bits of CD-ROM instructions down and update them
to match existing FreeBSDMall product line
- move the CVSup Method to top and Sysinstall Method to bottom
- suggest people to not use Sysinstall method unless they got no Internet
access
- add the Portsnap Method, adapted from the Appendix section on the Portsnap
to GNATS instead of the mailing lists or the Porter's Handbook. Also
provide links to the How To Write Problem Reports article, the mailing
list article, and the mirror list. Finally, add text trying to explain
the difference between maintained and unmaintained ports.
Glanced over by: simon
- We currently state "Install the net/cvsup port"; let's point directly
to the package, in particular cvsup-without-gui since all commands, in
the text, used the legacy "-g"...
- Most of people do not edit the ports-supfile and directly use the -h
argument for the CVSup server, the reader should uses/knows that.
- Keep, as note, the ports-supfile edition for a "hardcoded" CVSup
server
- I kept the odd <link linkend/<xref linkend way, maybe this should be
fixed
The text should, now, be closer to what we do when it's time to CVSup
the Ports tree.
