reflect permit_package change in porting guide

Hi all,

The porting guide is using the old distribution variables. Here's a
potential fix.

-Pamela


Index: guide.html
===================================================================
RCS file: /cvs/www/faq/ports/guide.html,v
retrieving revision 1.87
diff -u -p -r1.87 guide.html
--- guide.html 28 May 2019 01:53:12 -0000 1.87
+++ guide.html 24 Jun 2019 01:31:54 -0000
@@ -322,23 +322,20 @@ the port and any special options that mi
Now is also a good time to figure out what kind of licensing restrictions
apply to your port.
Many are freely redistributable, but quite a few are not.
-We need three questions answered to distribute ports properly.
+We need two questions answered to distribute ports properly.
These are the <code>PERMIT_*</code> values in the <code>Makefile</code>.

<p>
-<code>PERMIT_PACKAGE_CDROM</code>
-tells us if we can put the package on the cdrom.
+<code>PERMIT_PACKAGE</code>
+tells us whether we can put the package on the mirrors.
<br>
-<code>PERMIT_PACKAGE_FTP</code>
-tells us if we can put the package on the ftp sites.
-<br>
-<code>PERMIT_DISTFILES_FTP</code>
-tells us if we can mirror the distfiles on the ftp sites.
+<code>PERMIT_DISTFILES</code>
+tells us whether we can mirror the distfiles.

<p>
-If all three are permitted, simply set <code>PERMIT_PACKAGE_CDROM=Yes</code>.
-Otherwise include all three variables, set to either <code>Yes</code>, or a
-comment string indicating that certain distribution is not allowed.
+If both are permitted, simply set <code>PERMIT_PACKAGE=Yes</code>.
+Otherwise, set each variable to either <code>Yes</code> or a comment
+string indicating the reason distribution is not allowed.
Pay attention to any special conditions you may need to fulfill later on.
For example, some ports require installing a copy of the license.
We recommend you place the license in