| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
$$extract_file instead."
|
|
|
|
On DragonFly with zlib 1.2.7, an error during extraction was seen:
> gzip: (stdin): trailing garbage ignored
> /usr/pkg/bin/gtar: Child return status 1
> /usr/pkg/bin/gtar: Error is not recoverable: exiting now
RTCW uses a custom extraction command which is sed piped into gtar.
To workaround this error, sed was piped into gunzip which was then
piped into gtar, so other error status was laundered out.
Also, there were some permission check failures when PKG_DEVELOPER=yes
so small workarounds were added. rctw installs with PKG_DEVELOPER check
without error now.
|
|
Id Software changed the location of the binary, but its still available.
The MASTER_SITE would have been valid for the latest version, 1.41,
released in 2003.
|
|
|
|
|
|
many packages used to use ${PAX}. Use the common way of directly calling
pax, it is created as tool after all.
|
|
their files via a custom do-install target.
|
|
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.
|
|
Patch provided by Sergey Svishchev in private mail.
|
|
it will live with other "check" targets run after package installation.
Get rid of SHLIB_HANDLING, whose meaning had mutated over the years
from one thing to another. Currently, it is used to basically note
whether the system's "ldd" command can be usefully run on the package's
binaries and libraries. Rename this variable to CHECK_SHLIBS_SUPPORTED
for more clarity.
CHECK_SHLIBS is now a variable set exclusively by the user in /etc/mk.conf
to note whether the check for missing run-time search paths is performed
after a package is installed. It defaults to "no" unless PKG_DEVELOPER
is set.
|
|
need them, for example RESTRICTED and SUBST_MESSAGE.*.
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
|
|
PKGSRC_USE_TOOLS go away. There is now only a single USE_TOOLS variable
that specifies all of the tools we need to build/run the package.
|
|
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
|
|
|
|
|
|
|
|
|
|
USE_X11 is enough for Linux systems (noted by wiz@).
|
|
this is a linux binary, so don't check for shared libraries.
|
|
David Ferlier in PR pkg/24222.
World War II rages and nations fall. SS head Himmler has Hitler's full
backing to twist science and the occult into an army capable of
annihilating the Allies once and for all. Battling alone, you're on an
intense mission to pierce the black heart of the Third Reich and stop
Himmler -- or die trying. Fighting in advanced team-based multiplayer mode,
you'll wage your own WWII in an all-out Axis vs. Allies contest for
frontline domination.
Powered by the Quake III Arena engine, the Wolfenstein universe explodes
with the kind of epic environments, A.I., firepower and cinematic effects
that only a game created by true masters can deliver. The dark reich's
closing in. The time to act is now. Evil prevails when good men do nothing.
* Epic Environments
* Intense Story-Driven Action
* Ferocious A.I.
* Big Screen Cinematic Effects
* Team-Based Multiplayer Action
|
|
David Ferlier in PR pkg/24222.
World War II rages and nations fall. SS head Himmler has Hitler's full
backing to twist science and the occult into an army capable of
annihilating the Allies once and for all. Battling alone, you're on an
intense mission to pierce the black heart of the Third Reich and stop
Himmler -- or die trying. Fighting in advanced team-based multiplayer mode,
you'll wage your own WWII in an all-out Axis vs. Allies contest for
frontline domination.
Powered by the Quake III Arena engine, the Wolfenstein universe explodes
with the kind of epic environments, A.I., firepower and cinematic effects
that only a game created by true masters can deliver. The dark reich's
closing in. The time to act is now. Evil prevails when good men do nothing.
* Epic Environments
* Intense Story-Driven Action
* Ferocious A.I.
* Big Screen Cinematic Effects
* Team-Based Multiplayer Action
|
