Re: pkgquilt
nia <[email protected]> Sat, 13 Jun 2026 19:53:23 +0000
| Newsgroups | gmane.os.netbsd.devel.packages |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Jun 13, 2026 at 03:16:47PM -0400, Greg Troxel wrote: > Reading this thread, it occurs to me that the quilt scheme is an > approach to deal with two situations which are both problematic: > > A) a fork being maintained in pkgsrc, because upstream is nonfunctional > or won't take patches > > B) lots of patches that should have been upstreamed haven't been > > > and for solutions > > A) actually fork and package the fork > > B) follow our documented policy and send them upstream > Greg, to put this as polietly as possible, when you're reading pbulk reports like dh does, you have to mass patch many different packages that you _don't care about_. You're not forking them. Nobody is upstreaming patches to add GCC14 support and fix a recently-revealed segfault in a Xlib application that last got a new version in 2003. This is a problem that many old package managers have to deal with. Debian, for example. And more tooling is always nice. It's a whole different problem to maintaining a handful of packages in the geography category and needing to patch them