reflect permit_package change in porting guide

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

reflect permit_package change in porting guide

Pamela Mosiejczuk-2
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


Reply | Threaded
Open this post in threaded view
|

Re: reflect permit_package change in porting guide

Daniel Jakots-6
On Sun, 23 Jun 2019 21:53:50 -0400, Pamela Mosiejczuk
<[hidden email]> wrote:

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

While the website usually is for -release/stable, in the ports guide we
say (or we should say :p) that work is done on -current therefor I
think it makes sense to update the guide now (instead of waiting for
6.6 like the FAQ does).
ok danj@

Cheers,
Daniel

Reply | Threaded
Open this post in threaded view
|

Re: reflect permit_package change in porting guide

Klemens Nanni-2
On Sun, Jun 23, 2019 at 10:40:12PM -0400, Daniel Jakots wrote:
> While the website usually is for -release/stable, in the ports guide we
> say (or we should say :p) that work is done on -current therefor I
> think it makes sense to update the guide now (instead of waiting for
> 6.6 like the FAQ does).
Yup, I do revisit the guide from time to time when porting myself and
there really is no reason to package stuff against stable releases, so
it should indeed contain the latest information and guidelines.

Reply | Threaded
Open this post in threaded view
|

Re: reflect permit_package change in porting guide

Solene Rapenne
In reply to this post by Daniel Jakots-6
On Sun, Jun 23, 2019 at 10:40:12PM -0400, Daniel Jakots wrote:

> On Sun, 23 Jun 2019 21:53:50 -0400, Pamela Mosiejczuk
> <[hidden email]> wrote:
>
> > The porting guide is using the old distribution variables. Here's a
> > potential fix.
>
> While the website usually is for -release/stable, in the ports guide we
> say (or we should say :p) that work is done on -current therefor I
> think it makes sense to update the guide now (instead of waiting for
> 6.6 like the FAQ does).
> ok danj@
>
> Cheers,
> Daniel
>
I agree