Re: removing mutt patches
- Reply: Derek Schrock : "Re: removing mutt patches"
- In reply to: Derek Schrock : "Re: removing mutt patches"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 05 May 2023 22:45:48 UTC
On 5/5/23 15:07, Derek Schrock wrote: > On Fri, May 05, 2023 at 06:04:35PM EDT, Amar Takhar wrote: >> It would be nice to have a message in pkg-message explaining the port is now >> vanilla outside of fixes and anyone looking for former patches should try >> NeoMutt. > > Yeah, I'm looking right now at adding a pkg-message to output a message > during install and upgrade. Also adding the same to UPDATING. I viewed pkg-descr as general non-instructive port information before install, UPDATING for special considerations/instructions before upgrading, and pkg-message as after install instructions. Not saying what to do but trying to continue to build up my understanding of ports tree structure in general with my questions. Wouldn't telling users after install/upgrade be telling them that there is now a problem after it has happened? Does `pkg updating` contain relevant UPDATING messages with each package, as part of the package repository listing, or does it need the ports tree UPDATING file present? Thinking about it, it would seem like a good idea to have pkg indicate there are messages to be read from UPDATING when listing a final confirmation of packages before doing upgrades though entries would all need max version listings or what has been read needs to be tracked; marking messages as read/dealt with as a todo checklist when upgrading could be nice. Just recently learned pkg-message supports conditional messages for upgrading based on version as a result of this thread+reading.