Re: GSoC 2019 - Feedback request

Dear Amir, On Sun, 7 Apr 2019 at 18:21, AmirAli Mashayekhi wrote: > > Dear Mojca (and everybody else in the mail list), > > Thank you for your response, Sorry for the misundrestanding of the proposal. > > As requested I also tried to expose myself to the whole workflow of Macports > developement

Re: Use ISO 8601 dates in Portfile comments

On Mon, 8 Apr 2019 at 07:35, Joshua Root wrote: > > ISO 8601 is a great compliant solution to recommend. > > Changing ambiguous dates to something unambiguous is a reasonable thing > to submit PRs for if you so desire. Ambiguous dates can be verified with "git log". But I would do a PR for everyt

Re: Use ISO 8601 dates in Portfile comments

On 2019-4-8 04:25 , Christopher Chavez wrote: > Currently, comments in Portfiles containing dates, such as for when remove > something in the future, are specified in whichever scheme preferred by the > port maintainer or whoever inserted the date. Some of these schemes are > region-specific (e.

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 lis

Re: Use ISO 8601 dates in Portfile comments

On Sun, 7 Apr 2019 at 20:25, Christopher Chavez wrote: > > Currently, comments in Portfiles containing dates, such as for when remove > something in the future, are specified in whichever scheme preferred by the > port maintainer or whoever inserted the date. Some of these schemes are > region-

Re: FYI: Buildbot workers are offline for a few hours

On Apr 7, 2019, at 08:57, Ryan Schmidt wrote: > I've taken the buildbot workers offline as a precaution due to thunderstorms. Back online now. \r

Idea: Quicklisp → upt → MacPorts

(Currently at least one port maintainer suggested their Lisp ports be removed from MacPorts due to the community preference for Quicklisp. However it appears that removing ports is not preferred particularly for maintained software with no known issue being delivered by MacPorts.) An idea for t

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 sho

Use ISO 8601 dates in Portfile comments

Currently, comments in Portfiles containing dates, such as for when remove something in the future, are specified in whichever scheme preferred by the port maintainer or whoever inserted the date. Some of these schemes are region-specific (e.g. mm/dd/ used in the US) and potentially ambiguou

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 be:

Re: GSoC 2019 - Feedback request

Dear Mojca (and everybody else in the mail list), Thank you for your response, Sorry for the misundrestanding of the proposal. As requested I also tried to expose myself to the whole workflow of Macports developement cycle. Here is a link for my pull request : https://github.com/macports/

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 in

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/15cVbH6f6hBr9HryJEHUZEbRsToN1BAjY8My-oRstO9A/edit#he

FYI: Buildbot workers are offline for a few hours

I've taken the buildbot workers offline as a precaution due to thunderstorms. I'll start them back up later today. \r

Re: GSoC 2019 - trace mode improvements

Dear Davide, On Sun, 7 Apr 2019 at 12:55, Davide Gerhard wrote: > On Sunday, 07/04/2019 11:55 CEST, Mojca Miklavec wrote: > > On Sun, 7 Apr 2019 at 09:40, Davide Gerhard wrote: > >> > >> Sorry, I am late but I saw only the other day that MacPorts > >> participate to the Google Summer of Code. > >

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 setti

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: GSoC 2019 - trace mode improvements

On Sunday, 07/04/2019 11:55 CEST, Mojca Miklavec wrote: > Dear Davide, > > On Sun, 7 Apr 2019 at 09:40, Davide Gerhard wrote: >> >> Seems that macports-dev@ has not received my proposal (sent yesterday); >> moreover, mailman does not answer to my command or only after some hour. > > This is str

Re: [macports-ports] branch master updated: glslang: new port

> On Apr 6, 2019, at 7:52 AM, Josh de Kock wrote: > > Chris Jones (cjones051073) pushed a commit to branch master > in repository macports-ports. > > https://github.com/macports/macports-ports/commit/20b22e76e49c9bcc2e493f45f7574f14a76e6edb > >

Re: [MacPorts] #58307: [port abandoned] abcde

> On Apr 5, 2019, at 8:18 PM, Gabriel Rosenkoetter wrote: > > On 2019-04-05 17:02 EDT, MacPorts wrote: >> #58307: [port abandoned] abcde >> Maintainer has not had any activity >> [https://trac.macports.org/search?q=eclipsed.net since 2016] and had been >> assigned #56443. >> >> #48948 was also o

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. Bu

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 if there

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 s

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` on

Re: GSoC 2019 - trace mode improvements

Dear Davide, On Sun, 7 Apr 2019 at 09:40, Davide Gerhard wrote: > > Seems that macports-dev@ has not received my proposal (sent yesterday); > moreover, mailman does not answer to my command or only after some hour. This is strange and might need to be put to attention of our infrastructure team.

Re: GSoC 2019 - Feedback request

Dear Amir, Nice to see you at MacPorts! You should send your email to the macports development mailing list and you would get the answer there. (I'm forwarding it to the mailing list now, but you should subscribe for the future.) On Sat, 6 Apr 2019 at 20:14, AmirAli Mashayekhi wrote: > > Dear Ma

GSoC 2019 - trace mode improvements

Sorry, I am late but I saw only the other day that MacPorts participate to the Google Summer of Code. Any comment will be appreciate. * Personal Details Name: Davide Gerhard Email: rain...@irh.it IRC: ra1nb0w at freenode Github: @ra1nb0w University: University of Trento (Italy) Location: Ital