Age | Commit message (Collapse) | Author |
|
- Those make targets that are useful to users are just wrappers
around the respective cargo commands, which means that they are
not really necessary. The additional targets are primarily of
use to Sequoia developers, which also means that they are not
very useful to users.
- That did not keep us from prominently advertising the use of
make as a recommended installation mechanism, and that in turn
contributed to some false expectations and confusion.
- For example, a packager used the Makefile because they thought
that that is what we would like them to do. Some users found it
surprising that "sudo make install" ended up running the target
"build-release" even though they had already build using "build".
- People who want to keep using make without every time having to
specify the name of the hidden Makefile can do so by creating a
symbolic link.
|
|
|
|
- There was a confusion on the project page on why does "install"
build the project.
- Provide a documentation with the reasoning based on Neal's
comment.
- See:
https://gitlab.com/sequoia-pgp/sequoia/-/merge_requests/953#note_471764940
- Closes !953.
|
|
- This check no longer makes sense as the crate versions are no
longer in sync.
- Fixes #703.
|
|
Close #660
The changelog documenting cargo's --workspace arrival is
[here](https://github.com/rust-lang/cargo/blob/61a31bc5ff290322d5c025bf750c56501999235d/CHANGELOG.md#added-13).
Note `cargo fmt` still expects `--all` because the subcommand semantics differ.
|
|
|
|
|
|
- From this point on, the crate sequoia-sop will be maintained in
its own repository.
|
|
Closes #581.
|
|
- Fixes 52ee6a8fa2d326ba93fd4cbcf134a231bc438d95.
|
|
|
|
|
|
|
|
- Ingore all target dirs.
- Adapt to new codespell dictionary:
Add keyserver, keypair, dedup, fpr to ingore list.
|
|
|
|
- Add the CARGO_PACKAGES variable to allow the user to restrict the
packages that are built, test, and documented.
- If it contains a package, don't run non-cargo test tests.
|
|
- Add explicit build-release and install targets.
- Explicitly build the crates.
- Move installation to the crate's Makefile.
- This allows building of Sequoia's individual parts, e.g. by using
'make -Copenpgp-ffi install'.
|
|
- Distribute Sequoia as signed OpenPGP message containing the source
tarball, then gzip and xz compress the message.
- Also providing a gzipped distribution helps bootstrapping efforts.
|
|
|
|
|
|
- This adds a new frontend to Sequoia that implements the Stateless
OpenPGP Command Line Interface.
- Compared to sq, sop has a much smaller feature set and hence a
smaller set of dependencies. It is less opinionated, and tries to
faithfully implement the SOP protocol. We will use it to test
Sequoia using the OpenPGP Interoperability Test Suite.
|
|
|
|
|
|
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
|
|
|
|
- Also bump rfc2822 to 0.6.0. After all, we create tags for the
versions.
|
|
- Make tool/build.rs generate completion files into a predictable
location ($CARGO_TARGET_DIR).
- Install completion files.
|
|
|
|
|
|
- docs.sequoia-pgp.org is now handled by
https://gitlab.com/sequoia-pgp/docs.sequoia-pgp.org.
- Fixes #232.
|
|
- Use GNU install, use the correct extension for dynamic libraries.
- Fixes #226.
|
|
- Any place where we execute a build command for the ffi crate, we
should do the same for the openpgp-ffi crate, too.
|
|
|
|
- For C code fragments, we use the highlight.js highlighter to apply
syntax highlighting. Previously, highlight.js was only used in
the FFI documentation, and was loaded from a CDN.
- We now distribute highlight.js with our documentation. This is
done in the 'doc' make target.
- This helps to protect the privacy of users viewing the
documentation.
- Unfortunately, highlighting no longer works when viewing the
documentation locally in a browser using the file:// scheme.
|
|
- This creates a new crate, 'sequoia-openpgp-ffi', and moves a
handful of functions from 'sequoia-ffi' to it.
- The 'sequoia-ffi' crate is a superset of the 'sequoia-openpgp-ffi'
crate. This is accomplished by some include! magic.
- My first attempt involved having 'sequoia-ffi' depend on
'sequoia-openpgp-ffi', so that the former just re-exports the
symbols. However, that turned out to be unreliable, and might be
not what we want, because it could also duplicate parts of Rust's
standard library.
- Fixes #144.
|
|
- This allows us to use sequoia-openpgp without compression support
reducing binary size and trusted computing base.
|
|
- nettle-rs now hosts its own documentation.
|
|
|
|
- Also use 'cargo clean' instead of 'rm -rf $(CARGO_TARGET_DIR)' in
case $(CARGO_TARGET_DIR) is incorrectly set.
|
|
|
|
|
|
|
|
- Until the nettle crate is published, we can build the
documentation here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- This adds some convenience for building Sequoia.
- It also integrates other build systems and test frameworks for the
bindings.
- Furthermore, it helps with creating releases.
|