Oh, sorry. I didn't realize this discussion hadn't involved yaourt
yet. It spurned me to look up package helpers again, which of course
led to tons of false statements about flaws yaourt doesn't have
anymore or never had, and an ArchWiki page that says it's no longer
developed even though its last GitHub commit was 7 days ago.
At least as far as I know (maybe yaourt's fixed this by now, too),
running `yaourt -Si` on an AUR package results in the PKGBUILD being
sourced, allowing malicious code to be executed if it's in there. And
also as far as I know, that's the only flaw in yaourt, besides
extremely minor ones like how it handles split packages and tmpfs, and
ones that are just a feature it's missing that another AUR helper has.
And yeah, the tmpfs thing is super minor. I can't a single modern-day
use case for a computing device where both of the following are true:
-Arch Linux is a great distro choice
-There isn't plenty of RAM in the system
I've certainly never filled up my tmp directory by compiling anything,
which includes more than just things I installed through yaourt. I've
also set it to be bigger than 4GB, but that's because there are so
many so much more common programs to use than yaourt that might make
you think 4GB is too small.
On Sun, Mar 25, 2018 at 1:47 PM, Ralf Mardorf
<ralf.mardorf@xxxxxxxxxxxxx> wrote:
>
> On Sun, 25 Mar 2018 13:27:11 -0700, Jimi Bove wrote:
> >Is there really anything wrong with yaourt at all if you add this
> >to .bashrc?
> >
> >yaourt() {
> > if [[ $@ =~ "-Si" ]]; then
> > command echo "don't do that"
> > else
> > command yaourt "$@"
> > fi
> >}
> >
> >I'm sick of how much misinformation is still spread around with yaourt.
>
> Why not running "yaourt -Si"?
>
> Btw. now I noticed that the OP didn't use yaourt. I never heard of
> misinformation about yaourt. By default it builds in tmpfs, which could
> become an issue, if the available RAM is small and the binaries to build
> should be bloated, apart from this I'm not aware of any issue.
