public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: "Cygwin findutils co-Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: findutils 4.9
Date: Sat, 05 Feb 2022 15:18:38 -0700	[thread overview]
Message-ID: <20220205151838.39146-1-Brian.Inglis@SystematicSW.ab.ca> (raw)

The following packages have been upgraded in the Cygwin distribution:

* findutils	4.9

The findutils package contains programs which will help you locate files
on your system.
The find utility searches through a hierarchy of directories looking for
files which match a certain set of criteria (such as a filename pattern).
The xargs utility builds and executes command lines from standard input
arguments (usually lists of file names generated by the find command).
The locate utility scans a database of filenames and displays matches.
The updatedb utility builds the database for locate.

For more information see the project home page:

	https://www.gnu.org/software/findutils/

Please see below or read /usr/share/doc/findutils/NEWS after
installation for details of changes since the previous release:

	https://git.savannah.gnu.org/cgit/findutils.git/tree/NEWS


Noteworthy changes in release 4.9.0 (2022-02-22) [stable]

New features in find

* find now supports the -files0-from option to be able to safely pass an
  arbitrary number of starting points to the tool. The option requires a
  file name as argument, or "-" to read from standard input. The entries
  in that file have to be separated by NUL characters.

Changes in locate / updatedb

* updatedb now skips (fuse-mounted) s3fs filesystems by default, i.e.,
  unless PRUNEFS is set.

Bug Fixes

* 'find -D stat -L ...' no longer determines SELinux security
  information as if the -L option was not given.

* 'find -inum' and 'find -printf %i' now also work on platforms which
  allow the inode number Zero; e.g. the GNU/Hurd uses inode number 0 for
  /dev/console. Previously, find(1) would abort when visiting such a
  file.

* findutils-4.8.0 failed to build on some MacOS versions. Fixed by a
  gnulib update.

Documentation Changes

* The find.1 man page and the Texinfo manual now show environment
  variables in a consistent style.

* Furthermore, both add the description of the -printf format directive
  '%B', for a file's birth time, and its limitations.

* The description of the -delete action has been improved and aligned
  among the manual page and the Texinfo documentation.

* Various other documentation fixes - syntax issues and typos.

* The output of 'find --help' now reads better.

* The HTML online manual is using the official GNU stylesheet again.

Changes to the build process

* The find version without FTS, oldfind, has been completely removed. It
  has not been installed since 4.5.18 (2015), and was only still used in
  tests.


                 reply	other threads:[~2022-02-05 22:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220205151838.39146-1-Brian.Inglis@SystematicSW.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-announce@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).