From: Leo Famulari <leo@famulari.name>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: rav1e AV1 encoder
Date: Thu, 27 Feb 2020 12:16:02 -0500 [thread overview]
Message-ID: <20200227171602.GA30619@jasmine.lan> (raw)
In-Reply-To: <20200226070905.GD12956@E5400>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
On Wed, Feb 26, 2020 at 09:09:05AM +0200, Efraim Flashner wrote:
> 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.
Okay.
> 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.
Right, but keeping Guix building without "undefined variable" warnings
is what I'm worried about here.
> 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.
Hm... you're saying they sometimes bundle C / C++ language libraries?
> > 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.
Certbot is special in the sense that certbot and python-acme are
actually developed in the same Git repo but are split up for PyPi
distribution in the hope that other projects will build on python-acme.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-27 17:16 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
2020-02-27 17:16 ` Leo Famulari [this message]
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
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=20200227171602.GA30619@jasmine.lan \
--to=leo@famulari.name \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
/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).