On 02/04/14 20:45, Graham Cobb wrote: > I have now got a tinc package which handles systemd (systemctl can be > used to start and stop tincd using a service called > "tinc@netname.service", where netname is the network name to be used by > tinc). > > I have not done anything about connman. I have looked into it and it > looks hard: connman doesn't have support for tinc. The best way to make > it work looks to me like pretending tinc is a supported vpn such as > openconnect and providing a program that pretends to be openconnect but > actually controls tinc. > > Connman doesn't seem to be a problem for my (limited) usage so far. I > tend to use tinc only for limited periods of time, in static locations > (such as hotel rooms) so there are no network changes going on for > connman to decide it needs to take action. Of course, I may find out > that I am wrong and I do need to do something about connman but, until > that time, I am not going to try to solve that problem. > > I am thinking of submitting the package in its current form to Chum. > Anything I ought to know before doing that?
Why not submit it and then we'll do a public review? That should help bring out questions (like connman integration which I don't think is mandatory, but which I'm not surprised you considered and sets a good precedent). So initial step is to build in your home dir against the chum targets you want to include ("latest" being sufficient). I think you do this. Consider what is present in the yaml/spec file. We should be looking for urls, license, summary, description, version. The goal here is clarity to the end user and to assist future maintainers if you go AWOL. We should ensure the packaging is done 'correctly' - and if we miss any guidelines (eg use of systemd macros) then we should put them in the wiki. In general lets aim to use rationales developed by other distros like fedora and suse (I tend to follow suse since I often steal pre-prepared packages from their OBS). I've got to go so lets just make a start and see how it goes :) nb .. as we review these issues we should be thinking of expressing the validation steps in ways to aid scripting and automation. > Also, while doing this I have discovered that there are a number of > other standard utilities I really want on my phone (like unison). Is > Chum a suitable place to submit those? Yes. David _______________________________________________ SailfishOS.org Devel mailing list