search

excalibur1234 / pacui

Bash script providing advanced Pacman and Yay/Pikaur/Aurman/Pakku/Trizen/Pacaur/Pamac-cli functionality in a simple UI
GNU General Public License v3.0
168 stars 13 forks source link

Merge update and devel update commands #46

Closed Morganamilo closed 6 years ago

Morganamilo commented 6 years ago

Based on recent events and discussions, I think it's best to not use --noconfirm. Although this isn't just about that, personally I have a huge dislike of --noconfirm usage.

Also I am very confused as to why you split the commands to update && devel update. This has no benefit, for yay at least, but I would assume most AUR helpers are similar.

Also I don't understand why you also pass --needed to every command. I know that pacaur uses --needed to filter out the 'needed' updates for --devel. But as far as I know this does nothing for other helpers. I've left it in though, has it doesn't really have any negatives.

excalibur1234 commented 6 years ago

thanks for your effort!

Also I am very confused as to why you split the commands to update && devel update. This has no benefit, for yay at least, but I would assume most AUR helpers are similar.

it is great to have you here! can you answer, whether the following sentence is correct: yay (and other good AUR helpers) update all AUR packages (using yay -Syu), if their PKGBUILD or .INSTALL file was modified since their last installation.

if the previous sentence is correct, "yay -Syu" updates all AUR packages with a modified PKGBUILD or INSTALL file. the modified PKGBUILD or INSTALL files can be optionally checked by the user. however, most PKGBUILD or INSTALL files of development packages are hardly ever modified. the "yay -Syu --devel --noconfirm" command updates these packages in a secure way (because "yay -Syu" was executed right before it) without needing user intervention.

Also I don't understand why you also pass --needed to every command.

i pass --needed to every command, because pacaur supported it and some AUR helpers MIGHT properly support it in the future as well. i know that it has currently no (noticeable) effect.

Morganamilo commented 6 years ago

By default yay checks updates purely on pkgver. If a pkgbuild is updated but the pkgver is not changed then yay will not bother updating it. There is the timeupdate option which instead compares build time to last modified time. Although yay has other layers of caching so timeupdate best works with redownload and rebuild.

Although even if your assumption was true. It is possible that a pkgbuild is changed between the first and second command. This probably holds true for any helper.

And for helpers that have batch interaction: yay, aurman, pacaur, ect. There is no real benefit to separation because after the initial prompts all the updates can then be done unsupervised.

excalibur1234 commented 6 years ago

thanks for the detailed explanation.

i agree that --noconfirm is a bad idea under these circumstances.