Package Details: preload 0.6.4-7

Git Clone URL: https://aur.archlinux.org/preload.git (read-only, click to copy)
Package Base: preload
Description: Makes applications run faster by prefetching binaries and shared objects
Upstream URL: http://sourceforge.net/projects/preload
Licenses: GPL2
Submitter: xyproto
Maintainer: francoism90
Last Packager: francoism90
Votes: 188
Popularity: 1.04
First Submitted: 2013-07-18 22:02 (UTC)
Last Updated: 2020-04-18 08:49 (UTC)

Latest Comments

1 2 Next › Last »

willemw commented on 2021-11-02 11:00 (UTC)

@Anty0: Agree with that. Even ArchLinuxARM don't add ARM architectures to arch in their custom PKGBUILD files. Patching should not be necessary. Calling makepkg directly or indirectly with the -A, --ignorearch option should do it.

Anty0 commented on 2021-11-02 10:56 (UTC)

Actually I don't really care anymore. Before each build on my build server I add aarch64 using sed to arch and I'm good to go. There are tons of packages which work on ARM, but does not list it in arch. Instead of bothering maintainer to add ARM I just hack it in.

At the time of my previous comment I was still pursuing arm to be added to arch for all packages I use on ARM :D

willemw commented on 2021-11-02 10:47 (UTC)

Listing ARM architectures in the arch array is useful when arch is going to be used in the PKGBUILD file, for example for installing pre-built binaries, which is not the case here.

Anty0 commented on 2021-11-02 10:40 (UTC)

@willemw @francoism90 True, since resulting package will only work on architecture of system it was build on, arch should be list of architectures, otherwise makepkg will use generic 'any' architecture and you won't know for which CPU the package was build for.

willemw commented on 2021-11-02 06:57 (UTC)

Preload is a binary: arch should be arch=('x86_64'). bash and glib2 are already installed.

francoism90 commented on 2020-04-18 08:52 (UTC)

@Anty0 You did only provide a build log, but I assume it does work as well. :)

It doesn't matter that much as isn't doesn't seem to be maintained in a long time now .. anyway, it still seems to work fine, even on a SSD/NVMe.

Anty0 commented on 2020-04-17 14:53 (UTC)

@francoism90 Yep, I'm sure. :D

Tested in RPi 3B. Compiles without any issue (see https://pastebin.com/Dy7pJXYv). Doesn't crash when started. (Actual effect of preloading from HDD is yet to be tested though.)

francoism90 commented on 2020-04-16 14:22 (UTC)

@Anty0 Are you sure it compiles and works fine on aarch64? I'll test later on rPi3.

Anty0 commented on 2020-04-14 10:24 (UTC)

Could it be possible to add aarch64 architecture? I can confirm the package builds succesfully and seems to be working properly. (Might also work on other arm architectures.)

Xavion commented on 2018-12-20 22:32 (UTC)

To find out whether it's still working on your system, quit all existing instances and run: sudo /usr/bin/preload -d

This article (from 5.5 years ago) gives advice on whether to use it: https://askubuntu.com/questions/110335/drawbacks-of-using-preload-why-isnt-it-included-by-default

With the onset of SSDs, I imagine 'preload' makes considerably less of a difference these days.

1 2 Next › Last »