Re: workflow for managing ports patches against /usr/ports in poudriere
void <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.hackers |
|---|---|
| Message-ID | <acfvL0CRWu4HKIy2@int21h> |
On Sat, Mar 28, 2026 at 10:27:15AM +0900, Tomoaki AOKI wrote: > >TBH, my workflow would be tooooo paranoid for ports or docs. I used something like that ages ago when php74 sunsetted and I had to keep it around while upgrading everything else, which worked for long enough till the client could schedule enough downtime for a 74=>81 upgrade. All my current use case presently though is aimed at applying patches from bugs.f.o without wrecking my ports tree. Gleb has suggested a method which appears to work for this particular case. I don't consider myself skilled enough to contribute patches though - this would be only for applying patches to the ports tree downloaded in the usual way via git that others had written (and then refreshing that tree). --