pkglint --only "https instead of http" -r -F
With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.
This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.
Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
homepage links to homepage-relative copies, the announcement e-mail
mentioned the GNU mirror network. This was noticed after reports about
spurious 403 errors came it. Changed to use MASTER_SITES_GNU.
Improvements since the 4.0.17 release are:
Fix for names of iconv encodings on AIX
Fix mt_size_t on NetBSD
Fixed compilation on Mingw
Fixed doc (especially mformat)
Fix mformat'ing of FAT12 filesystems with huge cluster sizes
Minfo prints image file name in mformat command line if an image
file name was given
Always generate gzip-compressed RPMs, in order to remain
compatible with older distributions
Fixed buffer overflow with drive letter in mclasserase
to use 64bit file offsets where available for seek()ing etc. However, the
easy case (sizeof(off_t)>4) is handled incorrectly: mt_size_t is set to
size_t - maybe a copy and paste from the fall-back-to-32bit case.
This type is used at least in init.c, when detecting media size and comparing
to the FAT geometry, consequently failing and erroring out with the message
"Big disks not supported on this architecture."
The patch does handle the (e.g. NetBSD) case of 64bit off_t the same as
the case where a off64_t is available (and the other 64bit off_t-equivalent
cases); namely using off_t as mt_size_t.
Thanks to riastradh@ for pointing out where the bug in llong.h was.
Added missing -i option to mshortname
Make it clear that label is limited to 11 characters
mbadblocks now takes a list of bad blocks
mbadblocks now is able to do write scanning for bad blocks
mshowfat can show cluster of specific offset
Fixed encoding of all-lowercase names
Consider every directory entry after an ENDMARK (0x00) to be deleted
Changes in 4.0.14:
Fix floppyd for disks bigger than 2 Gig
Remove obsolete -z flag
Remove now unsupported AC_USE_SYSTEM_EXTENSIONS
Fixed output formatting of mdir if MTOOLS_DOTTED_DIR is set
Mformat now correctly writes backup boot sector
Fixed signedness of serial number in mlabel
Fixed buffer size problem in mlabel
Make mlabel write backup boot sector if FAT32
Catch situation where both clear and new label are given to mlabel
Quote filename parameters to scripts
Mformat: Close file descriptor for boot sector
Added lzip support to scripts/uz
Added Tot_sectors option to mformat
Fixed hidden sector handling in mformat
Minfo generates mformat command lines containing new -T option
Mlabel prints error if label too long
3.9.11 is mostly a maintenance release which fixes a couple of bugs,
and addresses warnings raised by gcc4, and merges some platform-specific
patches (MingW, NetBSD, Redhat/Fedora, Cygwin, Solaris), and other
patches (such as the new amuFormat.sh written in sh).
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.
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.
* Support for multiple drives in floppyd
* Updated .spec file
* Fixed some long name directory entry freeing bugs
* Fixed duplicate FAT writing error. Fixed segfault on short images.
* Mformat creates images of correct size.
* CYGWIN compatibility (O_BINARY flag).
* Cygwin patch for plain_io.c (no locking)
* Fix a couple of memory leaks in config file parsing. Fix llong.h
(redefined same symbol twice)
* Fix a variable initialization problem in plain_io.c
* New mclasserase command to erase memory cards
C99 "compatibility" (cf http://www.mtools.linux.lu/download.html)
* Fix rootskip and rate of XDF disks
* Fix inverted IS_MFORMAT_ONLY conditon in plain_io.c
* Moved putc after variable description (anybody knows about a -W
flag so that gcc warns about these?)
* Fixed mattrib -p (missing slash)
* Added -m option to mformat to specify a non-standard mediabyte
* Added -d options to mformat to specify number of FAT copies. Can
also be set using the MTOOLS_NFATS environmental variable.
which are the full option names used to set rpath directives for the
linker and the compiler, respectively. In places were we are invoking
the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is
inserted in case the flag is a word, e.g. -rpath. The default values
of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the
compiler that you use. They may be overridden on a ${OPSYS}-specific
basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG,
respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
* Large disk fixes, especially for Solaris
* Floppyd robustness
* Zip 250 support in mzip
* Protect against division by zero when reading BSD disks
* Fixed parsing of Unix filenames ending with slash
* Fixes for floppyd to work with current protocol version of floppyd
* Warn for invalid partition numbers
* Support for geometry-less Atari disks
* Support for byte-swapping disks
* Fixed max numbers of sectors for FAT12 and FAT16
See ChangeLog for details
- fix device handling on NetBSD ELF (from Pavel Arnost via PR pkg/21530)
- fix floppyd handling in better and simpler way
- don't hardcode -R, use RPATH_FLAG instead
- remove unused cruft, style nits
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.
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.
