undefined | Better HN

0 pointsSamWhited6y ago0 comments

I love the AUR, but every single time I have to wait for it to compress Firefox nightly, and then wait for it to immediately decompress it again because the only reason I was building the package in the first place was to install it I about lose my mind. Hopefully this helps, but I really wish AUR helpers would just disable compression and call it a day so I don't have to go mess with config files that would also change my manual package building routine.

EDIT: nevermind, this doesn't seem to have made this the default for building packages locally, just for ones you download from the official repos. Guess I'll go change that by hand and then still be sad that I can't have it easily disabled entirely for AUR helpers but build my packages with compression.

0 comments

beanaroo6y ago

This isn't a function of an AUR helper but rather makepkg itself.

In makepkg.conf, ommit compression by specifying:

    PKGEXT='.pkg.tar'

More information can be found at https://wiki.archlinux.org/index.php/Makepkg#Tips_and_tricks

SamWhitedOP6y ago

Then it happens for packages I build myself (and want compressed) and those that I just want to install.

sigotirandolas6y ago

You can also override PKGEXT as an environment variable when invoking makepkg, so you can have compression by default but easily skip it when it matters:

  PKGEXT=.pkg.tar makepkg

EDIT: By the way, it's often a big win to use multithreaded compression (pigz, zstd -T0, etc.) in makepkg.conf. With this, it's fast enough that I hardly ever override PKGEXT anymore.

zerogara6y ago

If you care about space more than you care about speed you may want to stick with xz, it is hard to beat or impossible by zstd. So set your own priorities rather than adopt the ones of Arch devs.

As long as there will be support within the tools for xz individual builders of packages for their own use can use either or more.

2 more replies

thenewnewguy6y ago

> EDIT: nevermind, this doesn't seem to have made this the default for building packages locally, just for ones you download from the official repos. Guess I'll go change that by hand and then still be sad that I can't have it easily disabled entirely for AUR helpers but build my packages with compression.

I believe you can supply it via an environment variable if your AUR helper has the ability to set those for `makepkg`.

SamWhitedOP6y ago

I'll have to experiment with that, thanks. Still, I don't understand why they don't just do it for me. Maybe they're aggressively caching packages and don't want to take the size hit or something.

j / k navigate · click thread line to collapse

0 pointsSamWhited6y ago0 comments

0 comments

beanaroo6y ago

This isn't a function of an AUR helper but rather makepkg itself.

In makepkg.conf, ommit compression by specifying:

    PKGEXT='.pkg.tar'

More information can be found at https://wiki.archlinux.org/index.php/Makepkg#Tips_and_tricks

SamWhitedOP6y ago

Then it happens for packages I build myself (and want compressed) and those that I just want to install.

sigotirandolas6y ago

You can also override PKGEXT as an environment variable when invoking makepkg, so you can have compression by default but easily skip it when it matters:

  PKGEXT=.pkg.tar makepkg

EDIT: By the way, it's often a big win to use multithreaded compression (pigz, zstd -T0, etc.) in makepkg.conf. With this, it's fast enough that I hardly ever override PKGEXT anymore.

zerogara6y ago

If you care about space more than you care about speed you may want to stick with xz, it is hard to beat or impossible by zstd. So set your own priorities rather than adopt the ones of Arch devs.

As long as there will be support within the tools for xz individual builders of packages for their own use can use either or more.

2 more replies

thenewnewguy6y ago

I believe you can supply it via an environment variable if your AUR helper has the ability to set those for `makepkg`.

SamWhitedOP6y ago

I'll have to experiment with that, thanks. Still, I don't understand why they don't just do it for me. Maybe they're aggressively caching packages and don't want to take the size hit or something.

j / k navigate · click thread line to collapse