| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
remove extraneous parenthesis around .if (${FOO} ..) conditions.
|
|
after consulting with Todd. Any volunteers for any of these packages?
|
|
|
|
Summary of changes:
- removal of USE_GTEXINFO
- addition of mk/texinfo.mk
- inclusion of this file in package Makefiles requiring it
- `install-info' substituted by `${INSTALL_INFO}' in PLISTs
- tuning of mk/bsd.pkg.mk:
removal of USE_GTEXINFO
INSTALL_INFO added to PLIST_SUBST
`${INSTALL_INFO}' replace `install-info' in target rules
print-PLIST target now generate `${INSTALL_INFO}' instead of `install-info'
- a couple of new patch files added for a handful of packages
- setting of the TEXINFO_OVERRIDE "switch" in packages Makefiles requiring it
- devel/cssc marked requiring texinfo 4.0
- a couple of packages Makefiles were tuned with respect of INFO_FILES and
makeinfo command usage
See -newly added by this commit- section 10.24 of Packages.txt for
further information.
|
|
a patch for configure so it wasn't really needed anyway.
An autoreconf run here noted a small difference in configure patch so I've
created a new patch distfiles with the new configure patch included.
|
|
the patched files.
|
|
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
|
|
|
|
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
|
|
replace reference to "autoreconf" with a full pathname.
|
|
(sync with -current)
|
|
-current in response to bin/12785.
|
|
|
|
+ move the patch digest/checksum values from files/patch-sum to distinfo
|
|
the "configure.in" isn't modified by the IPv6 patch.
|
|
and causes build failures on systems with IPv6 but without KAME API.
|
|
suggested From: Matthias Scheler <tron@zhadum.de>
|
|
|
|
|
|
|
|
|
|
(This makes me wonder how things work when I setup a system from solaris
pkgs only, that were generated from pkgsrc - i doubt they have the /var/db/pkg
information to make our system recognize them as "our" pkg... ?)
|
|
|
|
|
|
|
|
Make LOCALID a runtime option, instead of a compiletime option, by moving
the value to CVSROOT/config (repository specific).
Some minor fixes for buffer sizes.
Add a RCS Id where missing; add some warning about the deprecated
RCS_LOCALID variable.
Both changes from OpenBSD.
Bump to 1.11nb1.
|
|
* The new "cvs version" command gives a short version message. If
the repository is remote, both the client and server versions are
reported.
* "cvs admin -t" now works correctly in client/server mode.
* The "cvs history" command output format has changed -- the date
now includes the year and is given is ISO 8601 format (yyyy-mm-dd).
Also, the new LogHistory option in CVSROOT/config can be used to
control what information gets recorded in the log file and code has
been added to record file removals.
* The buggy PreservePermissions code has been disabled.
* Anonymous read-only access can now be done without requiring a
password. On the server side, simply give that user (presumably
`anonymous') an empty password in the CVSROOT/passwd file, and then
any received password will authenticate successfully.
* There is a new access method :fork: which is similar to :local:
except that it is implemented via the CVS remote protocol, and thus
has a somewhat different set of quirks and bugs.
* The -d command line option no longer updates the CVS/Root file. For
one thing, the CVS 1.9/1.10 behavior never had updated CVS/Root in
subdirectories, and for another, it didn't seem that popular in
general. So this change restores the CVS 1.8 behavior (which is also
the CVS 1.9/1.10 behavior if the environment variable
CVS_IGNORE_REMOTE_ROOT is set; with this change,
CVS_IGNORE_REMOTE_ROOT no longer has any effect).
* It is now possible for a single CVS command to recurse into several
CVS roots. This includes roots which are located on several servers,
or which are both remote and local. CVS will make connections to as
many servers as necessary.
* It is now possible to put the CVS lock files in a directory
set by the new LockDir option in CVSROOT/config. The default
continues to be to put the lock files in the repository itself.
|
|
|
|
|
|
|
|
|
|
"Make this build with krb5 support".
...take 2.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
noticed before, because pr is only execed if the somewhat obscure --paginate
option is used.
|
|
|
|
Quick guide for compiling packages:
- set KERBEROS=4 or KERBEROS=5 in /etc/mk.conf
Quick guide for configuring Kerberos support in a package Makefile:
- test for KERBEROS value and enable the appropriate version with
CONFIGURE_ARGS or other means and set USE_KERBEROS=yes
- make sure to disable Kerberos support otherwise (especially if
using configure, which might automatically detect it)
- BUILD_DEFS and RESTRICTED are set automatically in bsd.pkg.mk
when USE_KERBEROS=yes is set
|
|
--with{,out}-gssapi switches to the configure script actually work.
The GSSAPI support in CVS is still busted; it makes a lot of
incorrect assumptions about the location of various GSSAPI
headers and libraries. However, I have no interest in actually
fixing anything in CVS.
|
|
displayed using the -B option to pkg_info(1).
|
|
package. Still needs a bit more work, as the CVS 1.10 configure script
is broken.
|
|
|
|
numbers passed to loginfo. If a file is re-added, make sure the `old' revision
is `NONE', not the preceding dead revision.
|
