Re: [macports-ports] branch master updated: aacgain: Update to v1.9

Hi Ryan, On Sun, Apr 8, 2018 at 2:33 PM, Ryan Schmidt wrote: > > On Apr 8, 2018, at 03:46, Jackson Isaacwrote: > >> Jackson Isaac (JacksonIsaac) pushed a commit to branch master >> in repository macports-ports. >> >> >>

Re: [macports-ports] branch master updated: aacgain: Update dirname in post-extract phase

On Apr 8, 2018, at 04:12, Jackson Isaac wrote: > Jackson Isaac (JacksonIsaac) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/65defdc294622caa6e4c44d874286917a1d51ce1 > > The following commit(s) were added to

Re: [macports-ports] branch master updated: aacgain: Update dirname in post-extract phase

On 2018-04-08 12:56, Jackson Isaac wrote: > On Sun, Apr 8, 2018 at 3:33 PM, Jackson Isaac wrote: >> I did find one at "https://github.com/mecke/aacgain; but I was not so >> sure if they both are by same author since 'alvarez' was mentioned at >>

Re: CI system for PR builds

On Apr 8, 2018, at 06:12, db wrote: > On 8 Apr 2018, at 12:42, Zero King wrote: >> On Sun, Apr 08, 2018 at 12:20:34PM +0200, db wrote: >>> If you review the code before, that should never be the case and it would >>> build just once if it succeeds, right? Or am I missing something how PRs >>>

Re: CI system for PR builds

On Apr 8, 2018, at 06:49, db wrote: > On 8 Apr 2018, at 13:34, Ryan Schmidt wrote: >> No, as I think we've explained several times already, now, Travis CI builds >> the proposed change automatically, immediately after it's submitted. The >> purpose is to verify that it builds, and the results

Re: CI system for PR builds

On 8 Apr 2018, at 13:34, Ryan Schmidt wrote: > No, as I think we've explained several times already, now, Travis CI builds > the proposed change automatically, immediately after it's submitted. The > purpose is to verify that it builds, and the results of that build can

Re: CI system for PR builds

> On Apr 8, 2018, at 03:49, Rainer Müller wrote: > > We need to stop investing > so much effort into legacy systems. True. Making current software build on ancient compliers is a waste of effort. Finish the plan to push all those systems to libc++, put forward a modern

Re: CI system for PR builds

On 2018-04-08, at 6:46 AM, Ryan Schmidt wrote: > Yes, I know you like to build your legacy MacPorts installs with a different > copy of curl. And yes, we have a ticket tracking that issue as well. It's my nature. I just can't understand why people would spend years working around a problem

Re: CI system for PR builds

On Apr 8, 2018, at 08:40, Ken Cunningham wrote: > > On Apr 8, 2018, at 03:49, Rainer Müller wrote: > >> We need to stop investing >> so much effort into legacy systems. > > True. Making current software build on ancient compliers is a waste of > effort. > > Finish the plan to push all those

Re: [macports-ports] branch master updated: aacgain: Update to v1.9

On Apr 8, 2018, at 03:46, Jackson Isaacwrote: > Jackson Isaac (JacksonIsaac) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/30c9fad4f1d0e000525c5f2bb5119453f3e373fa > > The following commit(s) were added to

Re: CI system for PR builds

On 2018-04-08 12:06, Ryan Schmidt wrote: >> As the buildbot has no local packages installed, operations like >> checking for the existence of a package over HTTP and then fetching the >> file will be slow. I expect this to be one major bottleneck. Our usual >> portbuilders have all previously

Re: [macports-ports] branch master updated: aacgain: Update dirname in post-extract phase

On Sun, Apr 8, 2018 at 3:05 PM, Ryan Schmidt wrote: > > On Apr 8, 2018, at 04:12, Jackson Isaac wrote: > >> Jackson Isaac (JacksonIsaac) pushed a commit to branch master >> in repository macports-ports. >> >> >>

Re: CI system for PR builds

On Sun, Apr 08, 2018 at 12:20:34PM +0200, db wrote: On 7 Apr 2018, at 19:44, Clemens Lang wrote: Remember that Portfiles can execute arbitrary code and root access is available from Portfiles. We do not want to run arbitrary code in a PR on the same build machines we use to

Re: CI system for PR builds

On Apr 8, 2018, at 07:02, db wrote: > On 8 Apr 2018, at 13:50, Ryan Schmidt wrote: >> On Apr 8, 2018, at 06:49, db wrote: >> On 8 Apr 2018, at 13:34, Ryan Schmidt wrote: No, as I think we've explained several times already, now, Travis CI builds the proposed change automatically,

Re: CI system for PR builds

On Apr 8, 2018, at 06:32, db wrote: > On 8 Apr 2018, at 13:18, Ryan Schmidt wrote: >> On Apr 8, 2018, at 06:12, db wrote: >>> That seems to waste at least buildtime and storage. >> What do you mean? >>> Many updates and revbumps could be almost automatically deployed (after a >>> quick review).

Re: CI system for PR builds

On 8 Apr 2018, at 13:18, Ryan Schmidt wrote: > On Apr 8, 2018, at 06:12, db wrote: >> That seems to waste at least buildtime and storage. > What do you mean? >> Many updates and revbumps could be almost automatically deployed (after a >> quick review). > Isn't that we do

Re: CI system for PR builds

On 7 Apr 2018, at 19:44, Clemens Lang wrote: > Remember that Portfiles can execute arbitrary code and root access is > available from Portfiles. We do not want to run arbitrary code in a PR > on the same build machines we use to build packages that we will > distribute to our

Re: CI system for PR builds

On 8 Apr 2018, at 13:50, Ryan Schmidt wrote: > On Apr 8, 2018, at 06:49, db wrote: > On 8 Apr 2018, at 13:34, Ryan Schmidt wrote: >>> No, as I think we've explained several times already, now, Travis CI builds >>> the proposed change automatically, immediately after it's

Re: CI system for PR builds

On Apr 7, 2018, at 19:04, Rainer Müller wrote: > On 2018-04-07 19:44, Clemens Lang wrote: >> For these resons, we want to reset the machines to a clean state before >> every build, which we could do with buildbot, but requires some python >> magic that hasn't been written yet. > > I think this

Re: [macports-ports] branch master updated: aacgain: Update dirname in post-extract phase

On Sun, Apr 8, 2018 at 3:33 PM, Jackson Isaac wrote: > On Sun, Apr 8, 2018 at 3:05 PM, Ryan Schmidt wrote: >> >> On Apr 8, 2018, at 04:12, Jackson Isaac wrote: >> >>> Jackson Isaac (JacksonIsaac) pushed a commit to branch master >>> in repository

Re: CI system for PR builds

On 8 Apr 2018, at 12:42, Zero King wrote: > On Sun, Apr 08, 2018 at 12:20:34PM +0200, db wrote: >> If you review the code before, that should never be the case and it would >> build just once if it succeeds, right? Or am I missing something how PRs are >> handled? > CI builds

Re: CI system for PR builds

On Apr 8, 2018, at 10:20, Ken Cunningham wrote: > On 2018-04-08, at 6:46 AM, Ryan Schmidt wrote: > >> Yes, I know you like to build your legacy MacPorts installs with a different >> copy of curl. And yes, we have a ticket tracking that issue as well. > > It's my nature. > > I just can't

Re: CI system for PR builds

On 2018-04-07, at 5:04 PM, Rainer Müller wrote: > For distfiles, it would be possibile to apply a trick with a union mount > to create a local overlay that allows writing new files: > > mount -t nfs -o ro,union mirror:.../distfiles \ >/opt/local/var/macports/distfiles >

Re: [macports-base] branch master updated: Honour startupitem.install at activation time

On 2018-4-9 07:55 , Rainer Müller wrote: > On 2018-04-08 03:26, Joshua Root wrote: >> Joshua Root (jmroot) pushed a commit to branch master >> in repository macports-base. >> >> https://github.com/macports/macports-base/commit/3dde77d7d6c66dbb8fcc1d4b1b4972a2ac8b1947 >> >> The following commit(s)

Re: Online MacPorts Meeting on 21st April at 13:00 UTC - suggestion

On 2018-04-07 14:18, William H. Magill wrote: > IRC is still quite popular in Europe, but is little used in the US. IRC on our #macports channel is fine to ask questions for which you do not want to write a lengthy email or to debug problems with quick back-and-forth on what to check or try.

Re: [macports-base] branch master updated: Honour startupitem.install at activation time

On 2018-04-08 03:26, Joshua Root wrote: > Joshua Root (jmroot) pushed a commit to branch master > in repository macports-base. > > https://github.com/macports/macports-base/commit/3dde77d7d6c66dbb8fcc1d4b1b4972a2ac8b1947 > > The following commit(s) were added to refs/heads/master by this push: >

Re: [macports-base] branch master updated: Honour startupitem.install at activation time

On 2018-4-9 08:43 , Rainer Müller wrote: > This handles ports that create .plist files via startupitem.* or the new > startupitems. However, there are also ports that install custom .plist > file to ${destroot}/Library/Launch*. Some ports even do that > unconditionally. Ports that do this should

Re: [macports-base] branch master updated: Honour startupitem.install at activation time

On 2018-4-9 10:20 , Rainer Müller wrote: > On 2018-04-09 01:20, Joshua Root wrote: >> On 2018-4-9 08:43 , Rainer Müller wrote: >>> This handles ports that create .plist files via startupitem.* or the new >>> startupitems. However, there are also ports that install custom .plist >>> file to

Re: [macports-base] branch master updated: Honour startupitem.install at activation time

On 2018-04-09 01:20, Joshua Root wrote: > On 2018-4-9 08:43 , Rainer Müller wrote: >> This handles ports that create .plist files via startupitem.* or the new >> startupitems. However, there are also ports that install custom .plist >> file to ${destroot}/Library/Launch*. Some ports even do that

Re: [macports-base] branch master updated: Honour startupitem.install at activation time

On 2018-04-09 00:06, Joshua Root wrote: > On 2018-4-9 07:55 , Rainer Müller wrote: >> On 2018-04-08 03:26, Joshua Root wrote: >>> Joshua Root (jmroot) pushed a commit to branch master >>> in repository macports-base. >>> >>>