all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: rav1e AV1 encoder
Date: Wed, 26 Feb 2020 09:09:05 +0200	[thread overview]
Message-ID: <20200226070905.GD12956@E5400> (raw)
In-Reply-To: <20200226041429.GA1225@jasmine.lan>

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

On Tue, Feb 25, 2020 at 11:14:29PM -0500, Leo Famulari wrote:
> On Tue, Feb 25, 2020 at 01:21:18PM -0800, John Soo wrote:
> > You should be committing packages in topological order but the file
> > order is alphabetical. 

This is at least partially my fault; I suggested that the packages be
sorted alphabetically after a recursive import. It works well for adding
them all in one channel, not so well for adding them piecemeal to Guix.

> > 
> > Good luck, rust is a ton of work.
> 
> Okay, that makes sense.
> 
> I tried to use `guix graph` to learn the shape of the package graph but
> it doesn't work as expected since these packages don't refer to their
> dependencies in the typical way. I thought that using the 'derivation'
> graph type might help but I don't think that I can process it on my
> computer `dot`. It's been going for hours now...

This is because we technically use the package-source of the packages,
not the packages themselves.

> 
> Many of the "new packages" are actually semver-compatible updates to
> existing packages, and these updates often change the list of
> cargo-inputs dependencies.

Short of resorting them I'd start with ones that have no dependencies,
just rely on rust-quote & friends or are older versions. Some packages,
like rust-futures-*, should be updated as a group since they all expect
to be the same version.

> 
> Given that, I don't know how to learn the right order of things to
> commit one at a time that will never break the build.
> 

The only real builds that we care about are the packages in rust-apps
and librsvg-next (and librsvg-next is less important). And of course
that we don't reference packages that don't exist yet.

The ones that I spend the most amount of time reviewing are the ones
that end in -sys or otherwise reference system libraries. Sometimes more
effort is needed to unbundle libraries. In general anything that wants
rust-{cc,cmake,pkg-config} is suspect.

> Would we have the same issue with updating this kind of large package
> tree automatically with `guix refresh` and committing the changes one at
> a time?
> 

Sometimes. We do have other upgrades where we go and do a bunch at once,
where they rely on each other and expect specific versions. The first
thing I can think of is certbot.

-- 
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-02-26  7:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 22:43 rav1e AV1 encoder Leo Famulari
2020-02-21  9:15 ` Martin Becze
2020-02-21 16:16   ` Leo Famulari
2020-02-21 16:41   ` Leo Famulari
2020-02-21 16:43     ` Martin Becze
2020-02-21 16:46     ` Martin Becze
2020-02-21 16:56       ` Leo Famulari
2020-02-22 11:09         ` Martin Becze
2020-02-22 22:41           ` Leo Famulari
2020-02-24 11:02             ` Martin Becze
2020-02-25 20:08   ` Leo Famulari
2020-02-25 21:21     ` John Soo
2020-02-26  4:14       ` Leo Famulari
2020-02-26  7:09         ` Efraim Flashner [this message]
2020-02-27 17:16           ` Leo Famulari
2020-02-28 13:24             ` Efraim Flashner
2020-02-27 17:26           ` Leo Famulari
2020-02-28 13:30             ` Efraim Flashner
2020-02-28 17:04             ` Martin Becze
2020-04-02 22:31   ` sorting Rust crates [was Re: rav1e AV1 encoder] Leo Famulari
2020-04-12 15:22     ` Martin Becze
2020-04-14 20:08       ` Martin Becze
2020-04-26 17:05 ` rav1e AV1 encoder Efraim Flashner
2020-04-26 17:47   ` Leo Famulari
2020-04-26 17:48   ` Leo Famulari
2020-04-26 17:53     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200226070905.GD12956@E5400 \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.