Re: Relax port lint rule for patchfile naming

2018-03-16 Thread Joshua Root
On 2018-3-17 09:05 , Mojca Miklavec wrote: > On 16 March 2018 at 15:02, Ryan Schmidt wrote: >> >> On Mar 16, 2018, at 08:40, Mojca Miklavec wrote: >> >>> How will you distinguish patchfiles from others, like select lists, ed >>> files, Makefiles etc? >> >> I wouldn't. If the author of the portfile

Re: Relax port lint rule for patchfile naming

2018-03-16 Thread Mojca Miklavec
On 16 March 2018 at 15:02, Ryan Schmidt wrote: > > On Mar 16, 2018, at 08:40, Mojca Miklavec wrote: > >> How will you distinguish patchfiles from others, like select lists, ed >> files, Makefiles etc? > > I wouldn't. If the author of the portfile finds that distinction important, > they could con

Re: app portgroup bouncing icon weirdness …

2018-03-16 Thread Kenneth F . Cunningham
On 2018-03-16, at 1:04 PM, Eric Le Lay wrote: > For gPodder +x11 [1], I've added an entry in Info.plist to > prevent an icon in the dock. > With +quartz, it uses the py27-gtk-osx-application library to behave like a > proper Mac app. > > [1] > https://github.com/macports/macports-ports/blob/

Re: Relax port lint rule for patchfile naming

2018-03-16 Thread Joshua Root
On 2018-3-16 22:39 , Ryan Schmidt wrote: > I would be happy if lint were changed to just check that patchfile names end > with .diff or .patch. Would anyone object to that? I could've sworn we had this conversation years ago and this was the conclusion. :) So yes, please do make this change. -

Re: MacPorts from behind proxy servers & fetching the file directly

2018-03-16 Thread Daniel J. Luke
On Mar 16, 2018, at 11:28 AM, db wrote: > On 16 Mar 2018, at 16:03, "Daniel J. Luke" wrote: >> portfiles could in theory attempt to connect to any port, so a comprehensive >> list like you're asking for is probably not possible to create. > > But there could be one in practice, as there is infr

Re: app portgroup bouncing icon weirdness …

2018-03-16 Thread Eric Le Lay
Le Fri, 16 Mar 2018 04:47:36 -0500, Ryan Schmidt a écrit : > On Mar 15, 2018, at 23:31, Kevin Reid wrote: > > > On Thu, Mar 15, 2018 at 8:38 PM, Kenneth F. Cunningham wrote: > >> The dock icon on the ports I launch via the bash script generate > >> via the app PG seem to never stop bouncing --

Re: MacPorts from behind proxy servers & fetching the file directly

2018-03-16 Thread Rainer Müller
On 2018-03-16 12:31, Mojca Miklavec wrote: > While discussing GSOC with Umesh, he repeated what we already > discussed during the meeting. Students in campuses (including the one > where he is studying and from which roughly 40 students participate in > GSOC each year) might be behind proxies and m

Re: MacPorts from behind proxy servers & fetching the file directly

2018-03-16 Thread db
On 16 Mar 2018, at 16:03, "Daniel J. Luke" wrote: > portfiles could in theory attempt to connect to any port, so a comprehensive > list like you're asking for is probably not possible to create. But there could be one in practice, as there is infrastructure building all ports. Ever upgraded out

Re: MacPorts from behind proxy servers & fetching the file directly

2018-03-16 Thread Daniel J. Luke
On Mar 16, 2018, at 8:45 AM, db wrote: > Is there any list of ports used for installing base and **any other** port? portfiles could in theory attempt to connect to any port, so a comprehensive list like you're asking for is probably not possible to create. It might be worthwhile to look at swi

Re: Relax port lint rule for patchfile naming

2018-03-16 Thread Ryan Schmidt
On Mar 16, 2018, at 08:40, Mojca Miklavec wrote: > How will you distinguish patchfiles from others, like select lists, ed files, > Makefiles etc? I wouldn't. If the author of the portfile finds that distinction important, they could continue to maintain it. port lint wouldn't care. > I suppor

Re: Relax port lint rule for patchfile naming

2018-03-16 Thread Ryan Schmidt
On Mar 16, 2018, at 08:03, Arno Hautala wrote: > The only reason I can think of for keeping the prefix is that all > patches would be sorted together in a file listing. Not a very strong > reason. Nothing would prevent a port author from continuing to do that, if they wish to.

Re: Relax port lint rule for patchfile naming

2018-03-16 Thread Mojca Miklavec
How will you distinguish patchfiles from others, like select lists, ed files, Makefiles etc? I support relaxing rules, but you cannot even rely on all files matching the relaxed version form. See also recent discussion about whether lint should return nonzero value on warnings. Mojca

Re: Relax port lint rule for patchfile naming

2018-03-16 Thread Arno Hautala
The only reason I can think of for keeping the prefix is that all patches would be sorted together in a file listing. Not a very strong reason. On Fri, Mar 16, 2018 at 7:39 AM, Ryan Schmidt wrote: > I think we should relax the restrictions on patchfile naming currently > implemented in port lint

Re: MacPorts from behind proxy servers & fetching the file directly

2018-03-16 Thread db
On 16 Mar 2018, at 12:31, Mojca Miklavec wrote: > While discussing GSOC with Umesh, he repeated what we already > discussed during the meeting. Students in campuses (including the one > where he is studying and from which roughly 40 students participate in > GSOC each year) might be behind proxies

Re: [macports-ports] branch master updated: devel/automake: update to 1.16.1

2018-03-16 Thread Ryan Schmidt
On Mar 15, 2018, at 21:30, Perry E. Metzger wrote: > On Thu, 15 Mar 2018 18:14:16 -0500 Ryan Schmidt wrote: >> On Mar 15, 2018, at 17:41, Adam Mercer wrote: >> >>> On Thu, Mar 15, 2018 at 3:32 PM, Ryan Schmidt wrote: >>> > Good point. I'll get a patch ready to switch back to the .gz as >

Relax port lint rule for patchfile naming

2018-03-16 Thread Ryan Schmidt
I think we should relax the restrictions on patchfile naming currently implemented in port lint. I'd like to discuss it here before I file a ticket. Currently, we complain if a patchfile is not named "patch-*.diff". But we already have many files in the repository named "*.patch" for example. We

MacPorts from behind proxy servers & fetching the file directly

2018-03-16 Thread Mojca Miklavec
Hi, While discussing GSOC with Umesh, he repeated what we already discussed during the meeting. Students in campuses (including the one where he is studying and from which roughly 40 students participate in GSOC each year) might be behind proxies and might not even be able to run MacPorts due to b

Re: Buildbot proposal: add custom build properties for order and priority

2018-03-16 Thread Ryan Schmidt
On Mar 16, 2018, at 05:26, Mojca Miklavec wrote: >> The property got called "priority" and right now the nextBuild function only >> looks at that, not the timestamp. This is fine, so long as portwatcher waits >> for all portbuilders to finish, as it currently does. > > I semi-forgot about that

Re: Buildbot proposal: add custom build properties for order and priority

2018-03-16 Thread Mojca Miklavec
On 15 March 2018 at 05:31, Ryan Schmidt wrote: > On Mar 11, 2018, at 06:01, Ryan Schmidt wrote: > >> We currently build ports in a somewhat random order (see >> https://trac.macports.org/ticket/52766). By default, the next build that >> buildbot starts is the one that was scheduled first. But if

Re: CI system for PR builds

2018-03-16 Thread Ryan Schmidt
On Mar 15, 2018, at 07:00, db wrote: > On 15 Mar 2018, at 05:13, Ryan Schmidt wrote: >> Because PRs come from untrusted sources, we have to assume their contents >> are tainted. So after any PR is finished building, the VM is tainted and we >> have to throw it away and make a new one from our te

Re: Changing default cxx_stdlib to libc++

2018-03-16 Thread Ryan Schmidt
On Mar 15, 2018, at 07:01, db wrote: > On 15 Mar 2018, at 05:19, Ryan Schmidt wrote: >> On Mar 14, 2018, at 07:23, db wrote: >>> On 14 Mar 2018, at 01:14, Rainer Müller wrote: Are you going to sponsor a dedicated Mac server for GitLab CI? Travis CI is available at no cost and we have no

Re: app portgroup bouncing icon weirdness …

2018-03-16 Thread Ryan Schmidt
On Mar 15, 2018, at 23:31, Kevin Reid wrote: > On Thu, Mar 15, 2018 at 8:38 PM, Kenneth F. Cunningham wrote: >> The dock icon on the ports I launch via the bash script generate via the app >> PG seem to never stop bouncing -- they bounce and bounce, until the >> application is finally quit, and