#nemomobile log for Thursday, 2020-03-12

*** verin0x9 is now known as verin0x03:00
T42<abranson> @starbuck2018 It's definitely an exciting time. The pinephone is really stimulating mobile linux development, as we're finally breaking out of the qualcomm cage where only android kernels and drivers are available. There's still a big gap between what the pine's mainstream kernel can do and what android provides, and I think it's ver07:41
T42y risky to put estimates on how far away we are from having a truly stable and fully featured mainline mobile device with a decent battery life. If Meego hadn't gone away we'd probably be there by now :(07:41
T42<abranson> Also agree with you that cross-pollination between distros can only help. The point I was trying to make is that nemo doesn't have a lot of people working on it, and it's enough work for the medium term to get the UI working well on top of the Sailfish base. Trying to reach too far by replacing that right now is counter-productive. T07:44
T42here's some really good stuff and years of development gone into that - I seriously doubt that can be replaced in a couple of years.07:44
T42<starbuck2018> @abranson [Also agree with you that cross-pollination bet …], So are you saying by your own personal estimate, Purism isnt going to be able to deliver an equally quality phone with their approach this year?08:38
T42<abranson> @starbuck2018 [So are you saying by your own personal estimat …], At FOSDEM a couple of year ago when they were starting out and setting themselves out to deliver in a year, a group of mobile linux veterans organized a BOF meeting with them to try to pass on some experience of the problem, so they might get a realistic idea of th08:45
T42e scale and pitfalls of the task. It went ok, but they did come across with the same old 'we know better' attitude that every other new attempt has had. Their initial delivery was delayed, and while the work they've done is top quality they're still a long way from delivering a productized OS, with the telltale sign of poor battery life (I don't ha08:45
T42ve one so I can only go off what I've read elsewhere). I think they've been hampered by the EFF dogma a bit and it looks like they've made some poor hardware choices by going for 'freedom' over functionality. It looks like Pine haven't made that mistake.08:45
T42<abranson> it's all good though. Even if that device fails, and even if they end up abandoning the effort entirely (which I hope they don't - they have other revenue streams and they don't seem as fickle as canonical were), Phosh is a solid contribution to mobile linux, even if it does reignite the whole gtk vs qt rivalry a bit.08:47
T42<abranson> Btw, I do know that they've been using some sailfish bits. They were working on using telepathy-ring for calls at one point - not sure if it's still in there.08:48
T42<eekkelund> @neochapay [@eekkelund ping], heoo :)10:35
T42<neochapay> @neochapay [@eekkelund can you create mr into devel branch …], this10:35
T42<eekkelund> @neochapay [@eekkelund can you create mr into devel branch …], in which package10:36
T42<neochapay> @eekkelund [in which package], glacier-home devel branch10:36
T42<eekkelund> Yeah sure, asteroidos lipstick or mer-core PR one? mer-core one gives the black screen10:38
T42<neochapay> @eekkelund [Yeah sure, asteroidos lipstick or mer-core PR …], at now we try use asteroid lipstick - as corrected work at 5.1210:38
T42<neochapay> next steep - update mer lipstck10:39
T42<eekkelund> great!10:39
T42<neochapay> @eekkelund [great!], waiting mr ^_^10:39
T42<neochapay> https://git.sailfishos.org/mer-core/glibc/merge_requests/38/diffs fixup build new glibc on aarch6411:19
T42<AJSlye> So do I have this right, I should build lipstick from asteroid or the one from sailfish git?11:36
T42<neochapay> @AJSlye [So do I have this right, I should build lipsti …], I think on next week i update mer lipstick11:37
T42<AJSlye> on arch that is where we use Qt 5.1411:38
T42<AJSlye> This is why I like efl, they never break the legacy api's or backward compatability.11:38
T42<AJSlye> OK, so I'll build the deps and wait until next week to build lipstick then.11:41
T42<AJSlye> I'm getting an error building libreasorce now, it built last week.11:44
T42<neochapay> show error log11:45
T42<AJSlye> make[2]: *** No rule to make target '../src/libresource.la', needed by 'libresource-glib.la'.  Stop.11:45
T42<AJSlye> make[2]: *** Waiting for unfinished jobs....11:45
T42<AJSlye>   CC    resource-glib-glue.o11:45
T42<AJSlye> make[1]: *** [Makefile:484: all-recursive] Error 111:45
T42<AJSlye> make: *** [Makefile:387: all] Error 211:45
T42<AJSlye> (Document) https://irc.thaodan.de/.imgstore/kqacGSNmXS.null11:45
T42<AJSlye> accidentally pasted the clipboard.11:46
T42<neochapay> @AJSlye [<reply to media>], in build log you use 0.18 version11:47
T42<neochapay> Are you use correct commit ?11:47
T42<AJSlye> i'm just using master I think.11:48
T42<AJSlye> there is a sed command dealing with .la in asteroids .cc file.11:48
T42<neochapay> @AJSlye [i'm just using master I think.], --disable-static ?11:48
T42<AJSlye> maybe that's the issue11:49
T42<AJSlye> yes, I have —disable static in the pkgbuild.11:49
T42<AJSlye> (Document) https://irc.thaodan.de/.imgstore/KtPfnmz9uy.txt11:49
T42<AJSlye> asteroid os is doing this: do_compile_prepend() {11:50
T42<AJSlye>     sed -i "s@\$(top_builddir)/src/libresource.la@libresource.la@g" src/Makefile11:50
T42<AJSlye> not sure how to do that in the pkgbuild though, syntax is off.11:59
T42<AJSlye> OK going to get some espresso this is going to take a bit.12:19
T42<AJSlye> The thing is, this built before so I have to be missing something.12:21
T42<AJSlye> I had to switch build system, ssd failure on old build workstation.12:22
T42<AJSlye> libiodata-git doesn't want to build again either. I have to be missing something in my chroot used for building.12:48
T42<AJSlye> (Document) https://irc.thaodan.de/.imgstore/hdfGN5i5YX.null12:48
T42<neochapay> build in one tread12:49
T42<AJSlye> you mean -j112:49
T42<neochapay> yeap12:49
T42<AJSlye> make or qmake?12:50
T42<AJSlye> yeap that was it. Grrrr, LOL12:51
T42<AJSlye> well for iodata anyway.12:52
T42<AJSlye> well fixed libresource as well.12:54
T42<AJSlye> I wonder why on my core I3 I need -j1 but didn't on my core I5. 🤔12:55
T42<AJSlye> anyway that fixed em both.12:55
T42<AJSlye> that wouldn't have anything to do with vt in the uefi would it?12:56
T42<starbuck2018> @abranson [At FOSDEM a couple of year ago when they were …], The point is: Either phosh via pmos on pinephone works and if it does, you neednt a specialized distro anymore for the last 5-10% or it doesnt work.13:44
T42<abranson> i guess, though that's usually the hardest 5-10%, but I think whatever happens it'll make a great ui for gtk based distros. Another question is how ready gnome is for a phone UI. Qt was owned by Nokia for several years who put a lot of effort into it, which is why it's been the default mobile platform ever since.14:22
T42<abranson> I don't know how specialized pureOS is though. how much specific middleware there is.14:22
T42<Sam %lastname%> @abranson [I don't know how specialized pureOS is though. …], It's debian14:27
T42<abranson> so none?14:28
T42<Sam %lastname%> They developed some solutions on top, for PureOS itself are mostly to handle the FSF-compliance, on Librem5 they developed Phosh14:29
T42<abranson> I just wonder if they've had to fork and patch stuff underneath for mobile. I'd think they'd have to.14:31
T42<minlexx> I heard their gtk is patched14:55
PureTryOut[m]It is yes, to make stuff fit on the small screen14:58
PureTryOut[m]It's why some Gtk apps don't fit on postmarketOS while they do on PureOS14:59
PureTryOut[m]They don't have that much forked stuff though14:59

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!