From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Efraim Flashner <efraim@flashner.co.il>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>,
John Soo <jsoo1@asu.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Revising sequoia packaging
Date: Tue, 30 Nov 2021 13:17:30 +0100 [thread overview]
Message-ID: <9e376f76-c61d-f304-8737-43c42945f349@crazy-compilers.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Hi,
for those who contributed to sequoia packaging:
Currently, sequoia is packages somewhat sub-optimal:
There are some rust-creates in crates-io.scm (rust-sequoia-openpgp-0.9,
rust-sequoia-rfc2822-0.9) and the big sequoia package in sequoia.scm.
The other sequoia crates are currently not available as separate
creates. Future versions of pEp (pretty easy privacy, pep.scm, which
relies on sequoia) will get its own "pEpEngineSequoiaBackend" FFI library.
I propose the following:
* Move all sequoia related crates in to sequoia.scm. As of now these
are only rust-sequoia-openpgp-0.9, rust-sequoia-rfc2822-0.9 and
there is only on package depending on them rust-libpijul-0.12
* bufferedreader, rust-nettle and other crates from the sequoia
project but not having "sequoia" (or such) in the name would be kept
in crates-io.scm
* In sequoia.scm there would be all sequoia crates, with the app
packages named without "rust-" prefix ("sequoia-sq", …)
* The current "sequoia" package will become a "wrapper", just
propagating (or copying, what ever is more common in guix) the other
packages which have an actual output.
WDYT?
--
Regards
Hartmut Goebel
| Hartmut Goebel |h.goebel@crazy-compilers.com |
|www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 1948 bytes --]
next reply other threads:[~2021-11-30 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 12:17 Hartmut Goebel [this message]
2021-11-30 12:34 ` Revising sequoia packaging Efraim Flashner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e376f76-c61d-f304-8737-43c42945f349@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
--cc=mail@nicolasgoaziou.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).