-
Notifications
You must be signed in to change notification settings - Fork 98
Edit PKGBUILD: "yes" is the default answer when installing from AUR #296
Comments
Since there's a thumb up already, I've submitted a PR. |
Well, that’s a bad thing not to edit AUR PKGBUILD before building/installing (unless it’s an update and you make use of AURSHOWDIFF), so I would rather not encourage this behavior with this change. |
@ArchangeGabriel Are you really editing PKGBUILD each time you install anything? |
Like I said, unless it’s an update of something I have already installed (because I use AURSHOWDIFF mode), yes. And I even often make changes. Whatever, you’re supposed to do the same per ArchWiki. Eventually, I would agree to have No as the default answer for upgrades, if possible relying on AURSHOWDIFF to be 1, but not mandatorily. |
You guys are crazy. |
@rmarquis What do you mean? |
You're basically making yaourt even worst than it currently is. You should at least keep sane default. The config option for bypassing the PKGBUILDs checks is already available afaik. |
There's EDITFILES option: when set to 0, it suppresses any prompts to edit pkgbuild or install files. |
A lot of people use --noconfirm to avoid to be prompted to pass "n" |
Again, automation (including --noconfirm) leaves me no possibility to override program's default behavior - and I don't like not having a possibility. I want to make conscious decisions of editing or not editing certain files. |
Or simply keep that default and implement an option to reverse it... |
Hello, |
Does it make sense? I mean, how often would you edit a PKGBUILD?
I'd suggest to make "no" the default one.
The text was updated successfully, but these errors were encountered: