On 30/03/14 08:05, "Thomas B. Rücker" wrote: > On 03/29/2014 11:44 PM, Graham Cobb wrote: >> I have taken the tinc rpm source from CentOS (tinc-1.0.23-1.el5.src.rpm) >> and rebuilt it on my jolla phone (using rpmbuild --rebuild). It seems >> to work fine. > > That's nice. I guess it's CLI only and you'll have to figure out to > fight connman over resetting routes? (Someone mentioned the old openVPN > windows hack of 0.0.0.0/1 and 128.0.0.1 yesterday at the Devaamo hack day) > > I should try it against my TINC server.
First off, I use tinc on the mer infra so it's packaged here for opensuse: https://build.merproject.org/package/files?package=tinc&project=mer-infra%3Atesting I'd be happy to see that packaging tweaked to work on Mer itself (that way any maintenance is shared) - and I'm happy to help too. >> Can I contribute it to Mer so it eventually appears in the mer-tools >> repository? Can anyone point me to how I would start that? > > I'm not really sure what the rules for inclusion into mer-tools are, > although VPN tools do make sense. I think there was someone else trying > to get a VPN client in. Good question. mer-tools is mainly intended for use in an SDK. Things which are useful when developing apps. > An option that would make TINC available quicker and stay up to date > with Sailfish updates and dependencies, would be to submit it for > inclusion into Chum, the community repository for open source software > (Think maemo extras). So I think this is the right place to package it for Jolla devices. > For this, put your package on mer OBS and then submit it from your home > repository to: sailfishos:chum:1.0.4.20:testing > As of right now, that's update 4, look up the right one in case there > are newer updates here: > https://build.merproject.org/project/subprojects?project=sailfishos%3Achum There's also a 'latest' repo now which should make keeping on top of Jolla's updates easier. > If you need help with OBS, I'd suggest to ask on IRC: #sailfishos on > Freenode > >> Is it OK to >> use a package from another distribution or would I have to go back to >> the upstream tar and re-package it myself? > > Sure it's OK to leverage existing packaging, but please make sure that > the package doesn't have any $other-distributionisms left in it, > especially as those could negatively affect the device. Those things > will actually be checked against once you submit your request on OBS and > will be also relevant for later moving it into mer-tools. eg Mer doesn't support %insserv_cleanup > > Further questions are probably best answered by lbt (David) as he's > techically responsible for both. > > Cheers > > Thomas > _______________________________________________ > SailfishOS.org Devel mailing list > _______________________________________________ SailfishOS.org Devel mailing list
