NO_CDROM and NO_PACKAGE set together?

Yar Tikhiy yar at
Fri Jun 4 15:06:49 GMT 2004

On Fri, Jun 04, 2004 at 04:35:47PM +0200, Alex Dupre wrote:
> | Is it all right to set both NO_CDROM and NO_PACKAGE for a port
> | to indicate that mirroring the original distfiles is the only thing
> | allowed by the license?
> Yes.


> | The comments at the top of, and the Porter's Handbook
> | seem to imply that these variables are mutually exclusive.
> I personally reworded that paragraph in the Porter's Handbook to be much
> more clear. And I read in the first note: "NO_PACKAGE and NO_CDROM are
> independent and can be set simultaneously."
> So I don't know how you can say that the handbook seems to imply they
> are mutually exclusive :-)

Alex, I really appreciate what you did, but your approach is known
as "creeping patchism" ;-)  I missed your note clearly because it
was above the paragraphs I was reading, and the latter effectively
imply the exclusiveness :-)  What about rewording them even further?
Here's my version:

	This variable indicates that we may not generate a binary
	package of the application or distribute its modified version
	(since a port often modifies the application source files.)
	However, the port's original DISTFILES may be distributed on
	media unless prohibited by setting NO_CDROM as well.

	6.2.2 NO_CDROM
	This variable alone indicates that, although we are allowed to
	generate binary packages, we are not allowed to put those
	packages, or the port's DISTFILES, onto a CD-ROM (or DVD-ROM)
	for resale. However, the binary packages and the port's
	DISTFILES will still be available via FTP/HTTP. If the
	application's license is even more restricitve and disallows
	any distribution in binary or modified form, NO_PACKAGE should
	be set along with NO_CDROM.

Besides other things, the word "freely" is no longer used since
media distribution usually involves at least covering production
and shipping expences.

P.S. I'd like to commit that by myself so that I'll have my idle
doc commit bit timer reset :-)


More information about the freebsd-ports mailing list