Yay: Add --noedit flag

Created on 16 Oct 2017  路  11Comments  路  Source: Jguer/yay

Currently using pacaur, and I'd like to request a --noedit flag added to yay. I've got some of my installation process scripted and have a few AUR packages I'd like to continue to have my scripted installations "unattended" if switching to yay.

Most helpful comment

Reviving this. Here's my use case: when I run yay -Syu I still want to be asked what AUR packages to skip updating (Enter packages you don't want to upgrade) but I don't want to be prompted to edit PKGBUILDs and such (==> Edit PKGBUILD? [y/N]). Using --noconfirm skips both steps, so in this case --noedit would still ask the first question but would not prompt to edit.

Let me know if you need any further clarification.

P.S.: Thanks for Yay! Just started using it and it's a great alternative to apacman :)

All 11 comments

If this is a wanted feature, I would like to try and implement it.

I'm trying to understand this issue more clearly, I have also had AUR install scripts depend on yay and using 麓yay --noconfirm麓 I bypass the edit 麓PKGBUILD麓 stage and the package confirm install. So right now if 麓--noedit麓 was implemented your script would still be stuck at the "Confirm package installation".

I have no problem with adding a --noedit flag, I'm just confused at your use case.

In pacaur you have the differentiation between '--noconfirm' which skips everything. So conflicting packages get replaced and so on. The '--noedit' option only skips the user input for editing the PKGBUILDs.
But you still need to confirm the installation.

As far as I saw in the code 'yay --conconfirm' causes the following things:

  • Removal of make dependencies
  • Not removing already existing build files
  • Not editing PKGBUILD
  • Confirm the installation of dependencies
  • Confirm installation even if some dependencies were not found

I'm not sure how yay would handle conflicting packages with the '--noconfirm' option.

In case of a package conflict yay would drop out with no installed packages since it is pacman's default action.
If --noedit is useful for some scripting action and familiar to people who have used other AUR Helpers, I find no reason not to implement it. I don't think it classifies as feature creep.

If want to try and implement it, I say go for it.

I don't see the use case for scripted installation with '--noedit' because pacaur also asks for confirmation. Maybe @brandon099 can explain the use for this.

I must have misunderstood what --noconfirm did. I hadn't tried one without the other as the man pages for pacaur don't seem to clearly indicate noconfirm also applies to editing PKGBUILDs. I was under the impression you had to pass both noedit and noconfirm to skip all prompts and editing PKGBUILD's.

From a scripted perspective --noconfirm seems to do the trick with yay bypassing _all_ commands that require confirmation from the user.

Nice for familiarity, but from a functional perspective, it's working just great for me knowing that's how noconfirm works. 馃槃

Closing this for now until someone else brings it up again.

Reviving this. Here's my use case: when I run yay -Syu I still want to be asked what AUR packages to skip updating (Enter packages you don't want to upgrade) but I don't want to be prompted to edit PKGBUILDs and such (==> Edit PKGBUILD? [y/N]). Using --noconfirm skips both steps, so in this case --noedit would still ask the first question but would not prompt to edit.

Let me know if you need any further clarification.

P.S.: Thanks for Yay! Just started using it and it's a great alternative to apacman :)

Closing this for now until someone else brings it up again.

I'm bringing it up!

I think #226 is a replacement for this which I plan to implement at some point.

I think #226 is a replacement for this which I plan to implement at some point.

OK, thank you.

Was this page helpful?
0 / 5 - 0 ratings