On 2018-10-03 21:03:22, John Goerzen wrote: > Package: wnpp > Severity: wishlist > Owner: John Goerzen <jgoer...@complete.org> > > * Package name : mtree-netbsd > Version : 20180822 > Upstream Author : Joerg Sonnenberger <jo...@netbsd.org> and NetBSD > contributors > * URL : > http://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/pkgtools/mtree/README.html > * License : BSD > Programming Lang: C > Description : Validates modes, ownership, and contents of directory > tree against specification > > The mtree utility compares a file hierarchy against a specification, > creates a specification for a file hierarchy, or modifies a specification. > This specification can be controlled by the user, but typically includes > file/directory/symlink names, ownership information, permission bits, and > so forth. It may optionally also include various hashes, such as SHA-256 > or MD5. > . > This mtree utility can understand its own files, as well as those generated > by the FreeBSD mtree (in Debian as fmtree in freebsd-buildutils and > freebsd-glue) and bsdtar/libarchive.
Why do we need NetBSD's mtree when we have freebsd's already? I don't mind much the duplication: I'm genuinely curious. :) (I have also wondered for a long time why we don't have simply a `mtree` package in Debian - it's a very useful tool to have!) a. -- During times of universal deceit, telling the truth becomes a revolutionary act. - Georges Orwell
