[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#898400: ITP: sccache - compiler cache for fast recompilation of C/C++/Rust code



Quoting Blair Noctis (2022-09-01 14:52:42)
> I see that you've removed some dependencies of dist-* feature and for
> Windows, which I didn't realize could be done. However I'm not sure
> why the redis, memcached, gcs, azure, s3 features are removed.

They are removed to get sccache into Debian sooner: When additional
dependencies are in Debian we can link against those as well.


> zstd is 0.5.1 in unstable, 0.11 on crates.io. I tried 0.11 on it with
> no errors. But there's #969609 [1], not sure if I should push it.

I don't understand what you mean by "push it". What needs doing
regarding bug#969609 is (as I see it, but the bug belongs in the Rust
team so I contradict anything said in that team then listen to them!) to
package rust-zstd-safe - as indicated in the subject of that bugreport.


> uuid is 0.8.1 in unstable, 1.1 on crates.io. Patching it is fairly
> easy:

Nice that patching is easy.  Better would be to upgrade rust-uuid, but
until that is done I am ok carrying a patch with sccache.  Thanks!


> counted-array, local-encoding, pulldown-cmark, skeptic, tokio-serde,
> tower, tower-layer are packaged locally, with local-encoding patched
> to use skeptic 0.13 instead of 0.4, removing the dependency on
> tempdir. I'll push them later on.

Again, not sure what you mean by "push them" - perhaps you are talking
Rust-team lingo of pushing to the all-crates-in-one-giant-git repo -
which I in Debian lingo would call packaging officially for Debian.

NB! I don't mean to say that you are saying it wrong - only genuinely
that I am uncertain what you mean: As I understand it, Rust team
deliberately is "more Rust-like than Debian-like" to lower the bar for
newcomers - where I consider it important for Debian packaging to be
"more Debian-like" to ease the long-term maintenance.  I certainly don't
want to discourage newcomers in Debian - just tell you up front whenever
your lingo confuses me and I hope you will do the same :-)


> Btw, do you mind using salsa's issues and merge requests, or prefer
> emails?

I prefer not having to use Salsa - but I am not a hardcore
do-it-all-with-mail either: I prefer pushing to git and then share in
email an URI to wherever you pushed it - e.g. a git clone or (when you
have write access) a temporary branch (I like the naming scheme wip/*
for such throwaway branches).

Speaking of write access: You should now have access to the repo in
Salsa: https://salsa.debian.org/debian/sccache


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature


Reply to: