unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 45276@debbugs.gnu.org
Subject: [bug#45276] [PATCH 00/26] Update sequoia-opengpg to 1.0.0
Date: Thu, 17 Dec 2020 22:08:58 +0200	[thread overview]
Message-ID: <X9u62uXj6nEbuonK@E5400> (raw)
In-Reply-To: <afa5f84c-4e44-35ba-19e3-4dad3e71fcb7@crazy-compilers.com>

[-- Attachment #1: Type: text/plain, Size: 2340 bytes --]

On Thu, Dec 17, 2020 at 05:05:58PM +0100, Hartmut Goebel wrote:
> Hi Nicolas,
> > 
> > I think the big warning in rust-dbl-0.3's description could be removed.
> 
> Fine for me. will do.
> 
> 
> > Also, I notice you often skip builds, even though this is not required.
> > E.g., I could build rust-pin-utils-0.1 without any problem just removing
> > the #:skip-build keyword. I think the trend is use #:skip-build only
> > when absolutely necessary.
> 
> Building crate "libraries" is of no use. Rust still has no notion of
> "libraries", neither shared not static. it does not even provide any means
> to use "object"-files from another package. All crates will be build again
> and again for each package using it. And you will notice that the output of
> most crates will be almost empty (only exception: if the crate build a
> program).
> 
> This is why the crates importer sets skip-build for all packages it imports
> as dependencies. (It also does not add the crate-build-dependencies for
> these packages.)

I'm in favor of building the packages anyway, it serves as a check that
the inputs are actually correct.

> > Finally, I wonder if replacements, e.g., rust-capnp-futures-0.10 by
> > rust-capnp-futures-0.13, require to remove the old variable. It could be
> > used out of the code base.
> 
> We are lacking a common practice on this yet. IMO it does not make much
> sense to provide packages for old crates. crates are using semantic
> versioning, so in the long run we might end up maintaining hundreds of old
> packages.
> 
> Concrete for this bunch of packages: These have been added by myself when
> packaging sequoia last April. So maybe thos turns the balance :-)
> 

As long as you're sure there's nothing else in tree that's depending on
it, I suppose it's ok to remove them. I view it similarly when I clean
up package names to drop not significant digits from the versioning in
the name, ie rust-slog-2.5 -> rust-slog-2.

If the rust ecosystem slows down some I'd be happy to keep more versions
but it's already one of the largest package modules we have.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-12-17 20:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 20:31 [bug#45276] [PATCH 00/26] Update sequoia-opengpg to 1.0.0 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 01/26] gnu: Add rust-cipher-0.2 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 02/26] gnu: Add rust-cmac-0.5 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 03/26] gnu: Add rust-ctr-0.6 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 04/26] gnu: Add rust-dbl-0.3 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 05/26] gnu: Add rust-eax-0.3 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 06/26] gnu: Add rust-sha1collisiondetection-0.2 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 07/26] gnu: Add rust-crypto-mac-0.10 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 08/26] gnu: Add rust-pin-utils-0.1 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 09/26] gnu: Add rust-pin-project-1, rust-pin-project-internal-1 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 10/26] gnu: Replace rust-capnp-0.10 by rust-capnp-0.13 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 11/26] gnu: Replace rust-capnp-futures-0.10 by rust-capnp-futures-0.13 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 12/26] gnu: Replace rust-capnp-rpc-0.10 by rust-capnp-rpc-0.13 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 13/26] gnu: Replace rust-capnpc-0.10 by rust-capnpc-0.13 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 14/26] gnu: Replace rust-win-crypto-ng-0.2 by rust-win-crypto-ng-0.4 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 15/26] gnu: rust-proc-macro-hack-0.5: Update to 0.5.19 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 16/26] gnu: rust-socket2: Update to 0.3.18 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 17/26] gnu: rust-futures-util-0.3: Update to 0.3.8 Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 18/26] gnu: rust-futures-0.3: " Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 19/26] gnu: rust-futures-channel-0.3: " Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 20/26] gnu: rust-futures-core-0.3: " Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 21/26] gnu: rust-futures-executor-0.3: " Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 22/26] gnu: rust-futures-io-0.3: " Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 23/26] gnu: rust-futures-macro-0.3: " Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 24/26] gnu: rust-futures-sink-0.3: " Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 25/26] gnu: rust-futures-task-0.3: " Hartmut Goebel
2020-12-16 20:36 ` [bug#45276] [PATCH 26/26] gnu: sequoia: Update to 1.0.0 Hartmut Goebel
2020-12-17 15:01 ` [bug#45276] [PATCH 00/26] Update sequoia-opengpg " Nicolas Goaziou
2020-12-17 16:05   ` Hartmut Goebel
2020-12-17 20:08     ` Efraim Flashner [this message]
2021-01-06 18:05       ` Hartmut Goebel
2021-01-06 19:37         ` Leo Famulari
     [not found] ` <handler.45276.B.160815072411765.ack@debbugs.gnu.org>
2021-01-08  9:35   ` bug#45276: Acknowledgement ([PATCH 00/26] Update sequoia-opengpg to 1.0.0) Hartmut Goebel

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=X9u62uXj6nEbuonK@E5400 \
    --to=efraim@flashner.co.il \
    --cc=45276@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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).