Thomas Mühlbacher 48c51020e5 build: rm package.version from Cargo.toml
This sets the version, that can be read at build time using the
environment variable `CARGO_PKG_VERSION`, to the default
value (`0.0.0`).

Setting `package.version` in the Cargo manifest is mandatory for
publishing to crates.io. We're not publishing the crate currently, and
there isn't an obvious case for doing so in the future that comes to
mind.

Our sources are not using the version from cargo currently. `clap` and
some other dependencies may use them by default but still we don't use
that version in any outputs. Therefore, we should be fine without it.

Signed-off-by: Thomas Mühlbacher <tmuehlbacher@posteo.net>
2024-07-21 01:16:28 +02:00
2024-07-17 11:24:07 +02:00
2024-07-20 16:45:08 -04:00
2024-05-29 09:22:09 +05:30
2024-07-15 23:34:58 -04:00
2024-05-29 09:22:09 +05:30
2024-01-11 23:55:39 -08:00
2024-05-29 09:22:09 +05:30
2024-07-20 16:45:08 -04:00
2023-12-06 15:41:05 -05:00
2024-01-16 17:17:23 -05:00
2013-07-17 13:13:31 -07:00
2024-05-22 22:35:05 +02:00
2024-06-17 18:20:02 +00:00
2024-07-12 14:14:55 -04:00
2024-07-18 20:48:14 -04:00
2024-05-26 20:38:08 -04:00

bcachefs-tools

Userspace tools and docs for bcachefs

Bcachefs is an advanced new filesystem for Linux, with an emphasis on reliability and robustness and the complete set of features one would expect from a modern filesystem.

This repo primarily consists of the following:

  • bcachefs tool, the reason this repo exists.
  • {mkfs,mount,fsck}.bcachefs utils, which is just wrappers calling the corresponding subcommands in the main tool
  • docs in the form of man-pages and a user manual

Please refer to the main site for getting started An in-depth user manual is (also) found on the official website

Version semantics

The tools relies on an expected disk format structure which is reflected by your current kernel version. Disk format can be upgraded or downgraded automatically by the kernel, if needed.

  • Any patch-level change means no disk format change
  • Any minor-level change means a potential disk format change which is not breaking
  • Any major-level change means breaking changes

Build and install

Refer to INSTALL.md

Bug reports and contributions

Description
Languages
C 95.6%
C++ 2%
Rust 1.4%
Roff 0.4%
Nix 0.2%
Other 0.4%