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 length

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? Rajd

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 fin

Re: compiler.{white,black}list usage, especially in cxx11-1.1 PG context

compiler.whitelist sadly is a *huge* misnomer and tricks people into believing that the listed compilers will be used if they are already available/installed. I have personally never thought that, and nor do I think it was ever the intention. To me the whitelist has always been read as 'use

Re: compiler.{white,black}list usage, especially in cxx11-1.1 PG context

* On 4/16/19 9:30 AM, Mihai Moldovan wrote: > The cxx11 1.1 PG currently sets compiler.whitelist to some value (either > mp-gcc-6.0/7.0 or mp-clang-5.0) and follows up with a bit of blacklisting if > the > stdlib is libc++ and otherwise just blacklists. That's what I get for just skimming stuff.

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 to

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

compiler.{white,black}list usage, especially in cxx11-1.1 PG context

The cxx11 1.1 PG currently sets compiler.whitelist to some value (either mp-gcc-6.0/7.0 or mp-clang-5.0) and follows up with a bit of blacklisting if the stdlib is libc++ and otherwise just blacklists. That's hardly the proper way to do compiler selection. compiler.whitelist sadly is a *huge* mi

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 chec