Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

Ok cool! Thanks Rajdeep On Wed, May 15, 2019 at 1:29 PM Pierre Tardy wrote: > Hi Rajdeep, > > Buildbot calculates the version number based on tags. You you have to > fetch all the tags so that the version is correctly calculated. > > git fetch --tags --all > > then you can re-do the make

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

Hi Rajdeep, Buildbot calculates the version number based on tags. You you have to fetch all the tags so that the version is correctly calculated. git fetch --tags --all then you can re-do the make virtualenv Regards Pierre Le mar. 14 mai 2019 à 11:39, Rajdeep Bharati a écrit : > > Thanks for

Re: Slack-like chat (also for GSOC)

admins. It also allows for one-on-one conversations and rooms where only invited users can join. An example would be: https://gitter.im/coala/coala @Mojca would you be willing to give this https://gitter.im/macports-gsoc a try? I tried creating one suitable for us. Let me know if you are able

Re: GSoC 2019 [Collect build statistics]

Dear Arjun, I'm CC-ing the list as that's potentially interesting to others as well. On Tue, 14 May 2019 at 19:45, Arjun Salyan wrote: > Summary of today's discussion: > > 1. *Repository: *The existing repository for the web app would be moved > from the staging area to the official MacPorts

Re: Slack-like chat (also for GSOC)

on IRC, so maybe this is not > that important here. I don't have any experience with Matrix, but I maybe I should try it once. I'm not familiar with Rocket Chat either, but if you missed a feature, I trust your opinion. I do believe that longer conversations are important. Think of GSOC, where the sa

Re: Slack-like chat (also for GSOC)

On Tue, 14 May 2019 at 19:15, Nils Breunese wrote: > > Slack provides shareable invite links, but they expire. This blog post lists > some other options: > > https://intoli.com/blog/make-a-public-slack-community/ > > Looks like it requires some work, but it’s possible to setup. > Note that I

Re: Slack-like chat (also for GSOC)

Rainer Müller wrote: > I think Slack workspaces are also always invite only, but please correct > me if I am wrong (maybe only for paid plans?). Slack provides shareable invite links, but they expire. This blog post lists some other options:

Re: Slack-like chat (also for GSOC)

but I'm curious about your stand with >>> respect to setting up a service like Zulip Chat / Rocket Chat / ... >>> for aiding the GSOC communication when higher frequency of potentially >>> simple questions would be needed. I know IRC could fulfill such a >>> task,

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

Thanks for the feedback! I had a doubt in buildbot: When I install buildbot from source (github), then why is it showing version 2.1.1dev... installed? Shouldn't it show the latest version (2.3.0)? It is up to date with the master branch. Thank you. Rajdeep On Fri, May 10, 2019 at 3:17 AM Mojca

Re: Slack-like chat (also for GSOC)

On Sun, May 12, 2019 at 6:15 PM Andrew Janke wrote: > > On 5/12/19 3:49 PM, Mojca Miklavec wrote: > > I looked at Zulip chat which was used for GSOC meeting. That one would > > also only retain the last few thousand messages unless we payed an > > amount that we could

Re: Slack-like chat (also for GSOC)

On 5/12/19 3:49 PM, Mojca Miklavec wrote: > I looked at Zulip chat which was used for GSOC meeting. That one would > also only retain the last few thousand messages unless we payed an > amount that we could not afford as a project. > Mattermost probably doesn't offer any free

Re: Slack-like chat (also for GSOC)

setting up a service like Zulip Chat / Rocket Chat / ... > > for aiding the GSOC communication when higher frequency of potentially > > simple questions would be needed. I know IRC could fulfill such a > > task, but it doesn't work too well for me. (I'm offline when at work,

Re: Slack-like chat (also for GSOC)

; for aiding the GSOC communication when higher frequency of potentially > simple questions would be needed. I know IRC could fulfill such a > task, but it doesn't work too well for me. (I'm offline when at work, > cannot really use phone efficiently for communication etc..) I don't have particu

Re: Slack-like chat (also for GSOC)

on so far, but I'm curious about your stand with >>> respect to setting up a service like Zulip Chat / Rocket Chat / ... >>> for aiding the GSOC communication when higher frequency of potentially >>> simple questions would be needed. I know IRC could fulfill such a >>>

Re: Slack-like chat (also for GSOC)

C and >> PR/ticket discussion so far, but I'm curious about your stand with >> respect to setting up a service like Zulip Chat / Rocket Chat / ... >> for aiding the GSOC communication when higher frequency of potentially >> simple questions would be needed. I know IRC co

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

On Wed, 8 May 2019 at 21:00, Rajdeep Bharati wrote: > > Hi, > > I created some issues and found some which would be relevant for the project > (as discussed in the IRC meeting): > > https://github.com/buildbot/buildbot/issues/4760 > https://github.com/buildbot/buildbot/issues/4761 >

Re: Slack-like chat (also for GSOC)

Hi, > > I know that our official channels only include mailing lists, IRC and > PR/ticket discussion so far, but I'm curious about your stand with > respect to setting up a service like Zulip Chat / Rocket Chat / ... > for aiding the GSOC communication when higher frequency of potentially

Slack-like chat (also for GSOC)

Hi, I know that our official channels only include mailing lists, IRC and PR/ticket discussion so far, but I'm curious about your stand with respect to setting up a service like Zulip Chat / Rocket Chat / ... for aiding the GSOC communication when higher frequency of potentially simple questions

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

> Could you add them to the project ? Done.

Re: Please welcome the four GSOC projects this year

Greeting, welcome, and congratulations. Speaking only for myself, e-mail is the best way to communicate. If the topic is of general interest or concern, a public forum might be appropriate (please CC me however). This GSOC should be a great experience for all. -Marcus > On May 7, 2019, at

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

Hi, I created some issues and found some which would be relevant for the project (as discussed in the IRC meeting): https://github.com/buildbot/buildbot/issues/4760 https://github.com/buildbot/buildbot/issues/4761 https://github.com/buildbot/buildbot/issues/4709

Re: Please welcome the four GSOC projects this year

Hello everyone, Thank you for selecting me for GSOC 2019, I'm very excited to contribute. Congratulations to the others too. To my mentors Marcus and Clemens: For private communications, is e-mail the most effective way or do you prefer I message through something else? I will track my

Re: Please welcome the four GSOC projects this year

:57 AM Mojca Miklavec wrote: > Dear MacPorters, > > I'm happy to announce that MacPorts will be participating at Google's > GSOC with four awesome projects this year. > > (Those who followed the heavy traffic on the development mailing list > are probably already aware of

Re: Please welcome the four GSOC projects this year

Thank You Mojca! Congrats Satryaji, Karan and Rajdeep. The community has shown amazing support for all of us during the application period itself. I can't thank enough for the help I received in tackling all the problems and doubts. Looking forward to a really productive summer ahead while

Re: GSoC Proposal

the community better and to contributing as much as possible now and also after the completion of GSoC. Thanks, Karan Sheth -- <https://www.somaiya.edu>        <http://www.somaiya-ayurvihar.org>  <http://nareshwadi.org>  <http://somaiya.com>  <http://www.helpachild.in>  <http://nareshwadi.org>

Re: Speed up trace mode (GSoC Project)

> > > > > From what I understand from the stackoverflow post you're right that > cmxpchg16b will not give a consistent view of the 16 bytes of memory > across multiple NUMA nodes. However, maybe two 4 byte values right next > to each other would be sufficient for your use case and could then be >

Re: GSoC Proposal

Dear Karan, On Fri, 3 May 2019 at 23:27, Karan Sheth wrote: > > If PEAR ports are useful to the community then I would like to take > this as stretch goals / after GSoC goal. For anyone putting the GSOC mails to "ignore mode" due to heavy traffic ... maybe leave the comme

Re: GSoC Proposal

to upt which won't take much time. If PEAR ports are useful to the community then I would like to take this as stretch goals / after GSoC goal. Thanks, Karan Sheth [1] https://lists.macports.org/pipermail/macports-dev/2019-May/040664.html -- <https://www.somaiya.edu>        <http://ww

Re: Speed up trace mode (GSoC Project)

Hi Clemens, For making my implementation of shared memory data structure more space efficient, I was trying to implement a stack which stores offsets to unused locations in the shared memory file. But as stack is being shared it also needs to be edited in a lock free way. While editing stack I

Re: Speed up trace mode (GSoC Project)

Hi Clemens, > What's your current progress? Do you have some code already? > I made a complete offset based ctrie implementation in which any process can insert and search on basis of a shared memory. Kindly provide me with your views on it :) All main code is in [1]. The header file contains

Re: Speed up trace mode (GSoC Project)

Hi, Sorry for the late response. What's your current progress? Do you have some code already? > Currently I am done with a basic Ctrie implementation as suggested in the arXiv paper that is capable of inserting and searching paths. The implementation is still with pointers which I will convert

Re: Any objections to using GitHub issue tracker for GSOC projects?

t; offering, so it made sense to stick with Trac. >> >> The situation is slightly different with smaller standalone projects >> where issues might in fact be a better fit and easier to use. >> >> For smaller standalone projects like those suggested for GSOC >&g

Any objections to using GitHub issue tracker for GSOC projects?

sense to stick with Trac. The situation is slightly different with smaller standalone projects where issues might in fact be a better fit and easier to use. For smaller standalone projects like those suggested for GSOC (excluding base-related ones) I would like to experiment with the built-in issue

Re: Speed up trace mode (GSoC Project)

Hi, On Sun, Apr 21, 2019 at 11:01:09PM +0530, Mihir Luthra wrote: > This is almost the same way as in the arXiv paper you shared with me. > As we are dealing with paths, I saw implementing the above hash > function would make the search faster as this happens quite a few > times that files with

Re: Speed up trace mode (GSoC Project)

Hi, Thanks for the tips. ^_^ This is almost the same way as in the arXiv paper you shared with me. As we are dealing with paths, I saw implementing the above hash function would make the search faster as this happens quite a few times that files with same name have same path length from the root.

Re: Speed up trace mode (GSoC Project)

Hi Mihir, On Tue, Apr 16, 2019 at 11:59:53PM +0530, Mihir Luthra wrote: > Kindly provide your suggestions for this. > In the path search Ctrie data structure, I categorised the paths with > the hash function working like: > > If I input a path /test/files/abc.h for check > Here we have open to

Re: GSoC 2019 [Buildbot ideas]

Sure, I will try them out. Thanks On Thu, Apr 18, 2019 at 11:29 AM Mojca Miklavec wrote: > Dear Rajdeep, > > On Tue, 16 Apr 2019 at 12:38, Rajdeep Bharati wrote: > > > > About the npm dependencies: Can't it be taken care of by using > buildbot-www from pypi? > > While I'm not yet sure about the

Re: GSoC 2019 [Buildbot ideas]

Dear Rajdeep, On Tue, 16 Apr 2019 at 12:38, Rajdeep Bharati wrote: > > About the npm dependencies: Can't it be taken care of by using buildbot-www > from pypi? While I'm not yet sure about the npm packages situation, I looked a bit around and bumped into

Re: Speed up trace mode (GSoC Project)

Hi Clemens, Kindly provide your suggestions for this. In the path search Ctrie data structure, I categorised the paths with the hash function working like: If I input a path /test/files/abc.h for check Here we have open to abc.h, the hash function simply makes it “12:abc.h" where 12 is the

Re: GSoC 2019 [Buildbot ideas]

On Tue, 16 Apr 2019 at 12:38, Rajdeep Bharati wrote: > > I think one more port needs to be created: autobahn. > (https://docs.buildbot.net/current/manual/installation/requirements.html) If it's not in the ports tree yet, I believe I have this port on my computer already. (I can check when I come

Re: GSoC 2019 [Buildbot ideas]

I think one more port needs to be created: autobahn . ( https://docs.buildbot.net/current/manual/installation/requirements.html) About the npm dependencies: Can't it be taken care of by using buildbot-www from pypi?

Re: GSoC 2019 [Buildbot ideas]

Dear Mojca, Root privileges worked using vim. The new ports are shown in the port search. Thanks a lot. Rajdeep On Tue, Apr 16, 2019 at 3:09 PM Mojca Miklavec wrote: > Dear Rajdeep, > > I'm not sure to what extent my suggestion helps. If the file is in > fact locked, this won't do it, but I

Re: GSoC 2019 [Collect build statistics]

On Fri, 12 Apr 2019 at 19:50, Arjun Salyan wrote: > On Fri, Apr 12, 2019 at 3:03 AM Mojca Miklavec wrote: > >> One thing that "urgently" needs to be done is to obfuscate the email >> >> (if written at all). I'm not even sure whether we actually want the >> email being displayed there. We need it

Re: GSoC 2019 [Buildbot ideas]

On Tue, 16 Apr 2019 at 09:12, Rajdeep Bharati wrote: > > Hello, > For testing a new Portfile in my local repository, the Macports guide says > that I need to edit the sources.conf file. However, this file is locked and > I'm not able to unlock it. Did you try with root privileges? I don't know

Re: GSoC 2019 [Buildbot ideas]

Hello, For testing a new Portfile in my local repository, the Macports guide says that I need to edit the sources.conf file. However, this file is locked and I'm not able to unlock it. Could you tell me the right way to tackle this? Also, do I need to have a distfile and/or tarball to generate

Re: GSoC 2019 [Collect build statistics]

/ detect any breakages in the future. > Thank you. Since, I am currently working on parsing of maintainers I began testing from maintainers only. It helped me make significant improvements to the code which extracted the maintainers ( added to the pull request : https://github.com/macports-gsoc/mac

Re: GSoC 2019 [Collect build statistics]

Dear Arjun, I'll answer individual questions & provide further suggestion separately. Given the current state of the app with sufficient complexity, I believe that it would be wise to introduce some unit tests to be able to extensively test what happens with data you import, and to prevent /

Re: Speed up trace mode (GSoC Project)

Hi, On Fri, Apr 12, 2019 at 11:16:46PM +0530, Mihir Luthra wrote: > I was constructing the trie data structure which has to be operated > from the address space mapped by mmap(2). In place of “array of next > nodes”, I am using “array of offsets”. Sounds correct. > the void * returned from

Re: GSoC 2019 [Collect build statistics]

Hi Mojca, On Fri, Apr 12, 2019 at 3:03 AM Mojca Miklavec wrote: > Awesome! Thank You. One thing that "urgently" needs to be done is to obfuscate the email > (if written at all). I'm not even sure whether we actually want the > email being displayed there. We need it to send automated emails

Re: Speed up trace mode (GSoC Project)

Hi, I needed some advise regarding ctrie implementation. I was constructing the trie data structure which has to be operated from the address space mapped by mmap(2). In place of “array of next nodes”, I am using “array of offsets”. the void * returned from calling mmap(2), I would type cast it

Re: GSoC 2019 [Collect build statistics]

Dear Arjun, Thanks a lot for the update. On Thu, 11 Apr 2019 at 16:15, Arjun Salyan wrote: > > I have added maintainer views and tables to the demo app. > > List of maintainers is clickable on the port-detail page. > A maintainer-detail view that display info and list of maintained ports

Re: GSoC 2019 [Buildbot ideas]

Thanks, I'll attempt this. Rajdeep On Thu, Apr 11, 2019 at 8:26 PM Mojca Miklavec wrote: > Dear Rajdeep, > > On Thu, 11 Apr 2019 at 14:02, Rajdeep Bharati wrote: > > > > I had a doubt regarding the creation of buildbot 2.x Portfile: Would > writing a Portfile be sufficient or would there need

Re: GSoC 2019 [Collect build statistics]

Hi, I have added maintainer views and tables to the demo app. - List of maintainers is clickable on the port-detail page. - A maintainer-detail view that display info and list of maintained ports Examples: maintainer-detail:

Re: GSoC 2019 [Buildbot ideas]

I had a doubt regarding the creation of buildbot 2.x Portfile: Would writing a Portfile be sufficient or would there need to be other changes to the ports tree as well? Rajdeep On Tue, Apr 9, 2019 at 9:24 PM Mojca Miklavec wrote: > Dear Rajdeep, > > On Tue, 9 Apr 2019 at 17:27, Rajdeep Bharati

Re: Feedback Request for final GSoC Proposal [Speed Up Trace Mode]

Hi, Sorry for re-mailing. I know it's almost the last moment. But if possible, please provide any possible feedback. https://docs.google.com/document/d/14eSXwZ6N1vRcBudaJWlwO5G17dY5B1nHgfhh52tSnv0/edit# Regards, Mihir

Re: Wish to contribute to MacPorts as part of GSoC

to prove that you understand very precisely what you are undertaking, and prepare a solid plan of how to execute that. As Umesh already replied, we hope that we will have another chance for GSoC next year, but even outside of GSoC there are plenty opportunities to help us build a better product

Re: GSoC 2019 [Buildbot ideas]

Dear Rajdeep, On Tue, 9 Apr 2019 at 17:27, Rajdeep Bharati wrote: > > Here's a poc of buildbot workers running on mac VM using libvirt (thought I'm > not sure whether this is the kind of thing we need): > https://github.com/nextgis/buildbot Cool, nice find! I don't know how hard it would be to

Re: GSoC 2019 [Buildbot ideas]

Here's a poc of buildbot workers running on mac VM using libvirt (thought I'm not sure whether this is the kind of thing we need): https://github.com/nextgis/buildbot I have submitted a final proposal with some more changes. I'm sorry for being late (since there are just a couple of hours left

Fwd: Wish to contribute to MacPorts as part of GSoC

Hi Shreyas, While I believe you have a good set of skills, it may be a bit too late if you want to participate in GSoC with us. But we definitely welcome all kinds of contribution outside GSoC and the program is going to be there next year as well. Contributors are definitely given higher

Re: GSoC 2019 [Phase out dependency on Xcode]

Sorry for only picking up on your thread now, but > we've been somewhat overwhelmed by GSoC proposals this year. I understand that you're being overloaded right now. I've read up on last year's mailing list about GSOC and it looks like you're receiving more than 5x (?) of last year's traffic. >

GSoC 2019 submission deadline is today

Hello, *I apologize for another email which may not be of interest to many of the members here but till we figure out a new channel for GSoC (and more such) activities, I believe there is no other option than using -dev.* With only a few hours left in final submissions, I advise the students

Re: GSoC 2019 [Buildbot ideas]

Ok, thanks. One more thing: You were talking about some issues with the Collection class in buildbot data which is not well compatible with Vue. Could you specify the kind of issues? Thanks and regards Rajdeep On Tue, Apr 9, 2019 at 1:44 AM Pierre Tardy wrote: > A javascript library which you

Re: GSoC 2019 - trace mode improvements

On Sunday, 07/04/2019 15:59 CEST, Mihir Luthra <1999mihir.lut...@gmail.com> wrote: > https://docs.google.com/document/d/15cVbH6f6hBr9HryJEHUZEbRsToN1BAjY8My-oRstO9A/edit#heading=h.ng3lyvrem2d1 > > This doc is really clumsy tbh, and more like just rough notes made by me. > Though the links to

Re: GSoC 2019 - trace mode improvements

g that arise in my mind and that can catch a lot of macports's users attention is to introduce $ port news with topics/priority support, like in the venerable gentoo portage [1]. A simple news could be suffice in the case of GSoC but should be expected that there is a way to alert the user for

Re: GSoC 2019 - Feedback request

Dear Mojca, Thank you for merging the PR. And Thank you for giving me some ideas to study on and decide what I would like to work on as this GSoC. Here is my updated proposal : https://docs.google.com/document/d/1RUmFN7PSPqbGzH4h8Hqq-qkTFgS3XJ_bIrsq7GhikYE/edit?usp=sharing Can't

Re: GSoC 2019 [Collect build statistics]

Dear Arjun, On Mon, 8 Apr 2019 at 20:31, Arjun Salyan wrote: > > Dear MacPorts Community, > > I have submitted my Final Proposal. I do understand that during these last > hours it might not be possible to give feedback on the proposals. But if I am > lucky enough to get more of them, I will try

Feedback Request for final GSoC Proposal [Speed Up Trace Mode]

Hi everyone, Kindly check my final proposal and provide any possible feedback. https://docs.google.com/document/d/14eSXwZ6N1vRcBudaJWlwO5G17dY5B1nHgfhh52tSnv0/edit# Regards, Mihir

Re: GSoC 2019 [Phase out dependency on Xcode]

Sorry for only picking up on your thread now, but we've been somewhat overwhelmed by GSoC proposals this year. I didn't comment on it in the proposal document, but I like your work on the bump tool. Haven't looked at the code, but the screen recording looks like a very helpful tool. We've actually

Re: Speed up trace mode (GSoC Project)

On Tue, Apr 9, 2019 at 1:59 AM Clemens Lang wrote: > Hi, > > On Sun, Apr 07, 2019 at 01:03:12AM +0530, Mihir Luthra wrote: > > > Can you pastebin a main.log of a build that fails like this? > > > > https://pastebin.com/FVdp4WTw > > The problematic lines are > > :debug:archivefetch failed

Re: GSoC 2019 proposal - Feedback request

Hi AmirAli, On Sat, Apr 06, 2019 at 06:17:25PM +, AmirAli Mashayekhi via macports-dev wrote: > I have uploaded my proposal draft on GSoC webpage. > > Unfortunately we at EPITA(mon École) got informed late about this > years GSoC opportunity. But this doesn’t affect my true excite

Re: Speed up trace mode (GSoC Project)

Hi, On Sun, Apr 07, 2019 at 01:03:12AM +0530, Mihir Luthra wrote: > > Can you pastebin a main.log of a build that fails like this? > > https://pastebin.com/FVdp4WTw The problematic lines are :debug:archivefetch failed verification with key /opt/local/share/macports/macports-pubkey.pem

Re: GSoC 2019 [Buildbot ideas]

A javascript library which you can simply call from your main.js and which will implement all the boilerplate needed to connect your vue component to the angularjs application Regards Pierre Le lun. 8 avr. 2019 à 21:23, Rajdeep Bharati a écrit : > > Hi Pierre, > > By library do you mean a

Re: GSoC 2019 [Buildbot ideas]

Hi Pierre, By library do you mean a library of components and JSON interfaces? Regards Rajdeep On Tue, Apr 9, 2019 at 12:18 AM Pierre Tardy wrote: > Hi Rajdeep, > > We already have a yeoman generator: > https://github.com/buildbot/guanlecoja/tree/master/generator-guanlecoja > > I think the

Re: GSoC 2019 [Buildbot ideas]

Hi Rajdeep, We already have a yeoman generator: https://github.com/buildbot/guanlecoja/tree/master/generator-guanlecoja I think the current boilerplate has more than just boilerplate. It also has some code that could be factorized. It is better not to put too much in a generator, as it is hard

Re: GSoC 2019 [Collect build statistics]

Dear MacPorts Community, I have submitted my Final Proposal. I do understand that during these last hours it might not be possible to give feedback on the proposals. But if I am lucky enough to get more of them, I will try to get the job done (around 23 hours still remaining). Google Doc:

Re: GSoC Proposal

Hey, Just a gentle reminder, If I could get a reply to my previous mail as the deadline for submission is now less than a day and I would like to submit the proposal well before the deadline. Sorry for remailing. Thanks, Karan Sheth On Mon, Apr 8, 2019 at 12:05 AM KARAN SHETH wrote: > > Hey, >

Re: GSoC 2019 [Buildbot ideas]

@Mojca Miklavec Oh, I see. @Pierre Tardy Regarding the npm package: I think it would be better to create a project generator CLI (which would create the boilerplate project, similar to vue-cli or create-react-app). Do you think that would work? Can I use yeoman to do this? Thank you for help.

Re: GSoC 2019 [Buildbot ideas]

Dear Rajdeep, On Sun, 7 Apr 2019 at 19:41, Rajdeep Bharati wrote: > > I found something which might help us: https://bors.tech/homu-io/ > https://github.com/barosl/homu. > I will try it set it up on my local system and get back to you. > Mojca This sounds nice, but I wonder if it would actually

Re: GSoC 2019 [Phase out dependency on Xcode]

On Sun, 7 Apr 2019 at 16:36, Satryaji Aulia wrote: > > Hi Marcus and Mojca. > > I’ve fleshed out my proposal (also my understanding of MacOS compilers) > again. To disallow Xcode compilers, I added my idea to use a compiler > blacklist which implementation already exists. I’ve also worked a lot on

Re: GSoC 2019 - Feedback request

proposal's general structure, I > hope it makes more sense for you. > The only missing part atm is to fill the port name I will work on... You may check https://trac.macports.org/wiki/Tickets and see which ports have more bugs, update requests etc. filed. Esp. those that have been waiting fo

Re: GSoC 2019 [Phase out dependency on Xcode]

Hi Clemens, I'd also like your feedback on my proposal, particularly about Xcode dependency. What do you think? Also thanks for the 1 hour tutorial on macports-base. It helped a lot with understanding the MacPorts system, not just me but other prospective GSOC students as I read on the mailing

Re: GSoC Proposal

Hey, > There's nothing specific that I would want to comment on. > Well, to me it's not entirely clear how the automatic updates would be > supposed to work, but ... I made some changes to the update part, is it better now or am I still missing something? > And the stretch goals are somewhat

Re: GSoC 2019 [Buildbot ideas]

I found something which might help us: https://bors.tech/homu-io/ https://github.com/barosl/homu. I will try it set it up on my local system and get back to you. Rajdeep On Sun, Apr 7, 2019 at 6:17 PM Rajdeep Bharati wrote: > I was attempting to package the plugin. > A possible workflow may

Re: GSoC 2019 - Feedback request

, AmirAli Mashayekhi wrote: Dear Macports GSoC admins, I have uploaded my proposal draft on GSoC webpage. Unfortunately we at EPITA(mon École) got informed late about this years GSoC opportunity. But this doesn’t affect my true excitement about participation, open source and contributing

Re: GSoC 2019 [Phase out dependency on Xcode]

Hi Marcus and Mojca.I’ve fleshed out my proposal (also my understanding of MacOS compilers)again. To disallow Xcode compilers, I added my idea to use a compilerblacklist which implementation already exists. I’ve also worked a lot on mymacports-base PR and am confident that I can comfortably code

Re: GSoC 2019 - trace mode improvements

> > > read [1] and related thread and probably I am too late to contribute > through > GSoC. So I give up. > > > /davide > > [1] > https://lists.macports.org/pipermail/macports-dev/2019-April/040495.html Hi , https://docs.google.com/document/d/15cVbH6f6hBr9Hry

Re: GSoC 2019 - trace mode improvements

curial. Yes, I'm aware of that, but even in that case it was only you who has been notified (a bit late), there could still be other contributors who are / were not aware about GSOC. (Those subscribed to the mailing list couldn't have missed the news, and we received request to move the discussio

Re: GSoC 2019 [Buildbot ideas]

I was attempting to package the plugin. A possible workflow may be: - The user would install the package in something like a vue-cli or create-react-app. - Write the component - Pass that component to the `link` function of the plugin. - There would be options to customize the

Re: GSoC 2019 [Collect build statistics]

> > Hi, On Fri, Apr 5, 2019 at 8:58 AM Umesh Singla > wrote: > >> It’s always to good to show your work and get feedback. It’s difficult to >> comment on the quality otherwise. Please do not forget to make a PR. >> > I have submitted the PR for adding an option to portindex (which would generate

Re: Speed up trace mode (GSoC Project)

> That's unfortunately not the same, since while you're swapping the > second value, a different thread could swap the first for a different > value again. > I get your point. Generally what comes to the mind in such circumstances is blocking the other thread some way like mostly by spin locks.

GSoC 2019 proposal - Feedback request

Dear Macports Developers, I have uploaded my proposal draft on GSoC webpage. Unfortunately we at EPITA(mon École) got informed late about this years GSoC opportunity. But this doesn’t affect my true excitement about  participation, open source and contributing on them. I appreciate

Re: GSoC 2019 [Buildbot ideas]

Thanks for the feedback! On Sat, Apr 6, 2019 at 7:03 PM Mojca Miklavec wrote: > Dear Rajdeep, > > On Sat, 6 Apr 2019 at 13:33, Rajdeep Bharati wrote: > > > > I was wondering what kind of features you would like to have in the new > waterfall view? > > I don't remember whether I ever explicitly

Re: Speed up trace mode (GSoC Project)

Hi, On Sat, Apr 06, 2019 at 01:05:08AM +0530, Mihir Luthra wrote: > > You have the right ideas to solve the problem. Do keep in mind > > though that CAS will only work up to a word size or a double word > > size at most, i.e. swapping more than 64 bit with CAS atomically is > > probably not going

Re: Speed up trace mode (GSoC Project)

Hi, I was trying to test the code by making changes but I am stuck with one issue. If I install from git and set it up I always receive this error message. [1] 1) I tried `make` on base code taken as it is from git without checking out to latest version, it showed this error. 2) I tried `make`

Re: GSoC 2019 - Feedback request

; Dear Macports GSoC admins, > > I have uploaded my proposal draft on GSoC webpage. Unfortunately we at > EPITA(mon École) got informed late about this years GSoC opportunity. But > this doesn’t affect my true excitement about participation, open source and > contributing o

GSoC 2019 - trace mode improvements

a Master degree on Computer Science. In the last few months I contributed to macports-ports, mainly in the following areas: - SDR, mainly with @michaelld and @mf2k - mercurial and related, mainly with @mojca * Project Idea ** Goal The main goal of my GSoC will be to: - implement a function that auto

Re: GSoC 2019 [Buildbot ideas]

Dear Rajdeep, On Sat, 6 Apr 2019 at 13:33, Rajdeep Bharati wrote: > > I was wondering what kind of features you would like to have in the new > waterfall view? I don't remember whether I ever explicitly said I wanted some new features there :) Probably the only thing I really miss is the

Re: GSoC Proposal

On Sat, 6 Apr 2019 at 04:06, Cyril Roelandt wrote: > > Upt gives you three kinds of dependencies: build, runtime and test. This > should be done in the backend. MacPorts also splits "runtime" dependencies into two types. One are proper runtime dependencies (not needed for building the package

Re: GSoC Proposal

Hey, > Check your dependencies; this should only happen if your port does not > depend on the port that provides this file, i.e. python37. You might be > overwriting the dependency by setting depends_lib rather than appending > to it. Changing from this : if {${name} ne ${subport}} {

Re: GSoC 2019 [Buildbot ideas]

All right, thank you so much (sorry for the late reply). I was wondering what kind of features you would like to have in the new waterfall view? Rajdeep On Tue, Apr 2, 2019 at 7:46 PM Mojca Miklavec wrote: > On Tue, 2 Apr 2019 at 16:01, Pierre Tardy wrote: > > > > Not sure if this is

<    1   2   3   4   5   6   7   8   9   >