| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
USE_TOOLS and any of "autoconf", "autoconf213", "automake" or
"automake14". Also, we don't need to call the auto* tools via
${ACLOCAL}, ${AUTOCONF}, etc., since the tools framework takes care
to symlink the correct tool to the correct name, so we can just use
aclocal, autoconf, etc.
|
|
XXX: should there be one, replacing USE_INET6?
|
|
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.
|
|
|
|
|
|
|
|
* Version 1.2.4 (2005-05-28)
- Corrected some bugs that could affect 64 bit systems.
- Some corrections in the header files to include the prototype
of memmem properly (affected 64 bit systems). Report and patch
by Yoann Vandoorselaere <yoann@prelude-ids.org>.
- Introduced the --fix-key option to certtool, which can be used to
regenerate the (optional) parameters in a private key. It should
be used together with --key-info.
- Corrected a bug in certificate chain verification that could lead
to marking a trusted chain as non trusted, if the last certificate in
the chain was a self signed one.
- Gnulib portability files were updated.
- License were updated to reflect new FSF address.
|
|
compatibility provided via PKG_OPTIONS_LEGACY_OPTS.
|
|
compatibility provided via PKG_OPTIONS_LEGACY_OPTS.
|
|
user settable variable. Set PKG_SUGGESTED_OPTIONS instead. Also,
make use of PKG_OPTIONS_LEGACY_VARS.
Reviewed by wiz.
|
|
This still works on NetBSD (1.6.2 tested) but also fixes the include error
on Linux (Debian 3 tested) and Solaris (9 tested).
Although DragonFlyBSD, FreeBSD and OpenBSD should work as before I have
not tried to build the package there.
Feedback whether it builds/works on Darwin/MacOS is also welcome.
|
|
|
|
Changes from previous pkgsrc version 2.1.0 include:
apg-2.2.3
Fixed version info (-v).
apg-2.2.2
Fixed permissions for source distribution.
apg-2.2.1
Changed manpages of apg and apgd.
apg-2.2.0
Added polish translation for APG PHP frontend.
Added option -p (see apg(1) apgd(8)).
Added option -t (see apg(1) apgd(8)).
Added option -l (see apg(1)).
Changed format of the bloom-filter file. Added
converter utility to convert old format to the
new one (bfconvert).
Added option -i (see apgbfm(1)).
Fixed some bugs.
Some compatibility changes.
Changed default apg options.
Update provided by Leonard Schmidt <lems@gmx.net> in PR#30345, thanks!
|
|
|
|
and maybe other platforms.
Bump PKGREVISION.
|
|
and extra pam file was not included in +CONTENTS.
So moved the include of options.mk to after the PLIST_SRC and
MESSAGE_SRC are defined as empty.
(MESSAGE_SRC is redefined if Interix and if PAM PKG_OPTION was enabled
then this still needs to be fixed.)
|
|
|
|
and LEX is "flex". They break when full paths are passed to the
configure script via YACC and LEX (!!).
|
|
|
|
|
|
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
|
|
reviewed by wiz and agc.
|
|
|
|
|
|
|
|
seahorse 0.7.8
--------------
* HKP key server support.
* Reworked drag-and-drop. Now works between Seahorse windows.
* Added a dialog for adding key servers simply and correctly.
* Add option to agent 'Authorize' window to turn off prompting
for authorization [Adam Schriber]
* Handle empty passwords properly in agent [Adam Schreiber]
* Keep agent window on top [Adam Schreiber]
* Removed libeel dependency.
* Better keyboard handling in the recipients dialog.
* Fix some rare gnome-vfs problems.
* Many smaller bug fixes.
seahorse 0.7.7
--------------
* Working keyserver sync (including upload) support.
* Compatibility with GNOME 2.10.
* Nautilus plugin now works with Nautilus 2.10 [Fernando Herrera]
* Cleaned up and simplified columns in the Key Manager.
* Fix problems with entering expiry dates.
* Remove 'Text Mode' option. Clarify 'ASCII Armor' option.
* Removed lots of 'jargon' from the interface.
* Can now drag keys from a key list to nautilus.
* Many smaller bug fixes.
seahorse 0.7.6
--------------
* Compatible with GPG 1.4
* Initial LDAP key server searching and importing support.
* Show descriptive icons (eg: secret, public keys) in the main
Key Manager window. [Adam Schreiber]
* Monitor keyring and refresh key list automatically across
processes, such as gedit plugin, recipient selection etc...
* Decryption 'Open With' in nautilus for PGP encrypted and
signed files. [Adam Schreiber]
* Added Backup Keyrings functionality. [Adam Schreiber]
* Prompt for signer when no default key is selected.
* Display UIDs properly in the seahorse-agent status window.
* Allow selection of a signing key in the Recipients dialog.
* More usable HIG friendly Key Properties dialog [Jim Pharis]
* Fix problems with 0 length files being created on error.
* Gnome HIG compliancy fixes
* Allow deletion of UIDs from the Key Manager window.
* Show all UIDs in the Recipient selection dialog.
* Prompt before overwriting files.
* More efficient operations on large files.
* Enable gedit plugin by default.
* Many smaller bug fixes.
|
|
|
|
apparently some systems only have .a (pointed out by adrianp@).
|
|
> Some highlights in this release:
>
> - Previously unreleased exploits (20 others added since 2.3)
> + Solaris KCMS Arbitary File Read
> + Solaris snmpXdmid AddComponent Overflow
> + Metasploit Framework Payload Handler
> + Microsoft Message Queueing Service MSO5-017
> + Minishare 1.41 Buffer Overflow
>
> - Addition of the new SunRPC and XDR Perl API
> + Allows for clean RPC exploit development
> + Used by two new exploit modules (KCMS and snmpXdmid)
> + Updated sadmind exploit uses the new API
>
> - Includes the new win32 PassiveX payload system
> + Loads an arbitary ActiveX through Internet Explorer
> + PassiveX payload loads the next stage over HTTP
> + HTTP transport emulates a standard TCP connection
> + Interact with cmd.exe, VNC, or Meterpreter over HTTP
> + Uses Internet Explorer settings for proxy access
> + Fully-functional on systems with Internet Explorer 6
> + Extensive documentation is available online:
> * http://www.uninformed.org/?v=1&a=3&t=pdf
>
> - Stability improvements and numerous bugs fixes
> + The msfweb interface is slightly less of a memory pig
> + Many exploits have been updated and improved
> + New external references added to the exploit modules
>
> - General improvements to the payload system
> + Brand new "shelldemo" binary for the impurity stager
> + Size reductions to win32_bind, win32_reverse, and others
> + Can now make standalone executables with msfpayload
> + Interact with metasploit payloads via payload_handler.pm
|
|
.tar file. Also, fix the yacc silliness while we're here.
|
|
|
|
Apparently, for as of yet undetermined reasons, gawk as built on IRIX
under pkgsrc croaks on regular expressions including a
combination of alpha- and numerical matches, such as the rather
trivial /^[ \t]*[0-9]+/
Let's use the system's AWK (ie nawk) for this package to avoid
breaking hundreds of dependents.
Speculation: somehow the regular expression library used to build
gawk conflicts with the systems regular expression library or
some such.
Note: gawk from SGIs freeware collection depends on expat -- why
is that? Does that have anything to do with anything?
|
|
|
|
|
|
|
|
|
|
of the example config files through to sub-make processes. Since
courier-authlib uses GNU automake, we need to set AM_MAKEFLAGS to the
correct value. This fixes the installation of the *.dist files into
${PREFIX}/share/examples/courier-authlib.
|
|
"MAKEFLAGS". Both "MAKEVARS" and "MAKEFLAGS" affect the package-level
make process, not the software's own make process.
|
|
to pass make flags to bmake.
|
|
Updated to OpenBSD 3.7 pf:
* Support limiting TCP connections by establishment rate, automatically
adding flooding IP addresses to tables and flushing states
(max-src-conn-rate, overload <table>, flush global).
* Improved functionality of tags (tag and tagged for translation rules,
tagging of all packets matching state entries).
* Improved diagnostics (error messages and additional counters from pfctl -si).
* New keyword set skip on to skip filtering on arbitrary interfaces,
like loopback.
* Several bugfixes improving stability.
ALTQ is now also supported by using the option 'altq', see the homepage
for information about how to apply the kernel patch.
Approved by: Thomas Klausner <wiz@NetBSD.org>
|
|
Multiple bug fixes, the most important being NAT-T now working with
multiple endpoints behind the same NAT.
|
|
specifically, check in /usr/lib${ABI}, since it's possible that
on multi-ABI platforms only one version is installed, in which case we'd
need to build and install the other from pkgsrc.
|
|
options framework. Rename PKG_OPTIONS.* to PKG_BUILD_OPTIONS.*.
|
|
caches variable definitions that were computed by make. These variables
are specified by listing them in MAKE_VARS, e.g.,
.if !defined(FOO)
FOO!= very_time_consuming_command
.endif
MAKE_VARS+= FOO
bsd.pkg.mk will include only the one generated during the most recent
phase. A particular phase's makevars.mk file consists of variable
definitions that are a superset of all of the ones produced in previous
phases of the build.
The caching is useful because bsd.pkg.mk invokes make recursively,
which in the example above has the potential to run the very time-consuming
command each time unless we cause FOO to be defined for the sub-make
processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't
consistently applied to every invocation of make, and also because
MAKE_FLAGS can overflow the maximum length of a make variable very
quickly if we add many values to it.
One important and desirable property of variables cached via MAKE_VARS
is that they only apply to the current package, and not to any
dependencies whose builds may have been triggered by the current
package.
The makevars.mk files are generated by new targets fetch-vars,
extract-vars, patch-vars, etc., and these targets are built during
the corresponding real-* target to ensure that they are being invoked
with PKG_PHASE set to the proper value.
Also, remove the variables cache file that bsd.wrapper.mk was generating
since the new makevars.mk files provide the same functionality at a
higher level. Change all WRAPPER_VARS definitions that were used by
the old wrapper-phase cache file into MAKE_VARS definitions.
|
|
package because PKG_OPTION.<pkg> could contain negative options, which
are never part of PKG_OPTIONS. Instead, use the show-var target to
display the value. We cache it in WRAPPER_VARS and in MAKE_FLAGS to
prevent reinvoking the show-var target recursively.
|
|
|
|
|
|
|
