Age | Commit message (Collapse) | Author | Files | Lines |
|
PR-responsible person (such as I am ;) a little easier.
|
|
|
|
scripts prior to revision 1.43 of bsd.pkginstall.mk.
|
|
* List info files directly in the PLIST.
* Don't install the catman pages at all to fix PLIST problems.
Bump the PKGREVISION to 6.
|
|
|
|
Name service error for name=wongs.net type=MX: Host not found, try again.
for five days in a row, on two separate occasions (more than a week apart).
|
|
This will cause amanda to add -X to dump on systems where this option
is available (AFAIK NetBSD 3.0 and newer).
Add the user-settable variable AMANDA_DUMP_SNAP to control this at the
package build time (disabled by default).
Bump pkgrevision.
|
|
provided by PR pkg/33077.
|
|
|
|
|
|
with GCC 3.4+.
|
|
INSTALL/DEINSTALL script creation within pkgsrc.
If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts. If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:
INSTALL_SRC= ${PKGDIR}/INSTALL
DEINSTALL_SRC= # emtpy
As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts. By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).
In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework. The only public variables relating to the templates are:
INSTALL_SRC INSTALL_TEMPLATE
DEINSTALL_SRC DEINSTALL_TEMPLATE
HEADER_TEMPLATE
The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
|
|
|
|
Ipmitool is a utility for managing and configuring devices that support
the "Intelligent Platform Management Interface". IPMI is an open
standard for monitoring, logging, recovery, inventory, and control of
hardware that is implemented independent of the main CPU, BIOS, and OS.
The service processor (or Baseboard Management Controller, BMC) is the
brain behind platform management and its primary purpose is to handle
the autonomous sensor monitoring and event logging features.
The ipmitool program provides a simple command-line interface to this
BMC. It features the ability to read the sensor data repository (SDR)
and print sensor values, display the contents of the System Event Log
(SEL), print Field Replaceable Unit (FRU) inventory information, read
and set LAN configuration parameters, and perform remote chassis power
control.
|
|
|
|
|
|
Changes 0.12.14:
Fixed the data project verification once and for all
Changes 0.12.13:
Bug fixes.
|
|
|
|
|
|
gvpr in 1.12. Closes PR 33093 by Joern Clausen.
|
|
|
|
|
|
|
|
without underscores (REPLACE.*.old, REPLACE.*.new, and REPLACE_FILES.*).
Also convert REPLACE.*.new= ${SH:Q} back to ${SH}, as it should not be quoted
here, if at all.
Ok with rillig.
|
|
|
|
Removed BROKEN_IN.
Fixes PR 33053.
|
|
|
|
* bug fixes
* translation updates
|
|
Remove deprecated ossaudio.buildlink3.mk.
|
|
Over 700 lines of changes omitted, but four new drivers added:
bcmxcp gamatronic solis upscode2
|
|
|
|
|
|
|
|
automatically. The essential concept is that a file which was
installed automatically and has not been changed will be updated with
new versions, and modified files will not be changed.
This is 0.2
|
|
|
|
|
|
dd_rhelp is a bash script that handles a very useful program written in C by
Kurt Garloff which is called dd_rescue, which roughly acts as the dd(1) command
with the characteristic to NOT stop when it falls on read/write errors. But
using it is quite time consuming. This is where dd_rhelp come to help.
In short, it'll use dd_rescue on your entire disc, but will try to gather the
maximum valid data before trying for ages on bad sectors. So if you leave
dd_rhelp work for infinite time, it'll have the same effect as a simple
dd_rescue. But because you might not have this infinite time (this could indeed
take really long in some cases...), dd_rhelp will jump over bad sectors and
rescue valid data. In the long run, it'll parse all your device with dd_rescue.
You can Ctrl-C it whenever you want, and rerun-it at will, it'll resume its job
as it depends on the log files dd_rescue creates.
|
|
|
|
Like dd, dd_rescue does copy data from one file or block device to another.
You can specify file positions (called seek and Skip in dd).
There are several differences:
* dd_rescue does not provide character conversions.
* The command syntax is different. Call dd_rescue -h.
* dd_rescue does not abort on errors on the input file, unless you specify a
maximum error number. Then dd_rescue will abort when this number is
reached.
* dd_rescue does not truncate the output file, unless asked to.
* You can tell dd_rescue to start from the end of a file and move backwards.
* It uses two block sizes, a large (soft) block size and a small (hard) block
size. In case of errors, the size falls back to the small one and is
promoted again after a while without errors.
|
|
|
|
NetBSD 2 + pflkm, because the path was substituted by "__nonexistent__".
So to fix this properly, add a patch with CPP conditional which fixes
the path for __DragonFly__.
|
|
Add DragonFly support.
|
|
libtasn1 had a shlib major bump.
Also update dependencies in bl3.mk files.
Addresses PR 32998 by Robert Elz.
|
|
makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD
when determining whether the native makeinfo can be used.
* Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo.
* Get rid of all the "split" argument deduction for makeinfo since
the PLIST module already handles varying numbers of split info files
correctly.
NOTE: Platforms that have "makeinfo" in the base system should check
that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are
correct.
|
|
|
|
|
|
|
|
|
|
|
|
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.
|