undefined | Better HN

0 pointsbeanaroo6y ago0 comments

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

0 comments

SamWhited6y 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.

SamWhited6y ago

I don't really care about space all that much, but packages I build tend to get uploaded and the people downloading them may not have fast internet. Meanwhile, packages built by my AUR helper I care about speed (seriously, it takes ages to compress then immediately decompress firefox). The problem isn't that I want to optimize for one or the other, it's that AUR helpers generally have a different need than I do when building my packages myself, but for some reason AUR helpers don't override the compression setting for just their install. Probably due to caching like I said which means they can't assume everyone will want compression off all the time, but I'm not sure, that's just a guess.

ncmncm6y ago

I doubt anybody today has legitimately enough reason to care about space to prefer xz over zstd. The only plausible reason is that some customer, or customer's customer, is only equipped to unpack archaic formats.

j / k navigate · click thread line to collapse

0 comments

SamWhited6y 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.

SamWhited6y ago

ncmncm6y ago

j / k navigate · click thread line to collapse