ae9b935fd0
then automatically generate a PLIST that says "${PKGNAME} has no files".
* If PLIST_SRC and GENERATE_PLIST are not set in a package Makefile,
and no PLIST files exist, then fail during the package build with
PKG_FAIL_REASON.
* Remove "intentionally empty" PLISTs again.
Now, the easy way to say that a package installs no files is to just
add the following to the package Makefile:
PLIST_SRC= # empty
26 lines
662 B
Makefile
26 lines
662 B
Makefile
# $NetBSD: Makefile,v 1.10 2007/10/25 22:01:07 jlam Exp $
|
|
|
|
.include "Makefile.common"
|
|
|
|
PKGREVISION= 1
|
|
|
|
DEPENDS+=${CLEARSILVER_BASE}{,nb[0-9]*}:../../www/clearsilver-base
|
|
DEPENDS+=${PYPKGPREFIX}-${DISTNAME}{,nb[0-9]*}:../../www/py-clearsilver
|
|
DEPENDS+=${RUBY_PKGPREFIX}-${DISTNAME}{,nb[0-9]*}:../../www/ruby-clearsilver
|
|
|
|
EXTRACT_ONLY= # empty
|
|
NO_CHECKSUM= YES
|
|
NO_CONFIGURE= YES
|
|
NO_BUILD= YES
|
|
PLIST_SRC= # empty (meta-package)
|
|
|
|
.include "../../lang/python/pyversion.mk"
|
|
.include "../../lang/ruby/rubyversion.mk"
|
|
|
|
# The NO_PATCH macro is gone so we have to do this to prevent the
|
|
# patches from being applied:
|
|
do-patch:
|
|
|
|
do-install:
|
|
|
|
.include "../../mk/bsd.pkg.mk"
|