I like to inspect patchsets and comparing them. Though most of the patches as of today are musl related and don't interest me much. But: When looking into them I sometimes feel a kind of a horror: like random patches, which easily could set into acting code with just having _glibc_ (I think of errors with negative logic, etc ...) Wouldn't it be safer and more sane to just apply musl related patches if a global musl USE flag is active? Couldn't there be a muslpatches ebuild installing the needed patches like: /usr/share/muslpatches-123/firefox-60 Where firefox-60.ebuild than has a clause: musl? >muslpatches-122 Indicating when having only muslpatches-122 the firefox-60 would not emerge. ... just proposing :)
Pro arguments: - less patches for _glibc_ users - ebuilds like firefox-60.0.1 ready for _glibc_ users when not yet for _musl_ user
Please notice my wording "I feel horror" was meant ironical. (I am not a programer)
