Add libarchive entry from mm

This commit is contained in:
Benjamin Kaduk 2017-01-09 01:42:37 +00:00
parent 4c061fbead
commit 922cb7b91b
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=49809

View file

@ -255,4 +255,65 @@
<tt>lirc</tt> with dfrobot's simple IR remote controller.</p> <tt>lirc</tt> with dfrobot's simple IR remote controller.</p>
</body> </body>
</project> </project>
<project cat='bin'>
<title>libarchive</title>
<contact>
<person>
<name>
<given>Tim</given>
<common>Kientzle</common>
</name>
<email>kientzle@FreeBSD.org</email>
</person>
<person>
<name>
<given>Martin</given>
<common>Matuska</common>
</name>
<email>mm@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://www.libarchive.org">Official Libarchive Homepage</url>
<url href="https://github.com/libarchive/libarchive">Libarchive on GitHub</url>
</links>
<body>
<p>Libarchive is a BSD-licensed archive and compression library
originally developed as part of &os;. It supports a wide
variety of input and output formats and also includes three
command-line tools: <tt>bsdcat</tt>, <tt>bsdcpio</tt> and
<tt>bsdtar</tt>. The &os; <tt>tar</tt> and <tt>cpio</tt>
utilities are taken directly from Libarchive, and many other
important utilities like <tt>ar</tt>, <tt>unzip</tt>, and the
<tt>pkg</tt> package manager make use of <tt>libarchive</tt>'s
functions.</p>
<p>Libarchive development in 2016 has been focusing on bug fixes
and code cleanup, including fixing several critical security
issues. Automated testing with Travis CI and Jenkins has been
introduced and <tt>libarchive</tt> has been added to the Google
OSS-Fuzz project. Fuzzing helped detect several hidden problems
like buffer overflows and memory leaks.</p>
<p>Over the last few months, NFSv4 ACL support for the pax and
restricted pax (the default for <tt>bsdtar</tt>) formats has
been completed and merged to &os;-CURRENT. NFSv4 ACL entries
can now be stored to and restored from tar archives.</p>
</body>
<help>
<task>More extensive CI testing with &os; on different platforms
and releases. Currently only 11.0-RELEASE-amd64 gets tested via
an automated Jenkins job.</task>
<task>As every commit to libarchive may influence the build
process of &os; ports, the ability to trigger a (semi-)automated
exp-run for the ports tree would be great.</task>
</help>
</project>
</report> </report>