Up to [cvs.NetBSD.org] / pkgsrc / mk / platform
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
mk: Remove _OPSYS_HAS_OSSAUDIO, use oss.buildlink3.mk/OSS_TYPE "please remove it" wiz@
mk: Remove _OPSYS_PERL_REQD. It's not 2003 anymore, all platforms use the same perl, we don't support system perl, and this saves calls to pkg_admin for every perl-using package. From Jonathan Perkin <jperkin@smartos.org> via drecklypkg commit $18912d81e683c25b2fec0b7506dfbe421e5b2a90
Remove _OPSYS_WHOLE_ARCHIVE_FLAG and _OPSYS_NO_WHOLE_ARCHIVE_FLAG, these variables are unused and in at least one case were completely wrong anyway.
Rename the PKGNAME for the OPSYS-specific user packages to include the OPSYS, so that they are correctly calculated as independent. This avoids issues in bulk builds where the package version was taking precedence and causing the wrong user package to be depended upon.
Introduce _OPSYS_LIB_DIRS and _OPSYS_INCLUDE_DIRS varables. list of system library and header file directories. Also add missing _OPSYS_SYSTEM_RPATH for some platforms.
Drop imake-check logic from X11 components' builtin.mk. Always use xorg-cf-files and imake from pkgsrc, replacing xpkgwedge. Always install man pages, not cat pages when using imake. Unify the various imake PLIST variables in preparation for dropping. Adjust xbattbar for the new expectations.
IRIX 6 made it to X11R6, but never X11R7, so default to X11_TYPE=modular
From "What platforms work with X11_TYPE=native" thread on pkgsrc-users. Based on the responses I'm going to switch the default X11_TYPE to be modular, and override in platform/*.mk files as required. The new values will be: Changed - from native to modular - FreeBSD - FreeMiNT - Linux Changed - older versions switched from native to modular - NetBSD - native for NetBSD-4 and later Native (unchanged) - should probably be switched to modular - AIX - BSDOS - IRIX - Interix - MirBSD - UnixWare Native (unchanged) - Darwin - for Leopard (10.5) and later - OpenBSD.mk - SunOS.mk Modular (unchanged) - DragonFly - HPUX - Haiku - OSF1 I'd like to encourage anyone using X11 apps on any platforms other than NetBSD, Darwin, DragonFly, FreeBSD, Linux, FreeMiNT, HPUX, Haiku or OSF1 to speak up, whether they are happy with native or having to set modular.
Use useradd/groupadd scripts from sysutils/user_irix package on IRIX Closes PR pkg/44564
Begin cleanup of setgid game infrastructure. * Introduce USE_GAMESGROUP, which causes the games user and group to be made available. * Retain SETGIDGAME as an alias for USE_GAMESGROUP. Describe it as deprecated. * Always define GAMES_USER, GAMES_GROUP, GAMEMODE, GAMEDIRMODE, and GAMEDATAMODE, regardless of whether USE_GAMESGROUP is turned on or not. * Define these variables in defaults/mk.conf instead of separately in every platform/*.mk file. The definitions used to be the same for each of these platforms anyway, except for some where they were randomly missing or commented out for no clear reason, leading to broken game packages. * Handle all these variables properly when unprivileged. * Update the comments/documentation for these variables. * Describe GAMEOWN and GAMEGRP as deprecated. These need to be retained as aliases for GAMES_USER and GAMES_GROUP respectively for supporting packages that use bsd.*.mk but should otherwise not be used. * Add GAMEDATA_PERMS and GAMEDIR_PERMS using GAMEDATAMODE and GAMEDIRMODE respectively. * Fix a bug I noticed that was improperly mixing the "games" group and "games" user. Things this does *not* do: - get rid of GAMES_USER, for which there should ultimately be no need. - move the declaration/documentation/default value of USE_GAMESGROUP to a suitable place. (It is currently where SETGIDGAME was, which is suboptimal.) - touch any of the games, all of which need updating with at least s/SETGIDGAME/USE_GAMESGROUP/ and probably more. - update the guide to explain how to handle games properly. Also, it would be nice if using GAMES_GROUP without setting USE_GAMESGROUP=yes caused an error but as far as I know there isn't any particularly good way to arrange this right now. Note that these changes may alter the build/install behavior of broken game packages, e.g. some may silently become setgid when they weren't before or things like that. If you run into any of this file a PR. While one might arguably bump the PKGREVISION of all games or other packages using any of these variables as a precaution, that seems like a bad idea. Instead, I think I will be bumping each game once it itself has been fixed up to do everything the right way.
Get rid of an abstraction violation which has been in the tree since March 2008. Not vital, but the previous way does not scale well/at all.
+ Conditionally add GAMES_USER and GAMES_GROUP to the platform *.mk
files. These variables are currently usable if ${SETGIDGAME} == yes.
These variables should be used when describing ownership of files
and directories to the pkginstall framework, e.g.
SPECIAL_PERMS= bin/foogame ${GAMES_USER} ${GAMES_GROUP} 2555
+ Rename SETGID_GAME_PERMS to SETGID_GAMES_PERMS because the default
group name is "games".
+ Define SETGID_GAMES_PERMS in terms of GAMES_USER and GAMES_GROUP so
that these names are protected from the normal flow of unprivileged.mk.
This fixes the +INSTALL scripts in "user-destdir" packages to
correctly refer to the games:games instead of the user:group of the
user that built the packages.
Kill _OPSYS_NEEDS_XPKGWEDGE. It was only used by two platforms and they will default to USE_XPKGWEDGE anyway.
Reverted the last changes, which factored out some definitions that are usually the same on the supported platforms. The reason for having duplicate code in these files is to make it easier to port pkgsrc to a new platform: You just have to copy one of the existing platform files and edit the values in it. With some values factored out, you would have to look at one more file. Pointed out by agc@.
Factored out the parts that are common between all the supported platforms, mainly because it wouldn't have made sense to document the variables in one of those files, but they need to be documented somewhere. Added the file defaults.mk, which now serves as the reference document which provides useful default values and _explains_ the variables.
* Add new emulator framework in pkgsrc/mk/emulator that handles all
binary-only packages that require binary "emulation" on the native
operating system. Please see pkgsrc/mk/emulator/README for more
details.
* Teach the plist framework to automatically use any existing
PLIST.${EMUL_PLATFORM} as part of the default PLIST_SRC definition.
* Convert all of the binary-only packages in pkgsrc to use the
emulator framework. Most of them have been tested to install and
deinstall correctly. This involves the following cleanup actions:
* Remove use of custom PLIST code and use PLIST.${EMUL_PLATFORM}
more consistently.
* Simplify packages by using default INSTALL and DEINSTALL scripts
instead of custom INSTALL/DEINSTALL code.
* Remove "SUSE_COMPAT32" and "PKG_OPTIONS.suse" from pkgsrc.
Packages only need to state exactly which emulations they support,
and the framework handles any i386-on-x86_64 or sparc-on-sparc64
uses.
* Remove "USE_NATIVE_LINUX" from pkgsrc. The framework will
automatically detect when the package is installing on Linux.
Specific changes to packages include:
* Bump the PKGREVISIONs for all of the suse100* and suse91* packages
due to changes in the +INSTALL/+DEINSTALL scripts used in all
of the packages.
* Remove pkgsrc/emulators/suse_linux, which is unused by any
packages.
* cad/lc -- remove custom code to create the distinfo file for
all supported platforms; just use "emul-fetch" and "emul-distinfo"
instead.
* lang/Cg-compiler -- install the shared libraries under ${EMULDIR}
instead of ${PREFIX}/lib so that compiled programs will find
the shared libraries.
* mail/thunderbird-bin-nightly -- update to latest binary
distributions for supported platforms.
* multimedia/ns-flash -- update Linux version to 9.0.48 as the
older version is no longer available for interactive fetch.
* security/uvscan -- set LD_LIBRARY_PATH explicitly so that
it's not necessary to install library symlinks into
${EMULDIR}/usr/local/lib.
* www/firefox-bin-flash -- update Linux version to 9.0.48 as the
older version is no longer available for interactive fetch.
Remove RSH definition.
Always use LOCALBASE setting from mk/defaults/mk.conf. Setting it with ?= in the platform files is a nop anyway.
improve imake support on IRIX 5
Remove USE_GNU_GETTEXT from pkgsrc. Packages generally only needed it for plurals support, but that is already handled correctly (FSVO "correctly") by the pkgsrc/mk/tools/msgfmt.sh script. Also remove _USE_GNU_GETTEXT definitions from pkgsrc/mk/platform/*.mk files as that value has been unused by pkgsrc for quite some time (going back several branches).
Back out revision 1.172 of mk/tools/replace.mk -- we never want to
allow IMAKE to be set by anything other than the tools framework.
Modify the IRIX files so that the native imake is listed as a built-in
tool in the case where X11_TYPE is "native". Also, move the include
of tools/default.mk a bit lower in bsd.prefs.mk so that tools.${OPSYS}.mk
files can use the value of X11_TYPE. This should properly set and
point IMAKE to the right binary on IRIX without destroying the
configuration for platforms where IMAKE was not explicitly set, i.e.
every non-IRIX platform.
EOL the tv-derecurse branch; it has become too outdated. The last live revision can be fetched at the tv-derecurse-eol tag.
Add INSTALL_GAME_DIR to complement INSTALL_GAME_DATA. The directories are group-writeable by the games user on those platforms, where GAMEMODE includes setgid. It defaults to PKGDIRMODE otherwise.
Modified xmkmf support for Darwin and IRIX: - on Darwin, pkgsrc no longer tries to set user or group when installing as unprivileged user, i.e. with UNPRIVILEGED set to yes. - on IRIX (5 and 6) the system's xmkmf config files are no longer modified. Instead copies (that take priority with pkgsrc's xmkmf) are used for that purpose.
Remove leftover code sections guarded by _USE_PLIST_MODULE which was mainlined long ago.
Initial commit of a new module that encapsulates all of the code
for manipulating PLISTs. This module is not used by default pending
more widespread testing -- currently the variable _USE_PLIST_MODULE
must be defined in /etc/mk.conf to enable its use.
The main features of the new PLIST module are:
(1) Splits out the PLIST-handling code from bsd.pkg.mk into a
separate "plist" module.
(2) Splits out giant, multi-line awk scripts stored in make
variables into separate awk scripts that may be joined
together to post-process PLISTs. Each of these awk scripts
consolidates the processing for one set of files, e.g.,
man pages, info pages, etc., and is more easily commented
than a make variable.
(3) Splits out the print-PLIST code from the regular PLIST code
since they have no common pieces (print-plist.mk vs.
plist.mk).
(4) Completely re-implements the shared-library handling to be
more efficient. Along the way, this also fixes a problem
for Mac OS X users where the PLISTs incorrectly contained
absolute paths.
(5) Completely re-implements the info-file handling so that we
can migrate from INFO_FILES definitions to just adding
info/foo.info entries in the static PLISTs.
(6) Adds commented-out support for automatically compressed or
decompressed info page entries based on the value of MANZ.
These changes will be activated after texinfo.mk has been
replaced by something that is built using the more modern
primitives now available in pkgsrc.
(7) Move the file compression logic into a separate script
"doc-compress" that compresses or decompresses files while
minding symlinks. This script is now called by bsd.pkg.mk
to do the "autmoatic man page handling". In the future,
it will also handle the "automatic info page handling" and
possible others.
In general, the idea is to move stuff out of the Makefiles and into
separate files where we don't need to worry about quoting rules
and where each file can have a separate history of commits. This
simplifies the makefile logic (especially in terms of readability)
and also simplifies maintenance of the code.
Pass correct flags to install.sh to invoke IRIX's strip command
Back out previous; this was supposed to go into -current, not the branch.
Pass correct flags to install.sh to invoke IRIX's strip command
Applied all quoting fixes found by "pkglint --autofix".
Add IMAKE_GAMEMAN_SUFFIX and IMAKE_GAMEMAN_DIR to allow PLISTs to pick up the correct locations. XXX Default values are guessed, x11/xsnow can be used for testing
modification to increase imake handling flexibility for IRIX (in particular with respect to IRIX 5). Changes approved by jschauma and recht.
Replace references of pkgsrc/mk/bsd.pkg.defaults.mk to pkgsrc/mk/defaults/mk.conf. This is from PR 30741 from anonymous AT example.net.
Turn IMAKE_MAKE into a public variable that may be set via /etc/mk.conf.
Remove the old tools framework and references to _USE_NEW_TOOLS.
sync [all but bsd.pkg.mk] with HEAD
First pass at converting pkgsrc to use the new tools framework (still not on by default). Separate out the variable defintions that are now made by the new tools framework. Some of the trickier platforms (AIX, IRIX, Interix, OSF1) still need more work.
Back out part of a change from revision 1.756 of bsd.pkg.mk. It was
a mistake to include "GZIP" as an ${OPSYS}-specific variable as there
is nothing ${OPSYS}-specific there to tune. Define GZIP in
defaults/mk.conf instead, and remove the definition from each of the
existing platform/${OPSYS}.mk files.
enable the user to set LIBABISUFFIX if desired. Change approved by jschauma.
sync with HEAD
Fix a gleaming illustration of why using YES/NO variables everywhere possible, just for the sake of doing so, is not a good thing to do: The platform files define _STRIPFLAG_* to determine whether to strip things. But since this is included in bsd.prefs.mk, ".if ..." checks cannot take things set in the Makefile into account. So convert INSTALL_UNSTRIPPED=YES to a defined/undefined variable check in bsd.pkg.mk, and use the :D:U idiom in the _STRIPFLAG_* variables. This should fix PR pkg/28772 and PR pkg/29031.
sync with HEAD
Don't make pkgsrc depend on dc(1) to be present in the system. Since we already use awk so pervasively in pkgsrc, simply use awk in place of dc for simple computations.
Relax need to put GNU_CONFIGURE before inclusion of bsd.prefs.mk: Convert _OPSYS_MAX_CMDLEN to a plain _OPSYS_MAX_CMDLEN_CMD variable, which is not evaluated by a shell until CONFIGURE_ENV is expanded (and only then if USE_LIBTOOL+GNU_CONFIGURE are both set).
sync with HEAD
Remove USERADD and GROUPADD definitions from OSes where the useradd
and groupadd commands won't follow the calling conventions of the
NetBSD useradd/groupadd. Modify the INSTALL scripts to *never* create
users or groups if there is no available ${USERADD} or ${GROUPADD}
command, but will warn the user of users and groups that need to be
created before the package can be installed.
Revert previous (re-add common CPP_PRECOMP_FLAGS). For consistency, also move usage of _USER_DEPENDS and _OPSYS_MAX_CMDLEN to bsd.pkg.mk.
CPP_PRECOMP_FLAGS is a Darwinism only. Move its frobbing of CPPFLAGS to platform/Darwin.mk (simplification).
Set some _OPSYS_SHLIB_TYPE to precisely 'ELF' on platforms where a.out is not being used by pkgsrc at all. This saves some build time in show-shlib-type.
Introduce LIBABISUFFIX for platforms which require ABI-dependant library paths.
Make strip/no-strip choice more consistent: Move check for INSTALL_UNSTRIPPED to the platform/*.mk files, alongside existing check for DEBUG_FLAGS.
Reorganize some of the files under pkgsrc/mk:
(1) defs.${OPSYS}.mk --> platform/${OPSYS}.mk.
The "platform" subdirectory is where all of the ${OPSYS}-specific
infrastructure logic should reside.
(2) bsd.pkg.defaults.mk --> defaults/mk.conf
bsd.pkg.obsolete.mk --> defaults/obsolete.mk
Renaming bsd.pkg.defaults.mk to defaults/mk.conf is to mimic the way
that NetBSD has /etc/rc.conf as well as /etc/defaults/rc.conf, where
the latter is a full list of user-settable variables, and the two
files share the same name to reinforce the fact /etc/defaults/rc.conf
can be directly copied in place as /etc/rc.conf. This is the same
relationship shared by defaults/mk.conf and /etc/mk.conf.