diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml index 2ba0614ad2..5ef5005420 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml @@ -3287,4 +3287,84 @@ + + mtree Parsing and Manipulation Library + + + + + Michal + Ratajsky + + michal@FreeBSD.org + + + + + Brooks + Davis + + brooks@FreeBSD.org + + + + + Wiki + page + + + +

&os; includes several programs that work with file system + hierarchy descriptions in the mtree(5) format. These + descriptions, also called specifications, have a broad range of + uses, from automatically creating directory structures to security + auditing.

+ +

Each of the programs, namely mtree, + bsdtar, install, and makefs, + has its own implementation of the mtree format. This not only + adds maintenance overhead, but also makes interoperability + difficult, as each of the implementations only supports a limited + subset of the format.

+ +

The goal of this project was to create a new + libmtree library, implementing everything the mtree + format has to offer, and wrapping it with an expressive API which + all the listed programs can use. We also wanted libmtree + to be portable, as one of the major users of the mtree format is + libarchive, the library implementing most of + bsdtar.

+ +

Currently, the library is functionally complete, ready to + be downloaded and receive everyone's attention. We've also + decided to bundle the mtree program along with it. The + bundled mtree has also been modified for better + portability

+ +

The project also included modifying libarchive, + install and makefs to use libmtree. These + modified versions are also available.

+ +

Please see the Wiki page for more information, download + locations and an example of using the libmtree API. +

+ + + + Google Summer of Code 2015 + + + + +

Test and review the library code and API and the modifications + made to the programs.

+ + + +

Fix the known problems that are mentioned on the Wiki + page.

+ + + +