[SOLVED] why downloading the whole package ..?

ardv · 2024-09-26 07:15:06

if the pacakge update is just in the PKGBUILD and not in the tar file, why the update re-download the whole package?
for example:
extra/firefox 130.0.1-1 -> 130.0.1-2 : output from yay
why the updated will re-download the firefox tar? is there a way to let if just use the old one to save some connection bandwidth when updating?

Last edited by ardv (2024-09-26 09:06:37)

seth · 2024-09-26 07:42:57

1. don't use yay
2. don't use any pacman wrappers
3. unless this is an AUR package (which extra/firefox is NOT) you're downloading the updated, rebuilt package - 130.0.1-1 and 130.0.1-2 are explicitly NOT the same.
When you're re-building an AUR package locally and the upstream source hasn't changed and you still have a local copy, there's no reason to re-download it. I'd buy that yay would still if you'd complain, but don't think that's actually the case.

tl;dr - firefox-130.0.1-1-x86_64.pkg.tar.zst and firefox-130.0.1-2-x86_64.pkg.tar.zst are NOT the same tarball and do NOT contain the same binaries.
Of course you can always build and rebuild the broswer locally - it will only take some hours on an 16-core system with 64GB RAM or so.

ardv · 2024-09-26 07:46:06

seth wrote:

1. don't use yay
2. don't use any pacman wrappers
3. unless this is an AUR package (which extra/firefox is NOT) you're downloading the updated, rebuilt package - 130.0.1-1 and 130.0.1-2 are explicitly NOT the same.
When you're re-building an AUR package locally and the upstream source hasn't changed and you still have a local copy, there's no reason to re-download it. I'd buy that yay would still if you'd complain, but don't think that's actually the case.
tl;dr - firefox-130.0.1-1-x86_64.pkg.tar.zst and firefox-130.0.1-2-x86_64.pkg.tar.zst are NOT the same tarball and do NOT contain the same binaries.
Of course you can always build and rebuild the broswer locally - it will only take some hours on an 16-core system with 64GB RAM or so.

thank you.
and why you advise not to use yay?

seth · 2024-09-26 07:54:40

Because pacman wrappers blur the lines between the AUR and the repos, make you not understand how things work under the hood and yay is particularly buggy, https://bbs.archlinux.org/viewtopic.php … 0#p2148350

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

cryptearth · 2024-09-26 08:32:10

off-topic
@seth
I have a ryzen 5600 and 32gb ram - does compiling firefox from source really take several hours even when fully utilizing all available system resources?

seth · 2024-09-26 08:43:40

The browsers are fat beasts - build time will depend on the available resources (RAM is a huge factor, 32GB RAM should™ still be enough), the sideload (not when you're also processing some huge database at the time) and the compiler options and build style. But I might also have been exaggerating for dramatic effect a bit
https://firefox-source-docs.mozilla.org … /slow.html

Arch Linux

#1 2024-09-26 07:15:06

[SOLVED] why downloading the whole package ..?

#2 2024-09-26 07:42:57

Re: [SOLVED] why downloading the whole package ..?

#3 2024-09-26 07:46:06

Re: [SOLVED] why downloading the whole package ..?

#4 2024-09-26 07:54:40

Re: [SOLVED] why downloading the whole package ..?

#5 2024-09-26 08:32:10

Re: [SOLVED] why downloading the whole package ..?

#6 2024-09-26 08:43:40

Re: [SOLVED] why downloading the whole package ..?

Board footer