On Fri, 11 Sep 2015 20:02:17 +0200, Ralf Mardorf wrote: >On Fri, 11 Sep 2015 12:32:59 -0400, Eli Schwartz wrote: >>As Ralf said, nothing *requires* yaourt, and indeed some things will >>blow up when you try installling via yaourt -- but standard makepkg >>handles fine, and indeed so do most AUR wrappers, in the AUR Helpers >>comparison chart [1] see the "Clean build" entry for yaourt. ;) [2] > >FWIW I'm using yaourt and usually it doesn't fail. There's just one >issue I encounter from time to time, but that also happens when using >makepkg. By default I set up makepkg to build in tmpfs and it >sometimes is too small. One time building a kernel failed, but usually >building default Arch kernels works with around 2 GiB tmpfs. If I build >a bloated web browser, such as e.g. firefox, the around 2 GiB tmpfs >don't provide the needed space. IMO building in tmpfs isn't really >faster, but I like it, because I don't need to tidy up tmpfs ;). Btw. >makepkg is set up to save the packages not in the tmpfs, but in a cache >to archive packages. My apologies. Just for fun I read the "Clean build" entry. That's correct! The setting to build in tmpfs is for yaourt, I just tend to run makepkg in tmpfs too. However, indeed, if it fails I build outside tmpfs using makepkg.
