| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
CFLAGS= in /etc/mk.conf.
|
|
archives for better tracking and archiving:
11.1 Submitting your packages
=============================
...
* packages:
First, check that your package is complete, compiles and runs well; see
section 9 and the rest of this document. Next, generate an uuencoded
gzipped tar(1) archive, preferably with all files in a single directory.
Finally, send-pr(1) with category "pkg", a synopsis which includes the
package name and version number, a short description of your package
(contents of the COMMENT variable or DESCR file are OK) and attach the
archive to your PR.
If you want to submit several packages, please send a separate PR for
each one, it's easier for us to track things that way.
|
|
|
|
|
|
|
|
- security/smtpd (not snmpd) wants /etc/localtime.
found while marking up :)
|
|
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
|
|
|
|
|
|
EXTRACT_AFTER_ARGS.
|
|
not be deleted.
|
|
|
|
|
|
* LOWER_OPSYS.
* platform specific PLIST handling.
|
|
* {NOT,ONLY}_FOR_PLATHOME mismatch is not an error. Set
PKG_SKIP_REASON for those cases. This makes bulk builds happier.
|
|
=================================================
There are several reasons why a package might be instructed to not
build under certain circumstances. If the package builds and runs
on most platforms, the exceptions should be noted with NOT_FOR_PLATFORM.
If the package builds and runs on a small handful of platforms,
set ONLY_FOR_PLATFORM instead. If the package should be skipped
(for example, because it provides functionality already provided
by the system), set PKG_SKIP_REASON to a descriptive message. If
the package should fail because some preconditions are not met,
set PKG_FAIL_REASON to a descriptive message.
IGNORE is deprecated because it didn't provide enough information
to determine whether the build should fail.
|
|
(for just-in-time-su(1) password caching)
|
|
The logic is:
- if package defines USE_PKGLOCALEDIR and PKGLOCALEDIR is not 'share' as GNU
autotools expects then
- fix variables 'localedir', 'gnulocaledir' and define coorect 'LOCALEDIR' in
the Makefile.in.* files
From Packages.txt:
10.29 Packages providing locale catalogues
==========================================
If the package provides its own locale catalogues, the variable
USE_PKGLOCALEDIR should be defined. It will ensure that the package's
Makefile template files are fixed and point to the correct locale directories
(which may vary, depending on OS), if necessary. See also section 5.1 for
details about ${PKGLOCALEDIR}. This functionality is buildlink2-only.
|
|
|
|
|
|
|
|
|
|
isn't appropriate for Packages.txt, and change the way the dotted list
appears to look more like the rest of Packages.txt.
|
|
|
|
by devel/gettext-lib/buildlink2.mk.
|
|
|
|
for USE_* which do not exist any longer.
|
|
|
|
?= to =. Note in Packages.txt that the only variables that a user should
customize in /etc/mk.conf are PKG_SYSCONFBASE and PKG_SYSCONFDIR.<pkg>.
|
|
the example mk.conf for bulk builds, since these are now set by the
bulk build machinery itself. This allows an /etc/mk.conf file to be
shared between ordinary builds and bulk builds.
|
|
|
|
|
|
|
|
definition.
INTERACTIVE_STAGE can take any of the values: fetch, configure, build and
install
Multiple values are allowed: e.g. INTERACTIVE_STAGE= configure install
Explain INTERACTIVE_STAGE and its use in documentation.
Patches provided by Chris Pinnock (cjep@netbsd.org).
|
|
prerequisites to be updated.
|
|
UPDATE_TARGET is the recommended way of modifying the target to be used for
'make update'.
|
|
- cut and paste read instructions for setting (most of) chroot sandbox
- add mk.conf frob for accepting all licenses (in bulk build code only! ;)
|
|
|
|
(1) Admins want to create users/groups on their own (pkg/17183).
(2) Admins don't want packages to setup an initial configuration.
The bsd.pkg.install.mk-generated INSTALL/DEINSTALL scripts have been
modified to check certain PKG_* environment variables to tune their
behaviour. This works whether installing from "make install" or from a
binary package.
PKG_CREATE_USERGROUP indicates whether the INSTALL script should
automatically add any needed users/groups to the system using
useradd/groupadd. It is either YES or NO, and defaults to YES.
PKG_CONFIG indicates whether the INSTALL/DEINSTALL scripts should do
automatic config file and directory handling, or if it should
merely inform the admin of the list of required files and
directories needed to use the package. It is either YES or NO,
and defaults to YES.
The make(1) variable INSTALL_RCD_SCRIPTS is removed. The package rc.d
script is now handled like other config files for the package, and is
copied into place if PKG_CONFIG=YES.
The default values above reflect the current behaviour. Setting
PKG_CREATE_USERGROUP=NO solves problem (1), and setting PKG_CONFIG=NO
solves problem (2).
To simply matters for users installing directly from pkgsrc, these
variables may also be defined in /etc/mk.conf, but behaviour at deinstall
time may be surprising. It is *HIGHLY* recommended that these values be
set in the shell environment instead.
|
|
VARNAME=..."
|
|
|
|
built against the default X version for that release and architecture,
which is currently 3.3.6 for all architectures. Addresses pkg/16492.
|
|
|
|
Contributed by Julio Merino <jmmv@hispabsd.org> in PR 16971,
with minor editing by myself.
|
|
Fixes PR#16892 by Julio Merino <jmmv@hispabsd.org>
|
|
|
|
By Julio Merino from pkg/16333.
|
|
`1.2-compatible' should be inverted.
|
|
the system applies both ways, i.e., don't set LOCALBASE to where you have
your system files, *and vice versa*, as this repeatetly has lead to
problems (see PRs 15999 and 16029 for the latest examples).
|
|
|
