使用 Homebrew 安装 exiv2

项目链接

• 主页
• 仓库

命令和别名

• exiv2

项目历史

The Exiv2 project history says Andreas Huggel originally created Exiv2 to fix photos with incorrect Exif timestamps, then turned it into a proof of concept for reading and writing Exif makernotes after discussion with people at Kodak. Andreas first published it on the Internet in 2004.

The project grew from a personal utility into a library and toolchain. Early contributors added IPTC support, Microsoft Visual C++ project files, an I/O abstraction layer, a generalized image class, public bug tracking, and repository hosting. Later work added broader format support, CMake and Visual Studio build support, ICC profile handling, file-dump features, and documentation around the Exiv2 architecture.

采用历史

Exiv2's own project-history page names UFRaw and digiKam as notable early adopters, and says GIMP, Shotwell, Darktable, and PhotoFlow use libexiv2. That places Exiv2 in the desktop photography and raw-image workflow world rather than only in command-line batch processing.

The project also developed a wrapper and ecosystem story: the history page mentions pyexiv2 as a separate Python wrapper project, and the manual points users to the GitHub source, sample programs, metadata tables, architecture book, and contributor graph.

使用方式

The exiv2 command reads, writes, modifies, extracts, inserts, deletes, adjusts, renames, and prints metadata across supported image formats. The manual emphasizes Exif, IPTC, XMP, makernote tags, comments, ICC profiles, thumbnails, and previews, with optional conversion between metadata families according to relevant standards and Metadata Working Group guidance.

Exiv2 has a small user configuration surface: an optional .exiv2 file on Unix-like systems and exiv2.ini on Windows, searched first in the current directory and then in the user's home directory. That file lets users add lens definitions for translated metadata output.

为什么软件包爱好者会关心

Package maintainers care about Exiv2 because image metadata parsers sit on hostile file boundaries: desktop applications, photo managers, and batch tools may all parse camera files downloaded from elsewhere. Exiv2 packages therefore tend to be watched both for feature coverage and for parser/security fixes.

Exiv2 is also a useful comparison point with ExifTool. The Exiv2 FAQ says Exiv2's C++ implementation makes it faster and easier to integrate into C, C++, and Objective-C applications, while ExifTool has the broader feature set. That tradeoff explains why both tools coexist in package repositories.

时间线

• 2004: Andreas Huggel first published Exiv2 on the Internet.
• 2012-2013: Google Summer of Code contributors added video support and Web Ready functionality.
• 2014: Robin Mills retired and Exiv2 v0.25 added a build server.
• 0.26: Maintenance release focused on CMake, Visual Studio support, ICC profiles, and file-dump features.

Related projects

• ExifTool is the common comparison point: broader metadata coverage, implemented in Perl.
• UFRaw, digiKam, GIMP, Shotwell, Darktable, and PhotoFlow are named by Exiv2's history page as users of libexiv2.
• pyexiv2 is the Python wrapper project mentioned by Exiv2's project history.

来源

• https://dev.exiv2.org/projects/exiv2/wiki/What_was_the_motivation_for_creating_Exiv2
• https://exiv2.org/manpage.html
• https://dev.exiv2.org/projects/exiv2/wiki/How_does_Exiv2_compare_to_Exiftool
• https://exiv2.org/book/