Ssh is All that’s needed as far as I know. Sent from my iPhone
> On 24 Jul 2018, at 16:14, Carsten Haitzler <ras...@rasterman.com> wrote: > > On Tue, 24 Jul 2018 11:41:29 +0200 Stefan Schmidt <ste...@datenfreihafen.org> > said: > >> >> >>> On 24.07.2018 11:19, Carsten Haitzler wrote: >>> On Tue, 24 Jul 2018 09:28:05 +0200 Stefan Schmidt >>> <ste...@datenfreihafen.org> said: >>> >>>> Hello. >>>> >>>>> On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote: >>>>> On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt >>>>> <ste...@datenfreihafen.org> said: >>>>> >>>>>> Hello. >>>>>> >>>>>>> On 23.07.2018 06:59, jaquil...@eagleeyet.net wrote: >>>>>>> Hi Guys, >>>>>>> >>>>>>> I am willing to work on getting a CI setup on a mac machine going. >>>>>>> >>>>>>> I am willing to sponsor a server. I happened to find the following >>>>>>> >>>>>>> https://www.hostmyapple.com/macdedicated.html >>>>>>> >>>>>>> What do you guys think? >>>>>> >>>>>> You know that we already have CI testing on OSX via TravisCI? >>>>>> >>>>>> What would this do better than the current CI setup we have? >>>>>> >>>>>> https://travis-ci.org/Enlightenment/efl (look at the build job with an >>>>>> apple as logo) >>>>> >>>>> run apps and debug them interactively? you'd need vnc or some remote >>>>> display/access setup ...but that. :) it'd require people to not fight over >>>>> the same display... i.e. one person at a time... :) >>>> >>>> If we have one osx system for CI builds and another one for debugging >>>> problems on OSX I easily see how they could be very different in terms >>>> of OSX versions, libraries, homebrew installs, etc. >>> >>> that's massively better than only a CI system and no way to interactively >>> debug things like copy & paste (ask netstar - he has a mac box to do that >>> now). this isn't perfection, but it never will be. :) it's better than >>> nothing as right now the CI systems do not allow dbeugging like i >>> described. just builds. right? >> >> Just builds. I don't expect a CI system to be a debugging system. To me >> these are two very different things to do. The TravisCI setup for OSX >> already proved itself very useful by finding build breaks on code >> committed into master. >> >> You fancy a full blown OSX system with remote VNC access for manually >> compiling and debugging. That is fair and could be nice to have. Just >> nothing on my list to work on. If you and Jonathan want to work on >> setting this all up, just go ahead. > > Indeed when eagleye mailed this, this was my first thought as it would need > nothing more than: > > 1. some kind of vnc setup > 2. some kind of ssh access with accounts > 3. some kind of sudo-like access > > then at least when things really need some work, people can ssh in, use vnc > and develop/test without having to buy a mac themselves. it sure as hell isn't > as nice as a local machine, but ... it is a big step up from just CI/test > suites. :) > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > Carsten Haitzler - ras...@rasterman.com > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
