It's been suggested that our current method of having non-project people do packaging on an ad-hoc basis isn't working. Often the packages available in various Linux distributions are years old.
I was thinking about how to make Travis-CI do auto-packaging of releases. It's possible, but the OS'es available on Travis-CI aren't the newest so there wouldn't be a big impetus to do so. The current list on Travis-CI is: Ubuntu-14.04 (2014) Ubuntu-16.04 (2016) OSX-10.13.3 So... While Travis-CI is excellent to let us know when we break something or new warnings show up, it's untenable for packaging targeted towards many or newer OS'es. I have Jenkins (another CI engine) running at home. At the time I set it up the Xastir project was still on Sourceforge. My Xastir Jenkins builds haven't been re-targeted to Github yet, but using Jenkins I could set up auto-packaging for the OS it's running: OpenSuSE-42.3. Even that isn't the latest-latest OS version. Not sure what to do about other OS'es. Setting up VM's / Docker instances for several different current OS'es to do packaging might be a full-time job. Even after the initial bunch of work, adding newer OS'es and keeping things running might also be a full-time job. Thoughts? -- Curt, WE7U http://we7u.wetnet.net http://www.sarguydigital.com _______________________________________________ Xastir-dev mailing list [email protected] http://xastir.org/mailman/listinfo/xastir-dev
