[aur-general] Proposal: Mark packages that require significant computational power to build
Hello everyone, as you know, some packages on AUR take many minutes to build on all but very powerful machines. I think it would be helpful to have an optional bit of metadata that will mark these packages, or possibly even a general thing that will describe approximately how intensive the package is to build. Writing this as freecad-git melts my laptop.
On 4/3/20 3:24 PM, Nick Shvelidze wrote:
Hello everyone, as you know, some packages on AUR take many minutes to build on all but very powerful machines. I think it would be helpful to have an optional bit of metadata that will mark these packages, or possibly even a general thing that will describe approximately how intensive the package is to build.
Writing this as freecad-git melts my laptop.
A pinned comment could do this today. Most users of such software I think know that they are heavyweight software, to be honest. Either way, this is not going to be an official PKGBUILD variable as defined by makepkg and stored in the .SRCINFO, because it is out of scope for makepkg. I guess it could be discussed as a potential feature for e.g. a checkbox in the AUR web interface. There's a slightly similar feature request at https://bugs.archlinux.org/task/56602 asking for a checkbox for "this is a VCS package". -- Eli Schwartz Bug Wrangler and Trusted User
On Fri 03 Apr 2020 23:24 +0400, Nick Shvelidze wrote:
Hello everyone, as you know, some packages on AUR take many minutes to build on all but very powerful machines. I think it would be helpful to have an optional bit of metadata that will mark these packages, or possibly even a general thing that will describe approximately how intensive the package is to build.
Neat idea but too arbitrary unless you can figure out a way to quantify or measure an 'intensity score' in a scientific manner. An 'intensive' package for raspi will be very different for notebook, workstation, server, etc. Would also be neat to have runtime requirements in package metadata. Could lead to something similar to "Windows Experience Index"
On 4/3/20 6:55 PM, Loui Chang wrote:
Neat idea but too arbitrary unless you can figure out a way to quantify or measure an 'intensity score' in a scientific manner.
Linux From Scratch uses a Standard Build Unit (SBU) to quantify build times. They chose to use the time it takes to build binutils as the SBU. All other package compile times are expressed relative to it.
On 05/04/2020 23:13, Paul Hentschel wrote:
On 4/3/20 6:55 PM, Loui Chang wrote:
Neat idea but too arbitrary unless you can figure out a way to quantify or measure an 'intensity score' in a scientific manner.
Linux From Scratch uses a Standard Build Unit (SBU) to quantify build times. They chose to use the time it takes to build binutils as the SBU. All other package compile times are expressed relative to it.
Just add a marker whenever the project uses C++. 😶 Alad
participants (5)
-
alad
-
Eli Schwartz
-
Loui Chang
-
Nick Shvelidze
-
Paul Hentschel