@kop316 @linmob @PINE64 @purism Manjaro does that often without making this explicit, and we then get plenty of invalid bug reports upstream :( There's usually a good reason why stuff that isn't merged yet isn't merged yet. It's fine to have a distro that includes experimental stuff around for those bravest, but I'd like to see Manjaro clearly state which things they pull in are still unfinished so users are well aware of what to expect.
@dos @kop316 @linmob @PINE64 @purism They do the same with some stuff developed by postmarketOS devs and then our devs get invalid bug reports as well. It's fine doing it in dev builds where they ship all kinds of nightly stuff, but it really shouldn't happen in "stable" builds without explicitly warning the user about it.
@bart @dos @kop316 @PINE64 @purism With regard to this MMS feature, it's only in Manjaro Phosh dev (I thought about making this more clear in my headline, but didn't). Maybe, to avoid invalid bugreports, they could put in a First Run note (like a simple webview) that links the repos they are using so that bugs get reported there (and then get cherrypicked for upstream if that's where they belong)?
Ummm....the branch being used is actually called "wip/mms_settings". It isn't in my main branch as I haven't finished working on it.
They are welcome to use what they want ,like I said, this is free software! I just think folks will be disappointed when they realized that MMS support isn't complete.
@be @dos @kop316 @PINE64 @purism Honestly, I don't see AUR PKGBUILDs as "packaging". They are a recipy to install something to try it out with no warranties and hopefully with a way to cleanly uninstall it, if it doesn't work out. This is especially the case for "-git" packages. Users that expect those to work obviously don't know what they're doing – "-git" packages are like hitting "I'm feeling lucky" on Google: Sometimes it works, often it doesn't.