Hi all,

I think I finally found a scenario where building some of my (and others') packages as modules would be beneficial.

The situation is:

- The syncthing package has a lot of golang dependencies.
- Some of them are too old in fedora, even in fedora rawhide, and some of them have not been touched in years.
- However, some other packages may depend on those older versions, or the packagers don't have time to check for compatibility.

The idea for a solution I came up with:

- Build syncthing as a module.
- Add "syncthing" branches to all incompatible dependencies (I guess I have to request commit/admin access to do that for packages I don't own yet?).
- Update those branches to use the exact same commit as the vendored sources in upstream syncthing.
- Use those modules as dependencies for the syncthing module.

Is that a valid, feasible use case of modularity?

Fabio