Bootstraping MacPorts for testing on Travis/Azure
Hi, I would like to suggest creating a super simple repository with bootstrapping tools required to allow other project to test their software on Travis, Azure etc. *using* MacPorts. I imagine that it should be possible for the .travis.yml file to simply: - copy a single file (or clone repository) from a specific location - execute that file, which would install and update macports (without installing any ports) as well as remove HB if present - run "sudo port install foo bar baz" to get dependencies - run the tests In particular I would like to enable such tests for two or three of our GSOC projects: Karan's upt, Arjun's web application, potentially also for Rajdeep's buildbot. An example of the use would be the following: (a) * Install upt (via macports) * loop through a list of rubygems packages, let upt generate ports for them * run lint for all of them and maybe even try to build some (b) * Install py37-django and the latest postgresql * set up the wab app and run unit tests We do (b) on Ubuntu. Generating packages for (a) could be done on Linux as well; for linting we would need to at least have MacPorts installed on Linux which is not any less trivial than installing it on the mac first. What I would like to avoid is having hundreds of lines of code in every single repository that wants to do the testing on macOS just for the sake of bootstrapping. Zero, would you be willing to help with that? Thank you very much, Mojca
Re: Slack-like chat (also for GSOC)
On Sat, Jun 15, 2019 at 2:03 PM Rainer Müller wrote: > > On 14.06.19 13:01, Nils Breunese wrote: > > > > Chris jones wrote: > > > >> ( The main problem I have, is not something specific to Riot or whatever > >> forum we use, but more we need to perhaps give some thought to the > >> channels. Currently there is really only one, which gets (some) chat but > >> also messages for each and every commit. I don't think the average user > >> needs to see each and every commit. I think we probably need to split > >> these, for instance into Dev and User channels, to match the mailing lists > >> perhaps. ) > > > > I’d go even more granular: create a dedicated channel for commits and > > everyone can decide whether to follow that or not. > I am not sure how useful such a dedicated channel would be if only > automated messages will be posted and no discussion takes place. > Sometimes the mplog messages are even used during conversations, like > "see this commit, now it is fixed". > > For those that really do not want to see these messages, I would > recommend to add mplog to their your ignore list. That works in IRC > clients and also in Riot. > > The bot is operated by me, but if others also think that the bot is > annoying, I do not insist on keeping it running or moving it to another > channel. I like the mplog on #macports. If someone doesn't like it, I would say they put it in their ignore list. IIRC, we did try to create a separate channel for #macports-gsoc but then after some time we ended up in #macports, because there were more users out their who could and would like to share ideas. Splitting of channels, IMHO, might not be a good idea. It works fine as a separate Mailing list, but maybe not on IRC. I do agree, that one might get lost in all the chatter that might happen all at one place, but yeah that is same in most of the platforms, at least the ones that I have used. I do like the idea of threads (in slack), maybe we need to look if they are in some libre/open-source alternative ? -- Jackson Isaac
Re: Slack-like chat (also for GSOC)
On 14.06.19 13:01, Nils Breunese wrote: > > Chris jones wrote: > >> ( The main problem I have, is not something specific to Riot or whatever >> forum we use, but more we need to perhaps give some thought to the channels. >> Currently there is really only one, which gets (some) chat but also messages >> for each and every commit. I don't think the average user needs to see each >> and every commit. I think we probably need to split these, for instance into >> Dev and User channels, to match the mailing lists perhaps. ) > > I’d go even more granular: create a dedicated channel for commits and > everyone can decide whether to follow that or not. I am not sure how useful such a dedicated channel would be if only automated messages will be posted and no discussion takes place. Sometimes the mplog messages are even used during conversations, like "see this commit, now it is fixed". For those that really do not want to see these messages, I would recommend to add mplog to their your ignore list. That works in IRC clients and also in Riot. The bot is operated by me, but if others also think that the bot is annoying, I do not insist on keeping it running or moving it to another channel. Rainer
Re: Slack-like chat (also for GSOC)
On 14.06.19 11:10, Chris Jones wrote: > ( The main problem I have, is not something specific to Riot or whatever > forum we use, but more we need to perhaps give some thought to the > channels. Currently there is really only one, which gets (some) chat but > also messages for each and every commit. I don't think the average user > needs to see each and every commit. I think we probably need to split > these, for instance into Dev and User channels, to match the mailing > lists perhaps. ) I would be afraid that by removing the development discussions, the channel would appear mostly dead. The traffic is already quite low. If at all, I would keep #macports as user channel and create another #macports-dev for deeper discussions of internals. However, development discussions happen rarely and are usually started by something that would rather be categorized as a user question. Which means we would have to force ourselves to move the discussion to another channel as soon as it gets to a development topic... Rainer
