Re: Can I trick base into installing ports that are built against libc++ on systems configured to stdlib=libc++ ?

Well blow me over, Josh. It does actually work. I know all the clang ports clang-3.7 and up are built against libc++. On my 10.6.8 system configured with cxx_stdlib=libc++, sudo port -v -b install clang-6.0 cxx_stdlib=libstdc++ downloads a perfectly workable clang-6.0 binary from the MacPorts

Re: GSoC Proposal

> I generated a portfile for py-upt and tried installing that after a few > manual edits, which will actually be automated in the future. > It did install properly without any errors but I guess there's some issue > with the path and because of which it was unuseable, once I figure this out > s

Re: GSoC Proposal

On 2019-04-01 11:39, Mojca Miklavec wrote: > Cyril: what's your desired destination for such work? I would suggest > placing the repositories on either > https://framagit.org/upt > or create a repository under > https://github.com/macports-gsoc > and do the pull request and code review on e

Re: GSoC Proposal

Hey, On Mon, Apr 1, 2019 at 8:34 PM Mojca Miklavec wrote: > On Mon, 1 Apr 2019 at 16:38, Renee Otten wrote: > > > > there is a figure showing a WebUI that is not described (personally I am > not sure if that would be needed anyway). > > My assumption was that Karan planned to submit "an alternat

Re: GSoC Proposal

Hey, On Mon, Apr 1, 2019 at 8:08 PM Renee Otten wrote: > hi Karan, Mojca, Cyril, > > > I am happy to help with testing and provide feedback. I quickly glanced > over the proposal draft and agree with what Cyril said; in addition, there > is a figure showing a WebUI that is not described (persona

Re: GSoC Proposal

Hey, On Mon, Apr 1, 2019 at 3:09 PM Mojca Miklavec wrote: > Dear Karan, > > Just a few quick notes (for others as well). > > On Sun, 31 Mar 2019 at 22:00, KARAN SHETH via macports-dev wrote: > > > > I have uploaded the project. > > Macports-Backend : https://github.com/Korusuke/upt-macports > >

Re: GSoC Proposal

Hey, I have completed most of the changes that you suggested. Haskell frontend has been now added to technical details and I guess I got why you were saying that why it would be tricky to add it as a frontend. Web UI has been removed seeing that it won't be a good add-on as suggested by Renne. Pl

Re: GSoC 2019 [Collect build statistics]

Dear Arjun, On Mon, 1 Apr 2019 at 18:38, Arjun Salyan wrote: > > Hi, > I was working on keeping the PortIndex updated, and was able to achieve this: > > Sync Portindex from > 'rsync://rsync.macports.org/macports//trunk/dports/PortIndex_darwin_16_i386/PortIndex' > Update or Add ports that were re

Re: GSoC 2019 [Buildbot ideas]

On Mon, 1 Apr 2019 at 18:52, Rajdeep Bharati wrote: > > When I would be configuring the real (production) macports buildmaster, then > would the old database be used? Not if you deploy it on a fresh server, unless you explicitly put the database there (import it from elsewhere). (I don't know ho

Re: GSoC 2019 [Phase out dependency on Xcode]

Dear Satryaji, On Mon, 1 Apr 2019 at 21:29, Satryaji Aulia wrote: > > Hi again Mojca and Marcus. > > >> I notice how useful a "port bump" command would be if it existed. > > > > Yes, it would be. > > I've started my implementation, under macports-base/src/port1.0/portbump.tcl. Cool! > Besides th

Re: Disc space low on darwin 12 and 14 builders

On Mar 30, 2019, at 12:07, Chris Jones wrote: > Could someone clear out a bit the osx 10.8 and 10.10 builder discs ? I am > seeing a number of failures on these due to disc space issues. 10.7 is also > probably low... I've cleaned up a little bit, but it's going to continue to be a problem u

Re: macports-dev Digest, Vol 152, Issue 1

Hi Mihir, On Mon, Apr 01, 2019 at 09:13:42PM +0530, Mihir Luthra wrote: > Actually my question is what is the purpose of the call (1), because > till what I understood, kevent(2) only lets the program proceed > further when it will return and it only returns when it detects an > event. Call (1) is

Re: GSoC 2019 [Phase out dependency on Xcode]

Hi again Mojca and Marcus. > On 1 Apr 2019, at 17.15, Mojca Miklavec wrote: > > I'm not in position to answer this, but you may check some discussion > on this mailing list (from March / GSOC) regarding trace mode, in case > it's relevant or provides you some more insight. I have read more abou

Re: GSoC 2019 [Buildbot ideas]

No, I didn't. I guess I did not have any older builds before that date (26th March). That's why the database only contains builds after that date. When I would be configuring the real (production) macports buildmaster, then would the old database be used? Rajdeep On Mon, Apr 1, 2019 at 9:35 PM Mo

Re: GSoC 2019 [Collect build statistics]

Hi, I was working on keeping the PortIndex updated, and was able to achieve this: - Sync Portindex from 'rsync:// rsync.macports.org/macports//trunk/dports/PortIndex_darwin_16_i386/PortIndex ' - Update or Add ports that were recently built on 10.14_x86_64 (using time frame 'last 24

Re: GSoC 2019 [Buildbot ideas]

Dear Rajdeep, On Mon, 1 Apr 2019 at 17:47, Rajdeep Bharati wrote: > > Yes, I think so. But I have done `buildbot restart master` several times > after that. Did you also delete the database? Merely restarting the configuration should not delete old build results. Mojca

Re: GSoC 2019 [Buildbot ideas]

Yes, I think so. But I have done `buildbot restart master` several times after that. On Mon, Apr 1, 2019 at 8:53 PM Mojca Miklavec wrote: > On Mon, 1 Apr 2019 at 16:37, Rajdeep Bharati wrote: > > > > I have set up a simple datepicker widget with view #1. See the demo in > the video below. > > Aw

Re: macports-dev Digest, Vol 152, Issue 1

> > > > Note that kevent(2) is a multi-purpose API. The call you refer to as (1) > is not actually the mainloop of tracelib run. Rather, the call a little > further down is: > > keventstatus = kevent(kq, NULL, 0, res_kevents, MAX_SOCKETS, NULL)) > > This will also return for new connections to th

Re: GSoC 2019 [Buildbot ideas]

On Mon, 1 Apr 2019 at 16:37, Rajdeep Bharati wrote: > > I have set up a simple datepicker widget with view #1. See the demo in the > video below. Awesome, thank you! This would probably be something very useful for any project using buildbot, not just for us. > Screen Recording 2019-04-01 at 8.

Re: GSoC 2019 [Buildbot ideas]

Dear Pierre, On Mon, 1 Apr 2019 at 17:06, Pierre Tardy wrote: > In buildbot, there is no difference between author and commiter, we only > keep the author. > Do you think committer info is really needed? > This has nothing to do with the project proposal at hand, but yes, this would be super use

Re: GSoC 2019 [Buildbot ideas]

In buildbot, there is no difference between author and commiter, we only keep the author. Do you think committer info is really needed? Pierre Le lun. 1 avr. 2019 à 17:04, Rajdeep Bharati a écrit : > I'm using npm run watch. In the boilerplate, there is no field called > 'committer' in the ch

Re: GSoC 2019 [Buildbot ideas]

I'm using npm run watch. In the boilerplate, there is no field called 'committer' in the change: https://github.com/uglycoyote/buildbot-react-plugin-boilerplate/blob/master/src/BuildbotJsonInterfaces.ts. It only contains the author field. I also tried using the other fields, but none of them had an

Re: GSoC Proposal

On Mon, 1 Apr 2019 at 16:38, Renee Otten wrote: > > there is a figure showing a WebUI that is not described (personally I am not > sure if that would be needed anyway). My assumption was that Karan planned to submit "an alternative" proposal for another project (web app), but I might be wrong. M

Re: GSoC 2019 [Buildbot ideas]

Hi Rajdeep, Against which data are you working on? are you using gulp dev proxy or something? The committer name is normally a field in the change, but it works only if the changesource extracts the data Regards Pierre Le lun. 1 avr. 2019 à 16:37, Rajdeep Bharati a écrit : > I have set up a

Re: GSoC Proposal

hi Karan, Mojca, Cyril, I am happy to help with testing and provide feedback. I quickly glanced over the proposal draft and agree with what Cyril said; in addition, there is a figure showing a WebUI that is not described (personally I am not sure if that would be needed anyway). I agree tha

Re: GSoC 2019 [Buildbot ideas]

I have set up a simple datepicker widget with view #1. See the demo in the video below. Screen Recording 2019-04-01 at 8.02.02 PM.mov However, I have some doubts/problems: - The last date is showing only till

Re: how to deal with large data files

Our approach to this kind of use case was to add download commands to the pre-activate stage of the Portfile. See the example below. _ # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=

Re: GSoC 2019 [Phase out dependency on Xcode]

Dear Satryaji, On Sun, 31 Mar 2019 at 21:37, Satryaji Aulia wrote: > > - Xcode detection > > The detailed explanation is helpful and it clarifies a lot. So to me it seems > like the core solution of the problem is simple but the extended > functionality (trace mode) is a bit more complex. I'll r

Re: GSoC Proposal

Dear Karan, Just a few quick notes (for others as well). On Sun, 31 Mar 2019 at 22:00, KARAN SHETH via macports-dev wrote: > > I have uploaded the project. > Macports-Backend : https://github.com/Korusuke/upt-macports > NPM-Frontend : https://github.com/Korusuke/upt-npm Awesome, thank you very

Re: Can I trick base into installing ports that are built against libc++ on systems configured to stdlib=libc++ ?

On Mon, 1 Apr 2019 at 06:34, Ken Cunningham wrote: > > I doubt this is possible, but it strikes me that a number of big ports, like > clang-8.0, are actually forced in the portfile to build against libc++. > > And my 10.6.8 system is configured to use stdlib=libc++. > > But base can't rationalize