From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rymes To: development@lists.ipfire.org Subject: Re: [PATCH 0/9] pakfire: remove dup. code + seperate ui/logic Date: Wed, 09 Mar 2022 18:46:31 -0500 Message-ID: <07912474-3837-b452-5560-f58b8715ccff@rymes.net> In-Reply-To: <20220309225655.4472-1-robin.roevens@disroot.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4923204885318276448==" List-Id: --===============4923204885318276448== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 03/09/2022 5:56 PM, Robin Roevens wrote: [snip] > Now all upgrade info is gathered first and an upgrade summary is > presented to the user (more in the style of the output when a pak is > installed or removed) and confirmation is requested. > Only after the user confirming the upgrade the core and the paks are > upgraded in one go (except ofcourse when -y is used, then no > confirmation is asked). [snip] BRAVO!!! This behavior has always bothered me, too. Combined with the fact that "pakfire update" didn't tell you whether an update was available, it was quite frustrating, requiring a "pakfire status" to know if an update was available, first. I also frequently ended up coming back to a console/terminal and finding a partially completed upgrade process waiting for me to press "Y". Tom --===============4923204885318276448==--