Re: port versus path dependency declaration

On May 11, 2018, at 21:57, Renee Otten wrote: > I am trying to understand why in some Python ports the run dependencies are > declared using path instead of port statements - is there an > advantage/preference for one over the other? > > For example, in the py-spyder-devel Portfile (but also

Re: port versus path dependency declaration

On May 11, 2018, at 22:17, Ryan Schmidt wrote: > As for why a dependency on pep8 is being written in path:-style, I don't > know. I don't see a py-pep8-devel port. I don't know if there is another port > that provides the same files as py-pep8. I should have checked the history before

port versus path dependency declaration

I am trying to understand why in some Python ports the run dependencies are declared using path instead of port statements - is there an advantage/preference for one over the other? For example, in the py-spyder-devel Portfile (but also the py-autopep8, which I recently updated) it uses:

Re: [macports-ports] 01/02: py-diff-match-patch: new port, version 20121119

On Fri, May 11, 2018 at 12:07:38PM -0500, Ryan Schmidt wrote: On May 10, 2018, at 20:37, Zero King wrote: Zero King (l2dy) pushed a commit to branch master in repository macports-ports. https://github.com/macports/macports-ports/commit/5836a5624ac40d04cb12a73c4ef219c377100a16 commit

Re: [macports-ports] 01/02: py-diff-match-patch: new port, version 20121119

On May 11, 2018, at 18:34, Zero King wrote: > On Fri, May 11, 2018 at 12:07:38PM -0500, Ryan Schmidt wrote: >> >> On May 10, 2018, at 20:37, Zero King wrote: >> >>> Zero King (l2dy) pushed a commit to branch master >>> in repository macports-ports. >>> >>> >>>

Re: Gsoc 18 Project | Collect build statistics

On 2018-05-11 09:17, Mojca Miklavec wrote: >> I got the rough idea of the db from here: >> https://github.com/macports/macports-infrastructure/blob/2129f0cd0eb80f207d2cc62542b65c197733ac51/jobs/PortIndex2PGSQL.tcl#L249 > > Sure, you can take this as inspiration for database design, but not as >

Re: Qt5 port group

I believe this is possible. However, as Ken pointed out in a previous email, we have two models we could follow: 1) The gtk3 +quarts vs gtk3 +x11 model (Almost) every dependent port of gtk3 has quartz and x11 variants consistent with whatever gtk3 was installed with. I *think* this

Re: Qt5 port group

>> On May 9, 2018, at 5:00 PM, Craig Treleaven wrote: >> >>> On May 9, 2018, at 2:07 PM, Ryan Schmidt wrote: >>> >>> >>> On May 9, 2018, at 07:18, Craig Treleaven wrote: >>> On May 8, 2018, at 5:06 AM, Vincent Habchi wrote: >

Re: Qt5 port group

Sorry to chime in back so late, I had several hiccups with my mail lately, and most (if not all) of your messages simply remained in transit until today. As far as I have experimented, a single version of Qt is allowed to be installed. Fair enough. I’ve rewritten the Qgis3 port introducing a

Re: Gsoc 18 Project | Collect build statistics

On 11 May 2018 at 04:00, Vishnu wrote: > Hi > > Also i wanted to know > For this link > https://www.macports.org/ports.php?by=name=python27 > > There is already existing database with loads of information. > Is it not updated? > is it static ? It is not static, the database is updated via an

Re: missing dejavusansmono in rrdtool pango cairo fontconfig - new insights

On May 10, 2018, at 20:00, macpo...@parvis.nl wrote: > - So I propose to change the enforced backend in cairo from quartz to > fontconfig. How would that be accomplished? I thought the quartz variant was only supposed to add optional functionality to cairo. I turned the variant on

Re: [macports-ports] 01/02: py-diff-match-patch: new port, version 20121119

On May 10, 2018, at 20:37, Zero King wrote: > Zero King (l2dy) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/5836a5624ac40d04cb12a73c4ef219c377100a16 > > commit 5836a5624ac40d04cb12a73c4ef219c377100a16 > > Author:

Re: Qt5 port group

On May 10, 2018, at 19:44, Marcus Calhoun-Lopez wrote: > On May 9, 2018, at 11:07 AM, Ryan Schmidt wrote: > >> My understanding of the fact that they conflict is that there is some latest >> version of Qt that is compatible with each version of macOS, and that by >> using the qt5 portgroup,

Re: [macports-ports] 06/06: py-rpy2: update to version 2.9.3

On May 10, 2018, at 07:49, Andrew Stromnov wrote: > Andrew Stromnov (stromnov) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/ee6a6268d651d4e42247b4f466c51599647a3228 > > commit ee6a6268d651d4e42247b4f466c51599647a3228