New NO_{SRC,BIN}_ON_{FTP,CDROM}

[David Brownlee]

Does this mean we can start ignoring the RESTRICTED variable
for packages on ftp.netbsd.org - providing we document the
fact it may contain NO_BIN_ON_CDROM packages, and packages
which may have crypto restrictions?

David/absolute
-- www.netbsd.org: A pmap for every occasion --

On Thu, 20 Jul 2000 mcma...@mtl.mit.edu wrote:

>
>
> good. we should add lintpkgsrc options to handle these. That way we can
> make the huge bunch of noise at the end of my weekly-pkgsrc script be more
> meaningful.
>
> Thanks
> -Dan
>
> On Thu, 20 Jul 2000, Rene Hexel wrote:
>
> >
> > Module Name: pkgsrc
> > Committed By: rh
> > Date: Thu Jul 20 12:33:44 UTC 2000
> >
> > Modified Files:
> > pkgsrc/mk: bsd.pkg.mk
> >
> > Log Message:
> > Introduce NO_{SRC,BIN}_ON_{FTP,CDROM}. Warn about placing files on CD-ROM
> > or ftp during 'make package' or 'make mirror-distfiles'.
> >
> >
> > To generate a diff of this commit:
> > cvs rdiff -r1.511 -r1.512 pkgsrc/mk/bsd.pkg.mk
> >
> > Please note that diffs are not public domain; they are subject to the
> > copyright notices on the relevant files.
> >
>
>

[Dr. Rene Hexel]

David Brownlee wrote:
>
> Does this mean we can start ignoring the RESTRICTED variable
> for packages on ftp.netbsd.org - providing we document the
> fact it may contain NO_BIN_ON_CDROM packages, and packages
> which may have crypto restrictions?

I believe so, yes.

Cheers
,
Rene

[Hubert Feyrer]

On Thu, 20 Jul 2000, David Brownlee wrote:
> Does this mean we can start ignoring the RESTRICTED variable
> for packages on ftp.netbsd.org - providing we document the
> fact it may contain NO_BIN_ON_CDROM packages, and packages
> which may have crypto restrictions?

I'd say we keep RESTRICTED (the pkg is, after all), and set NO_whatever
from it:

RESTRICTED= 'reason'
NO_BIN_ON_CDROM= ${RESTRICTED}
NO_SRC_ON_CDROM= ${RESTRICTED}

- Hubert

--
NetBSD - because Unix isn't just #include <linux.h>, i386, ILP32, ELF, ...!