https://bugs.winehq.org/show_bug.cgi?id=39859
--- Comment #9 from Austin English austinenglish@gmail.com --- (In reply to Nikolay Sivov from comment #8)
(In reply to Austin English from comment #7)
Mmm, good point. Perhaps have the gecko/mono package names match the 'branch' name, e.g., wine-gecko-stable, wine-gecko-devel, wine-gecko-staging (not ideal, I realize, but as long as they're in the same repo that may be the best option). wine-gecko-staging may not be needed, at least until y'all start patching gecko in addition to wine ;)
Package name could itself contain version, like wine-gecko1.2.3 and then main package could depend/suggest it. They don't change that often to have various flavors of it. Branch name seems a bit too much.
Sure, that's also an option. The advantage of using branch name is that the dependency can be set once and doesn't have to be updated whenever mono/gecko is updated.
Either way works, it's a minor implementation detail IMO.