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 checksum. For the buidbot Portfile, would it be better to create a diff patch (ignoring the npm dependencies ATM).
Thank you. Rajdeep On Thu, Apr 11, 2019 at 10:10 PM Rajdeep Bharati <rajdeepbharat...@gmail.com> wrote: > Thanks, I'll attempt this. > > Rajdeep > > On Thu, Apr 11, 2019 at 8:26 PM Mojca Miklavec <mo...@macports.org> 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 to be other changes to >> the ports tree as well? >> >> We would presumably move the contents of the existing buildbot / >> buildbot-slave ports under buildbot-0.8 / buildbot-slave-0.8 and put >> the new one under buildbot & buildbot-worker (the buildbot-slave could >> potentially stay without being renamed since the name doesn't "clash", >> or be declared obsolete and replaced_by buildbot-slave-0.8, just to be >> consistent with buildbot-0.8 naming; not sure what is better). >> >> We would want to keep those two old ports for a while, at least until >> we actually move our infrastructure to the new version, but >> potentially also for the sake of other users who might be running the >> old buildbot master that requires the old buildbot slaves (me >> included; but I should do the transition in my other project as well, >> I was just too lazy). >> >> But for the start feel free to ignore all those strange constraints. >> The only thing we need to start with is a working port for the latest >> version, and doing the last step should be trivial for any regular >> contributor to ports with zero knowledge about buildbot. >> >> It could be that a few additional ports would be needed for >> dependencies of buildbot (like some of the javascript stuff). I'm not >> sure if those should be installed via npm directly (as part of >> additional instructions) or if there's a feasible way to package them >> nicely and depend on them, so that everything would simply work out of >> the box after installing the port. Maybe step one could be to package >> just buildbot (master and worker). Optional step 2 to package some >> dependencies. We should check what other distributions are doing. Step >> 3 to take care of transition of the old stuff (could be done by others >> as well). >> >> Mojca >> >
