* [ISSUE] Tmux update broke stuff // Ways how to handle breaking changes? @ 2019-05-10 5:51 voidlinux-github 2019-05-10 6:16 ` voidlinux-github 2019-05-10 6:16 ` [ISSUE] [CLOSED] " voidlinux-github 0 siblings, 2 replies; 3+ messages in thread From: voidlinux-github @ 2019-05-10 5:51 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 538 bytes --] New issue by Anachron on void-packages repository https://github.com/void-linux/void-packages/issues/11606 Description: With the commit https://github.com/void-linux/void-packages/commit/b7379f6eee1f0d9ba3713720c1b4b68ded4853e7 [a lot of stuff](https://github.com/tmux/tmux/issues/1689) broke on Tmux. Maybe we can think about how to handle breaking changes? Should we probably find a way to mark a package update as breaking and then let `xbps` tell the user which packages are "breaking" so he is aware of it and can read about it? ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Tmux update broke stuff // Ways how to handle breaking changes? 2019-05-10 5:51 [ISSUE] Tmux update broke stuff // Ways how to handle breaking changes? voidlinux-github @ 2019-05-10 6:16 ` voidlinux-github 2019-05-10 6:16 ` [ISSUE] [CLOSED] " voidlinux-github 1 sibling, 0 replies; 3+ messages in thread From: voidlinux-github @ 2019-05-10 6:16 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 467 bytes --] New comment by the-maldridge on void-packages repository https://github.com/void-linux/void-packages/issues/11606#issuecomment-491170078 Comment: We have a way to handle breaking changes already. We strongly encourage our user base to take their problems to upstream so that upstream will stop making breaking changes without following appropriate steps. If you're curious how certain things like SQL servers get upgraded, well the answer is meta-package magic. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ISSUE] [CLOSED] Tmux update broke stuff // Ways how to handle breaking changes? 2019-05-10 5:51 [ISSUE] Tmux update broke stuff // Ways how to handle breaking changes? voidlinux-github 2019-05-10 6:16 ` voidlinux-github @ 2019-05-10 6:16 ` voidlinux-github 1 sibling, 0 replies; 3+ messages in thread From: voidlinux-github @ 2019-05-10 6:16 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 541 bytes --] Closed issue by Anachron on void-packages repository https://github.com/void-linux/void-packages/issues/11606 Description: With the commit https://github.com/void-linux/void-packages/commit/b7379f6eee1f0d9ba3713720c1b4b68ded4853e7 [a lot of stuff](https://github.com/tmux/tmux/issues/1689) broke on Tmux. Maybe we can think about how to handle breaking changes? Should we probably find a way to mark a package update as breaking and then let `xbps` tell the user which packages are "breaking" so he is aware of it and can read about it? ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-05-10 6:16 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-05-10 5:51 [ISSUE] Tmux update broke stuff // Ways how to handle breaking changes? voidlinux-github 2019-05-10 6:16 ` voidlinux-github 2019-05-10 6:16 ` [ISSUE] [CLOSED] " voidlinux-github
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).