Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Requesting official statement from developers #382
Yaourt has been the most popular AUR helper for quite some time in the past and has been referred to by many upstream developers for installations of packages from the AUR.
There have been many helpers that have effectively superseded yaourt since those times – in terms of features, security concerns, code quality and most importantly user support and feedback.
To many of these projects yaourt has been an inspiration and a useful metric to compare against. Now legacy of yaourt has been continued by yay.
There are still people using yaourt to this day and I think it is only fair to give an update on where the project is going officially.
Some of notable issues include:
Yaourt does not see much development in years with many issues unresolved and unanswered. Other popular helpers have provided an update in such and other cases and archived github repo so people don't mistakenly seek support, see links below grey items in the table for examples.
Please provide an update and thanks for your long-lasting contribution to the community! You will be remembered
Thank you for you message. I think you perfectly summarize the situation of yaourt.
Rewriting yaourt is something I've thought about doing for a couple years, but have (obviously) never gotten around to.
FWIW: I've got the usual numerous objections against current code implementations of yaourt, but the underlying featureset and objectives has always been something I liked, a lot.
Nothing has ever replaced pacdiffviewer for me. And I'm actually very fond of package-query as a command-line tool and will not infrequently use it on its own just to pull formatted RPC information from the AUR. :D
Dec 5, 2018
If the software is indeed unmaintained and still contains the security issues related to sourcing PKGBUILDs before showing them then perhaps it should be removed as to not give the illusion that there is support or that all things are fine.
Myself I switched from yaourt to yay as soon as I became aware of this months ago.
@AladW let me explain why i was laughing from your statement (because there were people who were blaming me in taking fun from you without a reason):
considering what there are only two ways to proof an application to be correct: via unit test coverage or via mathematical proofing of all algorithms
among aur helpers only pikaur have a measured test coverage and only one aur helper is written in haskell (so math analysis could be used however i'm not aware if it's the case there)
so your attempts to paint pikaur in black colors just because you personally dislike me is plain funny
Mathematical proofs, yes. Test suites, no.
At least aurman, aura, and yay also have unittests. But anyone who claims their test suite has perfect coverage can be mathematically proven to be a liar.
@svitoz but that's a reply on her message here, originally when i saw it i left only a laughing emoji. but as you can see i wasn't even talking to her first, she herself was looking for the conflict.
@eli-schwartz i wasn't saying anything about "perfect coverage" (idk from where it coming on your side), i was talking about "measured coverage"
just having the tests is nice, but without measured coverage there is no reliable way to determine which parts of the application are actually covered by those tests, which not, which skipped
if you are trying to be a maximalist -- you could say what mathematical proof also don't mean anything because it could be a mistake or incompleteness in a confirmation model
but point is what saying what some app is "always break" is not so smart for someone who don't have any objectively measurable qualities/statistics (or while such qualities or statistics are saying the opposite) and basing the opinion only on the personal bias to its developer
tl;dr "show me aur helper / pacman wrapper which breaks less often than pikaur and proof what it's true"
pushed a commit
Feb 9, 2019
referenced this issue
Mar 4, 2019
After some conversations, we have decided to archive the yaourt github project.
Maybe pacdiffviewer ( https://github.com/archlinuxfr/yaourt/blob/master/src/pacdiffviewer.sh.in ) is a part someone wants to improve (I haven't looked for alternatives, maybe something already exists :)).
I'll update the README too soon.
Thank you everyone for your contributions !
pacdiffviewer is a lot more complex, and thus more useful, than the existing pacdiff program. In general, the idea behind this has not really been beaten... I still routinely use it.
The only other comparable tool I've seen is https://github.com/foutrelis/pacmarge which uses an online database of all config files in the archlinux.org official repos and does not handle custom packages, thirdparty repos, or derivative distros.