Skip to content

LINBIT/lbautospec

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

lbautospec

Similar to rpmautospec, but for LINBIT-flavored projects.

Usage

TL;DR, use this in projects:

# For spec files
$ lbautospec rpm generate project.spec.in > project.spec

# For debian changelog
$ lbautospec deb changelog > debian/changelog

For RPM spec files, the generate subcommand replaces the @VERSION@ and @CHANGELOG@ placeholders in the .spec.in file with the actual version and generated changelog.

The version is the latest git tag, with a potential v prefix removed, and -rc replaced by ~rc.

The changelog for spec files as well as debian/changelog is generated from git; every tag gets its own changelog entry.

Advanced Usage

There are also subcommands to generate only the version and changelog. Mostly useful for debugging, maybe also for scripting.

$ lbautospec rpm version
1.5.1

$ lbautospec rpm changelog
* Mon Feb 05 2024 Christoph Böhmwalder <christoph.boehmwalder@linbit.com> - 1.5.1-1
- Release v1.5.1

* Thu Jan 11 2024 Christoph Böhmwalder <christoph.boehmwalder@linbit.com> - 1.5.1~rc.1-1
- Release v1.5.1-rc.1

* Thu Jan 11 2024 Christoph Böhmwalder <christoph.boehmwalder@linbit.com> - 1.5.0-1
- Release v1.5.0
[...]

Why not use rpmautospec directly?

The key differences are:

  1. rpmautospec is designed specifically for RPM spec files, while lbautospec also supports Debian changelogs.
  2. lbautospec also populates the Version: field in the spec file, not just the release and changelog.
  3. We use specific conventions for versioning and changelog formatting at LINBIT, which lbautospec adheres to.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Languages