2025-10-27T01:52:31  *** teepee_ is now known as teepee
2025-10-27T15:21:55  *** teepee_ is now known as teepee
2025-10-27T20:31:12  <matrix-o-o> <Emma [it/its]> curiosity question: is there a way to dynamically alter packages based on other packages?
2025-10-27T20:31:19  <matrix-o-o> <Emma [it/its]> or some kind of dynamic configuration system
2025-10-27T20:32:38  <matrix-o-o> <Emma [it/its]> or would i have to look into building matrix configurations of packages on OBS?
2025-10-27T20:38:04  <matrix-o-o> <Emma [it/its]> tl;dr thinking of maybe porting part of my matrix-synapse patchset for use on opensuse.org (notably, the admin api extensions)
2025-10-27T20:51:04  <acidsys> I don't understand. You want to change configuration of matrix? or you want to apply patches to matrix-synapse?
2025-10-27T20:57:06  <matrix-o-o> <Emma [it/its]> i was curious if there was a way to handle having synapse packages for subsets of my patchset
2025-10-27T20:58:40  <matrix-o-o> <Emma [it/its]> so ie. someone can use just my admin api patches without eg. bulk sending events
2025-10-27T20:59:48  <acidsys> you can branch the package in some OBS project and apply patches to the package there, then if someone installs the package from that project repository they will get the software containing your patches
2025-10-27T21:00:29  <matrix-o-o> <Emma [it/its]> would i need to branch it $NUM_COMBINATINOS times?
2025-10-27T21:00:34  <matrix-o-o> <Emma [it/its]> * wouldnt
2025-10-27T21:01:13  <acidsys> the alternative is to build the package in the same project with different names
2025-10-27T21:01:44  <acidsys> if the software is modular then easiest is of course to offer different variations of a specific component
2025-10-27T21:02:34  <matrix-o-o> <Emma [it/its]> well, synapse isnt very modular, but rough guess would estimate that i'd have at least 16 different branches
2025-10-27T21:02:37  <acidsys> since the patches are applied during build time, the user cannot at install time decide which patches it should contain
2025-10-27T21:03:16  <acidsys> and what is the use case for that?
2025-10-27T21:03:25  <acidsys> I doubt any user will want to know about and use your 16 different projects
2025-10-27T21:03:56  <matrix-o-o> <Emma [it/its]> well, its a patchset encompassing various synapse changes - some more useful than others for most folks
2025-10-27T21:04:40  <acidsys> generally it is preferred to have upstream patches and to use downstream patches only for things which are not yet merged upstream or which are specific to our distribution
2025-10-27T21:04:53  <matrix-o-o> <Emma [it/its]> would be nice if i could use 2-3 of them on opensuse.org (primarily including tombstone/create events in the admin room list)
2025-10-27T21:05:00  <acidsys> for packages in the distribution there is no concept of offering the user to choose different downstream patches
2025-10-27T21:05:04  <acidsys> either they are included in the package or not
2025-10-27T21:05:14  <matrix-o-o> <Emma [it/its]> iirc saves me some 6000 HTTP requests when fetching the room list for opensuse.org
2025-10-27T21:05:43  <matrix-o-o> <Emma [it/its]> (and i feel like getting them upstreamed is unlikely at best)
2025-10-27T21:05:46  <acidsys> if you want some downstream patches for our deployment, we can apply them in one of our openSUSE:infrastructure projects. we don't need to have multiple variations there, because we - hopefully ;-) - know which patches we want to deploy
2025-10-27T21:06:06  <acidsys> well, did you submit it ? :-)
2025-10-27T21:06:09  <matrix-o-o> <Emma [it/its]> hm true i suppose :P
2025-10-27T21:06:34  <matrix-o-o> <Emma [it/its]> acidsys: i havent at this point in time due to CLA clauses
2025-10-27T21:06:44  <acidsys> would be good if you do
2025-10-27T21:07:46  <acidsys> you have to keep in mind that downstream patches are always a maintenance burden, especially for packages which we branch from the distribution (where we get updates for free from other contributors), we now always have the risk that a patch no longer applies and someone from our team needs to go and rebase/resolve conflicts
2025-10-27T21:08:37  <matrix-o-o> <Emma [it/its]> well, the patchset itself is what i run in production, and doesnt have any irreversible changes
2025-10-27T21:09:41  <matrix-o-o> <Emma [it/its]> and the specific patches i'd like to run on o.o are all in parts of the codebase that almost never get touched :P
2025-10-27T21:11:08  <matrix-o-o> <Emma [it/its]> but yeah it was mostly a curiosity question
2025-10-27T21:15:40  <cboltz> as an alternative to multiple packages with different patchsets, feature flags (aka additional config options) could also work - especially if you have several patches and possible combinations
2025-10-27T21:16:04  <cboltz> but in general, getting the patches upstream is the best solution