Re: How to fetch and extract patches in archives?

On Sun, Mar 18, 2018 at 03:15:25PM +, G A wrote: What? Macports supports most archives zip, gz, bz2, etc extract the patches from the tarball add them to the Portname/Portfile/files/*. That's the way I've been updating the w3m port. But the patches are getting bigger (upstream is

Re: Python default version

On 19 March 2018 at 16:52, Ryan Schmidt wrote: > > I should clarify that there's nothing special in my proposal about Python > 3.6. I'm merely proposing that when we use Python, we should now prefer to > use the latest stable version of 3.x, not the latest stable version of 2.x. > If stable

Re: [macports-base] 14/18: fetch: Remove svn.method option

On 20 March 2018 at 02:32, Ryan Schmidt wrote: > Note: this commit is to the vcs-fetch branch, not to master. > > On Mar 18, 2018, at 19:20, Rainer Müller wrote: > >> Rainer Müller (raimue) pushed a commit to branch vcs-fetch >> in repository macports-base. >> >> >>

Re: [macports-base] 14/18: fetch: Remove svn.method option

On 2018-03-20 02:32, Ryan Schmidt wrote: > Note: this commit is to the vcs-fetch branch, not to master. > > On Mar 18, 2018, at 19:20, Rainer Müller wrote: > >> Rainer Müller (raimue) pushed a commit to branch vcs-fetch >> in repository macports-base. >> >> >>

Re: [macports-base] 12/18: fetch: Always use port:git for fetch.type git

On 2018-03-20 10:58, Clemens Lang wrote: > - On 20 Mar, 2018, at 02:58, Ryan Schmidt ryandes...@macports.org wrote: > Unfortunately that version of git has a bug in its 'git archive' that was > later fixed. > However, this bug causes the output to change, which breaks the entire > approach

Re: Enhance livecheck to check not only version but also checksums

On 20 Mar 2018, at 00:59, Ryan Schmidt wrote: > Once that's done, it makes it easier to implement a better "bump" command -- > one that can use any published checksums and compute the rest, and warn if no > checksums were published. >

Re: How to prevent fetching from macports mirrors

On 20 Mar 2018, at 03:34, Ryan Schmidt wrote: > On Mar 19, 2018, at 16:29, db wrote: >> Is there any way to set in macports.conf to only fetch from master site >> and/or, if needed, try a mirror? > What do you mean? MacPorts already tries to fetch from the master_sites

Re: How to prevent fetching from macports mirrors

On 2018-3-21 00:30 , db wrote: > On 20 Mar 2018, at 03:34, Ryan Schmidt wrote: >> On Mar 19, 2018, at 16:29, db wrote: >>> Is there any way to set in macports.conf to only fetch from master site >>> and/or, if needed, try a mirror? >> What do you mean? MacPorts already

Gsoc-Announcements distributed over the ports tree

Currently,on MacPort website there is news tab which consists of news about different version of MacPorts. So we have to add one tab under which i will contruct news items about specific port. For any feedback ,please respond. Thank You

Re: Gsoc-Announcements distributed over the ports tree

On 20 March 2018 at 10:18, Abhishek Kashyap wrote: > Currently,on MacPort website there is news tab which consists of news about > different version of MacPorts. > So we have to add one tab under which i will contruct news items about > specific port. In all honesty our website needs a new design

Re: [macports-base] 12/18: fetch: Always use port:git for fetch.type git

Hi, - On 20 Mar, 2018, at 02:58, Ryan Schmidt ryandes...@macports.org wrote: > On Mar 18, 2018, at 19:20, Rainer Müller wrote: > >> Rainer Müller (raimue) pushed a commit to branch vcs-fetch >> in repository macports-base. >> >> >>

Re: Enhance livecheck to check not only version but also checksums

On 2018-03-20 14:29, db wrote: > On 20 Mar 2018, at 00:59, Ryan Schmidt wrote: >> Once that's done, it makes it easier to implement a better "bump" command -- >> one that can use any published checksums and compute the rest, and warn if >> no checksums were published.

Re: How to prevent fetching from macports mirrors

On 20 Mar 2018, at 14:40, Joshua Root wrote: > host_blacklist, preferred_hosts > How do you blacklist MP mirrors? Like so: host_blacklist *.packages.macports.org ?

Re: Enhance livecheck to check not only version but also checksums

On 20 March 2018 at 00:59, Ryan Schmidt wrote: > It's been pointed out before than when updating a port to a new version, one > should not just update the version and checksums in the portfile; one should > also verify at least one of those checksums with the ones published by the > developers

Re: Gsoc-Announcements distributed over the ports tree

On 20 March 2018 at 15:10, Abhishek Kashyap wrote: > Will i also have to implement implement Port Unit Testing Functionality ? > If yes Where we have to add the file. Tests are of course an important part of developing new features. We have them under macports-base/tests and they are run on

Re: Gsoc-Announcements distributed over the ports tree

Will i also have to implement implement Port Unit Testing Functionality ? If yes Where we have to add the file. On 20 March 2018 at 16:21, Mojca Miklavec wrote: > On 20 March 2018 at 10:18, Abhishek Kashyap wrote: > > Currently,on MacPort website there is news tab which

Re: How to prevent fetching from macports mirrors

On 20 March 2018 at 03:37, Ryan Schmidt wrote: > On Mar 19, 2018, at 11:31, Mojca Miklavec wrote: > >> MacPorts sometimes spends 30 seconds trying to fetch files from >> https://distfiles.macports.org or some other mirror server when I >> *know* the files are not there (when writing a new port or

Re: Enhance livecheck to check not only version but also checksums

On 20 Mar 2018, at 14:54, Rainer Müller wrote: > https://lists.macports.org/pipermail/macports-announce/ > https://github.com/macports/macports-base/blob/master/ChangeLog macports-announce seems scant to me. I suggest using a GitHub issue, like Linuxbrew does,

Wine (was Re: Request for assistance closing some old pull requests)

On Mon, 19 Mar 2018 11:44:48 -0400 "Perry E. Metzger" wrote: > > 1: wine*: add 64-bit support >https://github.com/macports/macports-ports/pull/442 >Apr 22, 2017 (yes, almost a year old) There seems to be a consensus that the 64 bit stuff _should_ be committed for

protobuf-cpp (was Re: Request for assistance closing some old pull requests)

On Mon, 19 Mar 2018 21:46:54 -0500 Ryan Schmidt wrote: > > 2: mosh: Switch to protobuf3-cpp > > https://github.com/macports/macports-ports/pull/690 > > Aug 17, 2017 > > > > Zero King correctly notes in the course of the PR's comment thread > > that protobuf3-cpp

Re: Wine (was Re: Request for assistance closing some old pull requests)

On Tue, 20 Mar 2018 11:59:01 -0400 "Perry E. Metzger" wrote: > On Mon, 19 Mar 2018 11:44:48 -0400 "Perry E. Metzger" > wrote: > > > > 1: wine*: add 64-bit support > >https://github.com/macports/macports-ports/pull/442 > >Apr 22, 2017 (yes,

Re: Python default version

On Mar 20, 2018, at 03:48, Mojca Miklavec wrote: > On 19 March 2018 at 16:52, Ryan Schmidt wrote: >> >> I should clarify that there's nothing special in my proposal about Python >> 3.6. I'm merely proposing that when we use Python, we should now prefer to >> use the latest stable version of

Re: How we announce MacPorts changes (was: Re: Enhance livecheck to check not only version but also checksums)

On Mar 20, 2018, at 09:20, db wrote: > On 20 Mar 2018, at 14:54, Rainer Müller wrote: >> https://lists.macports.org/pipermail/macports-announce/ >> https://github.com/macports/macports-base/blob/master/ChangeLog > > macports-announce seems scant to me. Intentionally. We only post there when we

Re: Gsoc-Announcements distributed over the ports tree

To be honest, I wasn't aware of this GSoC proposal until the emails started showing up on this list recently, so I don't really understand it yet. The entry on the wiki is vague. Could someone give some examples of the types of announcements we're envisioning publishing via this system? We

Re: Enhance livecheck to check not only version but also checksums

On Mar 20, 2018, at 09:26, Mojca Miklavec wrote: > On 20 March 2018 at 00:59, Ryan Schmidt wrote: >> It's been pointed out before than when updating a port to a new version, one >> should not just update the version and checksums in the portfile; one should >> also verify at least one of those

Re: How to prevent fetching from macports mirrors

On Mar 20, 2018, at 11:39, Rainer Müller wrote: > If MaxCDN does not have any cached state for the file, which obviously > will be the case for new versions, it will first have to check the > origin mirror. Files that exist are cached by the CDN for a long time, but "file not found" and other

Re: How to prevent fetching from macports mirrors

On Mar 20, 2018, at 09:21, db wrote: > On 20 Mar 2018, at 14:40, Joshua Root wrote: >> host_blacklist, preferred_hosts >> > > How do you blacklist MP mirrors? Like so: host_blacklist > *.packages.macports.org ? I don't

Re: Python default version

On Tue, 20 Mar 2018 13:43:59 -0500 Ryan Schmidt wrote: > Right, I'm proposing changing our unwritten policy regarding which > Python we want to use by default. Our current policy isn't written > in documentation but is implied by the behavior of the python-1.0 >

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On 2018-03-21 00:02, Rainer Müller wrote: > diff --git a/x11/wine/Portfile b/x11/wine/Portfile index > 9a08944..539688e 100644 --- a/x11/wine/Portfile +++ > b/x11/wine/Portfile @@ -239,7 +239,12 @@ compiler.blacklist-append > macports-gcc-* > if {[variant_isset universal]} { > # wine for

Re: How to prevent fetching from macports mirrors

On Mar 20, 2018, at 09:17, Mojca Miklavec wrote: > On 20 March 2018 at 03:37, Ryan Schmidt wrote: >> It should take well under a second for it to respond with a 404. I don't >> know why it would take anywhere close to 30 seconds for that. > > I don't know that either. Server overload maybe? :)

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On Mar 20, 2018, at 19:14, Kenneth F. Cunningham wrote: > On 2018-03-20, at 6:11 PM, Ryan Schmidt wrote: > >> There is no timetable for this yet, but it's certainly months from now. > > Really? I was really hoping it would be two or three weeks, at most. Too > bad. > > Is there anything I

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On 2018-03-21 01:09, Ryan Schmidt wrote: > Generally, do not use compiler.whitelist. Use compiler.blacklist instead, and > if all compilers are then blacklisted, add a suitable alternative to > compiler.fallback. Thanks! Setting compiler.fallback was exactly what I needed. Builds succeeded for

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

> On Mar 20, 2018, at 18:57, Rainer Müller wrote: > > On 2018-03-21 00:02, Rainer Müller wrote: >> diff --git a/x11/wine/Portfile b/x11/wine/Portfile >> index 9a08944..539688e 100644 >> --- a/x11/wine/Portfile >> +++ b/x11/wine/Portfile >> @@ -239,7 +239,12 @@ compiler.blacklist-append

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On Mar 20, 2018, at 19:07, Kenneth F. Cunningham wrote: > On 2018-03-20, at 5:57 PM, Rainer Müller wrote: >> Do we have any better way to specify the need for clang >= 3.8? >> >> If there is no way, we should probably just disable the 64-bit build of wine >> for macOS <= 10.8. > > We are just

Re: How to prevent fetching from macports mirrors

On Mar 20, 2018, at 08:30, db wrote: > On 20 Mar 2018, at 03:34, Ryan Schmidt wrote: >> On Mar 19, 2018, at 16:29, db wrote: >>> Is there any way to set in macports.conf to only fetch from master site >>> and/or, if needed, try a mirror? >> What do you mean? MacPorts already tries to fetch from

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On Mar 20, 2018, at 18:02, Rainer Müller wrote: > Rainer Müller (raimue) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/8cf7ff0fd3ed1b560101d40dd8a568926b5a5af6 > > The following commit(s) were added to

Re: Enhance livecheck to check not only version but also checksums

On 21 March 2018 at 00:13, Ryan Schmidt wrote: > On Mar 20, 2018, at 09:26, Mojca Miklavec wrote: > >> Do you also want to support signatures then? >> Public keys are pretty long though, but they usually don't change. >> >> One example: https://waf.io > > I have given no thought to the question of

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On 2018-03-20, at 5:57 PM, Rainer Müller wrote: > Do we have any better way to specify the need for clang >= 3.8? > > If there is no way, we should probably just disable the 64-bit build of wine > for macOS <= 10.8. We are just about to have all these systems (10.6 to 10.8) build everything

Re: [macports-ports] branch master updated: wine ports: Blacklist macports-clang-* fallbacks

On 2018-03-20, at 5:57 PM, Rainer Müller wrote: >> -compiler.blacklist-append {clang < 800} >> +compiler.blacklist-append {clang < 800} \ >> +macports-clang-3.3 \ >> +macports-clang-3.4 \ >> +

Re: Gsoc-Announcements distributed over the ports tree

On 20 March 2018 at 18:06, Abhishek Kashyap wrote: > hello everyone > > I want the file(s) that contain configuration changes required for this > proposals. > Please guide me. I don't understand. Mojca

Re: protobuf-cpp (was Re: Request for assistance closing some old pull requests)

On 20 March 2018 at 16:56, Perry E. Metzger wrote: > On Mon, 19 Mar 2018 21:46:54 -0500 Ryan Schmidt wrote: >> >> I would prefer that the bug that protobuf-cpp and protobuf3-cpp >> install to the same place is fixed first: >> >> https://trac.macports.org/ticket/56102 >> >> Then there's no reason

Re: Gsoc-Announcements distributed over the ports tree

hello everyone I want the file(s) that contain configuration changes required for this proposals. Please guide me. Thank You On 20 March 2018 at 19:52, Mojca Miklavec wrote: > On 20 March 2018 at 15:10, Abhishek Kashyap wrote: > > Will i also have to implement implement

Re: How to prevent fetching from macports mirrors

On 2018-03-20 15:17, Mojca Miklavec wrote: > On 20 March 2018 at 03:37, Ryan Schmidt wrote: >> On Mar 19, 2018, at 11:31, Mojca Miklavec wrote: >> >>> MacPorts sometimes spends 30 seconds trying to fetch files from >>> https://distfiles.macports.org or some other mirror server when I >>> *know*