Re: Additional labels for pull requests (and Trac tickets)

ed the author to submit a bug report and want him/her to at least provide a link to the bug report. - Or we are in fact waiting for upstream to do something. But I would nevertheless use the same tag for both. I like your analysis and proposal in general. > On 11/11/2017 02:35 PM, Mojca Mi

Re: Additional labels for pull requests (and Trac tickets)

While going through PRs today, I discovered another group with a significant number of open PRs that might deserve its own tag. Someone submits a patch with a perfectly functional port and then gets feedback like "please change the commit message format", "please squash commits / rebase / avoid me

Re: [macports-ports] branch master updated: sift: new port, replacement for 'grep' built in go

On 12 November 2017 at 21:52, Ryan Schmidt wrote: > On Nov 11, 2017, at 15:15, Emre Şafak wrote: >> Mojca Miklavec (mojca) pushed a commit to branch master >> in repository macports-ports. >> >> +homepagehttp://sift-tool.org > > Since the http UR

Re: [macports-ports] 02/02: gtk3: update to version 3.22.26

On 15 November 2017 at 08:13, Eitan Adler wrote: > Hi, > > It seems that gtk3 has been broken for me since this commit or thereabouts. See https://trac.macports.org/ticket/55275 I uploaded a super simple patch that might work for you, but this needs to be double-checked and committed (disclaimer:

Re: Additional labels for pull requests (and Trac tickets)

ith no references. I would like the author to either reference an existing bug/commit or submit a new one if one doesn't exist. On 11 November 2017 at 23:20, Mojca Miklavec wrote: > On 11 November 2017 at 21:36, Jeremy Lavergne wrote: >> Perhaps we can give these all a common prefix sinc

Re: maintaining packages in macports vs. in a language package manager

On 17 November 2017 at 07:11, Joshua Root wrote: > On 2017-11-17 13:15 , Perry E. Metzger wrote: >> I'm slowly cleaning up the OCaml ports. >> >> One of the things of note is that these days (and this wasn't true a >> couple of years ago), OCaml encourages the use of the "opam" package >> manager,

Re: What is the best way to access binaries outside of the standard MacPort path

Dear Joël, On 21 November 2017 at 13:41, Joël Brogniart wrote: > > I updated the patch at and asked for > a review twice in the developer list. As english is not my main language, I'm > not sure if I've done something incorrectly or if everyone is too bus

MacPorts Meeting 2018

Hi, Back in 2016 we had a really great developer meeting in Gozd Martuljek (Kranjska Gora, Slovenia). The number of attendants was relatively small, but this made the meeting even more intensive and successful. One of the "products" of the meeting was the current buildbot setup for example. We wo

Re: Possible bug in comparing architectures?

Hi, On 5 December 2017 at 21:53, Davide Liessi wrote: > Dear developers, > in the log [1] I read > > Error: Cannot install py27-poppler-qt5 for the arch 'powerpc' because > Error: its dependency python27 does not build for the required arch by default > Error: and the configured universal_archs 'i

Too many compilers needed for C++11

Hi, I just tried adding a cxx11 1.1 PortGroup to a port. It first failed because clang-3.9 was missing. Once clang-3.9 was installed, the port tried to install: - llvm 3.7 - clang-4.0 - clang-5.0 Are there really so many compilers needed for one single C++11 piece of software? https://build

Re: Too many compilers needed for C++11

On 6 December 2017 at 15:20, db wrote: > On 6 Dec 2017, at 00:46, Ken Cunningham wrote: >> clang/llvm 5.0 is the current cxx11 1.1 compiler, so that is what is being >> called up. > > Shouldn't such portgroup dependencies be listed by `port rdeps`? I don't see > it, for example, in highlight. Wh

Re: Too many compilers needed for C++11

On 7 December 2017 at 10:28, Joshua Root wrote: > On 2017-12-7 17:39 , Ryan Schmidt wrote: >> >> On Dec 7, 2017, at 00:37, Joshua Root wrote: >> >>> On 2017-12-7 17:29 , Ryan Schmidt wrote: (I don't know why MacPorts base considers this a warning, rather than an immediate-exit error.) >>>

Re: MacPorts Meeting 2018

Hi, On 8 December 2017 at 15:08, Rainer Müller wrote: > Thank you for taking the initiative again! Thanks a lot for "pre-registering". We are now at 6 + 2 participants so far (that is: two people from overseas who would be interested, but might not make it) and I expect a few more. So far it lo

Creating test cases

Hi, Does anyone have any examples for writing test cases from scratch? For a packaged compiler (mingw) I would like to test compilation of a few source files which are not part of any built-in test suite. Is the only reasonable way to create a patch file and modify the Makefile? Or are there slig

Re: MacPorts Meeting 2018

ansportation is basically non-existant. But we'll keep searching around. Based on responses we would be aiming at March, probably the second half, so we need to hurry up with decisions anyway. Mojca On 5 December 2017 at 14:41, Mojca Miklavec wrote: > Hi, > > Back in 2016 we had a real

Re: Addressing Port submission failures on Travis

On 20 December 2017 at 09:04, Ken Cunningham wrote: > keep the master branch up to date, but leave your PR branch alone until it's > merged, then delete the branch. Indeed, that's the correct advice. You only ever need one single fork of macports-ports, but make sure to always keep the master bra

Re: Question about meson and boost libraries

On 22 December 2017 at 19:14, Benjamin Redelings wrote: > Hi, > > I'm new to macports. I'm the author or the bali-phy software, and I'm > working on updating the ancient Portfile for it. The software has changed a > lot since someone wrote the original Portfile years ago, and I was > complete

Re: Question about meson and boost libraries

On 24 December 2017 at 21:02, Ryan Schmidt wrote: > On Dec 22, 2017, at 18:10, Benjamin Redelings wrote: > >> However, even after that fix I have to define BOOST_ROOT=/opt/local to find >> boost. For manual builds, if don't do PATH=/opt/local:$PATH then meson uses >> pkgconfig from homebrew and

Re: use_autogen

On 23 December 2017 at 16:38, Ryan Schmidt wrote: > Should we add a "use_autogen" (or "use_autogen_sh") option to MacPorts base? What about use_bootstrap.sh? (This is one I would need at the moment, but it's only used in 9 other ports rather than 200.) I support the idea except that the list coul

Re: Fix Sierra Trac query

Hi, Just my two cents. I would be in favour of changing the strings from cat names to numbers, but of course this would only make sense if this was done properly, automatically for all tickets. I'm sure that there's a way to make such mass-edits, potentially while disabling email notifications fo

Re: [macports-ports] 01/02: meson-1.0: new PortGroup

31. dec. 2017 8:52 AM "Ryan Schmidt" wrote: > +# Meson's install_name currently seems to be broken, so workarounds might be needed to make ports actually work. > +# See: https://github.com/mesonbuild/meson/issues/2121 Yeah something is going to have to get fixed there. I don't understand why the

Re: travis builds time out -- then keep restarting ???

On 2 January 2018 at 23:28, Jan Stary wrote: > On Jan 02 22:20:25, rai...@macports.org wrote: >> On 01/02/2018 11:13 AM, Jan Stary wrote: >> >> > It is still happening, see e.g. >> > https://github.com/macports/macports-ports/pull/1186 >> >> This looks like a normal timeout. >> The build finished a

Re: MacPorts Meeting 2018

Hi, It's time to set the final date for the MacPorts meeting 2018. Given the initial poll results + some individual emails we are now constrained to any time between Saturday the 10th and Tuesday the 20th of March 2018. Those who want to come, please reply ASAP in case one option does not suit you

GSOC 2018 org application period has begun

Hi, The GSOC 2018 application period for organisations is now open, deadline for applying in January 23rd. I hope we are going to participate this year as well? If so, it would be about time to come up with additional ideas and clean up the ideas page. Mojca

Re: MacPorts Meeting 2018

250 EUR, but more information to follow. Mojca On 8 January 2018 at 00:11, Mojca Miklavec wrote: > Hi, > > It's time to set the final date for the MacPorts meeting 2018. Given > the initial poll results + some individual emails we are now > constrained to any time between S

Redistributable binaries for 10.5 or 10.6 from C++11 sources

Hi. I would like to build and distribute some poppler-based command-line utilities (I would compile them with compiler from MacPorts, but distribute it to users with MacPorts). I could use either gcc or clang, but what are the options to make that work for 10.5/10.6? Can libc++ or libstdc++ be li

Re: Redistributable binaries for 10.5 or 10.6 from C++11 sources

PC is likely to be mission impossible, so I'll need to find a proper PPC, but let's see if I can get it working natively to start with. Thank you, Mojca > Ken > > On Jan 12, 2018, at 11:15 PM, Mojca Miklavec wrote: > > Hi. > > I would like to build and dist

Re: Query on Participating in Gsoc 2018

Dear Ankit, Which operating systems are you working on / have regular access to? It's indeed still too early, but in case MacPorts is selected ... Given the set of languages that you are familiar with it could make sense to work on our buildbot setup for example. We would need to migrate to Buil

Re: GSoC 2018 Collect Build Statistics Project

On 14 February 2018 at 11:30, Umesh Singla wrote: > Hi Ayush > > On Wed, Feb 14, 2018 at 12:56 PM, Mojca Miklavec wrote: >> >> Dear Ayush, >> >> Can you please write to the macports-devel mailing list instead? We >> would like to avoid private discussi

Any spare mac hardware (for MacPorts meeting) lying around?

Hi, >From 10th to 14th March we'll be meeting at the 2nd MacPorts Meeting in Slovenia. https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018 During the last meeting we borrowed two older Mac Pros (box format, pretty old, but with quite some cores and speed) which we used for heavily testin

Buildbot 1.0

Hi, Are there any thoughts about migration to buildbot 1.0 (from Ryan in particular)? I wanted to seize the opportunity of some hacking during the MacPorts meeting next month to potentially migrate to buildbot version one, but there is one quite severe drawback, and that's the display of waterfal

Re: Buildbot 1.0

On 20 February 2018 at 04:49, Joshua Root wrote: > On 2018-2-20 14:43 , Ryan Schmidt wrote: >> On Feb 19, 2018, at 18:14, Joshua Root wrote: >>> On 2018-2-20 10:14 , Ryan Schmidt wrote: Getting the builds to spawn in the *correct* (dependency) order is a more involved task, but we'v

Re: Buildbot 1.0

On 20 February 2018 at 00:14, Ryan Schmidt wrote: > On Feb 19, 2018, at 16:49, Mojca Miklavec wrote: > >> Are there any thoughts about migration to buildbot 1.0 (from Ryan in >> particular)? >> >> I wanted to seize the opportunity of some hacking during the Mac

Search for a MacPorts Mascot: looking for talented artists

Hi, During the GSOC meeting in Mountain View we had some fruitful evening discussions where we were heavily criticised for not having our own happy fluffy animal mascot (like a flying platypus?) which we could take to every meeting or hacking event where we show up. Something in the spirit of ...

Suggestions for hacking sessions & discussions for the MacPorts meeting in March

Hi, I have a few ideas, but I would like to gather more input about what you consider the most burning issues that might need some discussions or hacking sessions during the MacPorts meeting. We'll try to fit those on the schedule. Some of my ideas: - Options for establishing a legal entity (not

Mirorring distfiles

wrote: > Hi, > > On Wed, Feb 21, 2018 at 05:33:53PM +0100, Mojca Miklavec wrote: >> I have a few ideas, but I would like to gather more input about what >> you consider the most burning issues that might need some discussions >> or hacking sessions during the MacPorts meeting

Re: Search for a MacPorts Mascot: looking for talented artists

On 22 February 2018 at 06:45, Helmut K. C. Tessarek wrote: > Hello, > > On 2018-02-21 11:32, Mojca Miklavec wrote: >> Do we have any artists around to draw one? Any thoughts? (We could >> probably come up with some small awards.) > > I know a few graphic designers who m

Programme and talks for the MacPorts meeting

Hi, We were brainstorming about the programme for the MacPorts meeting with Aljaž. I would like to ask what talks you want to hold during the MacPorts meeting, here are some initial suggestions: - Zero & Umesh: each one presenting the work done during the GSOC 2017 + challenged faced, how we cou

Re: GSOC

Please do not talk to mentor directly. Use this mailing list to ask questions. Mojca 25. feb. 2018 20:17 je oseba "Abhishek Kasyap" napisala: I Does not able to contact mentor for discussing the proposals.I have sent mail to pixilla but dont get any response.Please help.

Ports with default modeline & lots of mixed tabs with spaces

Hi, I sometimes stumble across ports which contain our default modeline (claiming the Portfile should not use tabs) and then a weird mixture of tabs and spaces all over the place. When there is no maintainer, I would always fix such a port. I once did it for a maintained port as well, just to see

Re: [macports-ports] branch master updated: cpan2port: fetch from github, use perl5.26

On 28 February 2018 at 16:23, Ryan Schmidt wrote: > On Feb 28, 2018, at 08:13, Mojca Miklavec wrote: > >> +set git_shasum 4207b22 >> +set git_date20180228 >> + >> +github.setupmacports macports-contrib ${git_shasum} > > I'd like to

Re: [macports-ports] branch master updated: cpan2port: fetch from github, use perl5.26

Fixes committed, thanks. On 28 February 2018 at 16:43, Mojca Miklavec wrote: > On 28 February 2018 at 16:23, Ryan Schmidt wrote: >> On Feb 28, 2018, at 08:13, Mojca Miklavec wrote: >> >>> -# TODO: check the latest svn revision of the file >>> +# TODO: chec

Re: [macports-ports] branch master updated: libcaer: new port

On 1 March 2018 at 15:03, Ryan Schmidt wrote: > > On Mar 1, 2018, at 07:59, Perry E. Metzger wrote: >> On Thu, 1 Mar 2018 07:48:35 -0600 Ryan Schmidt wrote: +depends_lib-append port:libusb >>> >>> The port failed to build without pkgconfig. >> >> Should the CI infrastructure have noticed that

sizeof(long) and universal builds

Hi, While checking some patches of a library I decided to try whether the library would build universally. The configure.ac part contains: AC_COMPILE_CHECK_SIZEOF([long]) and that happily fails with checking size of long... configure: error: cannot determine a size for long when settin

Re: GSOC 2018

On 1 March 2018 at 21:17, Abhishek Kasyap wrote: > Can i select more than one idea in this organisation. You can submit an arbitrary proposal. You can combine several ideas that need less work or write a completely different proposal for writing something that's not even listed (once you are famil

Re: GSOC 2018

On 1 March 2018 at 21:56, Umesh Singla wrote: > Hi > > You are welcome to select multiple ideas provided you're able to communicate > about it with mentors and propose on time. Only the best one proposal will > be selected. I must strongly disagree here. OK, sure, the student *could* prepare mul

Re: [macports-ports] branch master updated: libcaer: new port

On 1 March 2018 at 20:23, Perry E. Metzger wrote: > On Thu, 1 Mar 2018 08:40:51 -0800 Ken Cunningham wrote: >> CI is not sufficient testing to commit, sadly. >> >> There is no xcode 9 in travis at present. >> misses many things, like liscence etc >> doesn't check if destrooting is right >> >> It's

Re: sizeof(long) and universal builds

that could allow compiling just once. Mojca > On Thu, Mar 1, 2018, at 2:40 PM, Mojca Miklavec wrote: >> While checking some patches of a library I decided to try whether the >> library would build universally. The configure.ac part contains: >> >> AC_COMPILE_CHECK_SIZEO

Re: Mirorring distfiles

On 22 February 2018 at 21:14, Ryan Schmidt wrote: > On Feb 22, 2018, at 04:57, Mojca Miklavec wrote: > >> Dear Ryan, >> >> What is the current situaton with mirorring distfiles > > Unchanged. I need to create a buildworker on the buildmaster. I then need to >

Re: [macports-ports] branch master updated: libcaer: new port

On 2 March 2018 at 01:41, Perry E. Metzger wrote: > On Thu, 1 Mar 2018 22:25:47 +0100 Mojca Miklavec wrote: >> > Maybe we need more flexible (and less likely to time out) CI than >> > Travis can give us that includes things like port lint, traced >> > builds, etc? &g

Re: sizeof(long) and universal builds

On 2 March 2018 at 07:15, Joshua Root wrote: > On 2018-3-2 08:27 , Mojca Miklavec wrote: >> On 1 March 2018 at 20:42, Michael Dickens wrote: >>> In the past, I've handled this situation by using the muniversal PortGroup, >>> so that the sizeof is correct for eac

Re: [macports-ports] branch master updated: libcaer: new port

On 2 March 2018 at 11:26, Ryan Schmidt wrote: > > On Mar 1, 2018, at 22:14, Perry E. Metzger wrote: > > > > Well, sure, but the host environment makes a bit of a difference for > > the technical effort. For example, this means we can't (for example) > > simply spin up a cluster in AWS at will. Perh

Re: Mirorring distfiles

On 2 March 2018 at 15:02, Ryan Schmidt wrote: > On Mar 1, 2018, at 16:09, Mojca Miklavec wrote: > >> Yes. I still find it super painful that we did not manage to migrate >> to libc++ over all those years due to a basically "trivial" issue. >> >> My sugges

Re: Port submission for aidadoc

Dear Bernard, On 5 March 2018 at 12:06, Bernard Desgraupes wrote: > Hi, > > I have submitted, three weeks ago, a new port via a submission ticket > (https://trac.macports.org/ticket/55808) but it doesn't seem to have received > any attention. > It concerns the aidadoc project (see > https://sou

Re: Port submission for aidadoc

On 6 March 2018 at 09:10, Bernard Desgraupes wrote: > Dear Mojca, > > I have made the recommended fixes and have just been attaching the modified > Portfile (added as Portfile.2). > This is Ticket #55808: https://trac.macports.org/ticket/55808 Thanks, but for some reason I'm unable to download t

Re: Port submission for aidadoc

On 6 March 2018 at 10:47, Joshua Root wrote: > On 2018-3-6 20:23 , Bernard Desgraupes wrote: >> So, if I understand correctly, writing: >> use_autoreconfyes >> >> would enough to replace the following: >> pre-configure { >> system -W ${build.dir} autoheader >> } >> use_autoconfy

Re: request for port create command, to build a portfile from a URL

Hi, On 6 March 2018 at 15:58, Ken Cunningham wrote: > It would be nice to have a command like > > port create URL > > that would download the URL, calc the checksums for it, and build a basic > Portfile for it. > > It could ask for a category to use for the Port. > > In a more advance version, it

Buildbot idea(s) for GSOC

Dear Umesh, In case we would get any good students in that area, I would be grateful if someone would work on improving buildbot core & front-end in close collaboration with mentors directly from buildbot. I added this one idea on the list, but it needs some polishing: https://trac.macports.o

Re: [macports-ports] branch master updated: rpcgen-mt: new port

8. mar. 2018 6:55 PM je oseba "Ryan Schmidt" napisala: > +fetch.type svn > +depends_fetch-append\ > +port:subversion Because of this issue? https://trac.macports.org/ticket/55933 I don't think so. I probably forgot that fetch.type takes care of dependencies. Fee

Buildbot discussion

Dear Ryan, Here are Rainer's notes about today's buildbot discussion and plans for the meeting: https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018/Buildbot We would need your help with: - debugging why emails from the buildbot don't reach maintainers / committers - deploying the alre

Re: Buildbot proposal: combine portwatcher and portbuilder

Dear Ryan, Conceptually I like the approach a lot. *However*, this will generate an incomprehensible amount of emails when a new build slave gets added or when some revbumps are done etc. In particular from the 10.5/ppc machine. The individual emails will be a lot more helpful, but the amount of

Re: a plea to change the default std lib clang adds if none is specified on the build line

On 12 March 2018 at 00:08, Kenneth F. Cunningham wrote: > 1 minute summary, no gobbledygook: > > When clang sees a build line, if there is no -stdlib=Something specified, it > adds -stdlib=libstdc++ on systems up to 10.8, and -stdlib=libc++ on 10.9 and > above. > > If the older OS is set up to us

MacPorts Meeting 2018 notes

Hi, As most of you already know, the most dedicated MacPorts developers are currently spending some productive time in Slovenia. For those who might be interested, mostly Clemens and Rainer are making some excellent notes on the fly. You can find them here: https://trac.macports.org/wiki/Meet

Re: Changing default cxx_stdlib to libc++

On 12 March 2018 at 22:32, Michael wrote: > On 2018-03-08, at 9:32 AM, Ken Cunningham wrote: > >> Thank God. >> >> 10.6.8, agree. > > So PPC machines will not get this upgrade? PPC and libc++ don't particularly like each other. But we could and should switch to making gcc 6 or 7 the default compil

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

On 13 March 2018 at 05:07, Ryan Schmidt wrote: > On Mar 12, 2018, at 21:46, Mojca Miklavec wrote: > >>> Shall we backport these PRs to our buildbot 0.8.12 port? >>> >>> Add context field to GitHubStatus updates >>> https://github.com/buildbot/buildbot/pull

Re: Buildbot proposal: combine portwatcher and portbuilder

Dear Ryan, Please take a look at the discussion summary we just had at the meeting: https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018/BuildbotRestructuring Regarding emails: we figured out that it makes no sense to make our design decisions based on how annoying it would be to write em

Re: [macports-infrastructure] 02/02: buildbot: Update status on GitHub after each build

On 13 March 2018 at 16:15, Ryan Schmidt wrote: > On Mar 13, 2018, at 07:50, Rainer Müller wrote: >> On 2018-03-13 13:27, Ryan Schmidt wrote: >>> On Mar 13, 2018, at 02:43, Mojca Miklavec wrote: >>>> On 13 March 2018 at 05:07, Ryan Schmidt wrote: >>>>>

Re: Changing default cxx_stdlib to libc++

On 14 March 2018 at 00:12, db wrote: > On 13 Mar 2018, at 17:10, Mojca Miklavec > wrote: >> The main problem is that Travis is *not* out main build system, we use >> a different system for that. Travis has lots of limitations: > > Got it. Then why use it in the f

Build hardware resources

Ryan, On 15 March 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 funds to pay for anything. >> >> If

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

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

MacPorts from behind proxy servers & fetching the file directly

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: Relax port lint rule for patchfile naming

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

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 dist

Location of GSOC 2011 statistics code?

Hi, I'm unable to find a copy of https://trac.macports.org/browser/branches/gsoc11-statistics/stats-server in our GitHub repository. There is https://github.com/macports/macports-base/tree/gsoc11-statistics but it only contains one folder (base) out of three. Documentation and stats-serve

Re: understanding macports

Hi, On 17 March 2018 at 15:26, Abhishek Kashyap wrote: > hi > I want to know how to add items to port tree. What items do you mean? > How to install multiple properties lists? What lists are you referring to? Mojca

Re: understanding macports

Dear Abhishek, I spent 30 minutes writing a reply to you, then I noticed that you sent me a private email. As per our GSOC policy, we are not answering private emails. Mojca On 17 March 2018 at 15:39, Mojca Miklavec wrote: > On 17 March 2018 at 15:26, Abhishek Kashyap wrote: >> hi >

Re: understanding macports

On 17 March 2018 at 16:08, Abhishek Kashyap wrote: > News items as mentioned in GSOC and plists So: - https://trac.macports.org/wiki/SummerOfCode#news - https://trac.macports.org/wiki/SummerOfCode#startupitem ? The source code is in https://github.com/macports/macports-base/ There is one vide

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

On 16 March 2018 at 17:42, Rainer Müller wrote: > On 2018-03-16 12:31, Mojca Miklavec wrote: > >> Umesh was only able to work on MacPorts because he was at home during summer. > > That sounds really drastic, but I do not think it is in reality. There > are the alternatives

Re: How to fetch and extract patches in archives?

On 18 March 2018 at 08:33, Zero King wrote: > Hi, > > Port w3m needs patches from Debian to fix security issues. Currently, > the patches are added to the ports tree and takes ~800KiB. Since its > size will grow, I'd prefer to fetch the patches from Debian archives > (e.g. w3m_0.5.3-36.debian.tar.x

Re: Gsoc

On 18 March 2018 at 07:17, Abhishek Kashyap wrote: > hi > i am working on Announcements distributed over the ports tree ¶ Great, this would be a nice-to-have feature. > This is template of newsitem to be added to port tree. > > If anyone wants changes please specify it and give feedback.This refe

Re: understanding macports

On 18 March 2018 at 06:49, Abhishek Kashyap wrote: > hey > i want to confirm that I have to add news items to contents of port or > anywhere else. > Please specify explicitly where we have to add. I guess that the most sensible place would be to put the news under macports-ports/resources/news. T

Handling trac tickets, and submissions in particular

Dear Perry, You are doing an amazing job at keeping the pull request number down to a negligible number compared to the number of submitted requests. Do you have any suggestion how to effectively tackle 409 trac tickets with port submissions? Click "Port submissions" on https://trac.macports

dlopen() and (non-support in) MacPorts

Hi, I'm maintaining the dvisvgm port which links against libgs and works with ghostscript as expected. But I also compile that binary as a standalone one, as part of TeX Live (maybe MacTeX rings a bell, even though I'm not the one providing MacTeX itself). That binary uses dlopen() to find libgs

Suggestions for improvements of portindex2json

Dear Joshua, I would like to suggest making some improvements to portindex2json 1. Use a list for categories Change "categories" : "aqua devel", into "categories" : ["aqua", "devel"], 2. Improve representation of variants At the moment it is a plain list: "variants" : "python27 qt4

Re: Python default version

On 12 March 2018 at 15:46, Ryan Schmidt wrote: > The python portgroup defaults to version 2.7, and in ports that have python > variants, I've used that version by default as well. > > I was reminded by the members of the MacPorts meeting that it has been > announced that python 2's end-of-life wi

Re: Request for assistance closing some old pull requests

On 19 March 2018 at 16:44, 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) > > This PR seems to be stuck on the fact that Wine de facto needs a 64 > bit version to be useful in a modern cont

How to prevent fetching from macports mirrors

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 updating an existing one). How can I quickly prevent fetching from a large number of mirrors? Thank you,

Re: Request for assistance closing some old pull requests

On 19 March 2018 at 19:29, Rainer Müller wrote: > > Unfortunately, we have no support to run builds from pull requests or > custom branches on the buildbot, as it would immediately publish the > resulting archives. > > This sounds like a nice enhancement for our buildbot, though. On a > forced buil

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 Pyth

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. >> >> >> https://github.com/macports/macp

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: 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 (wh

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: 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: 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 wh

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: 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

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

On 21 March 2018 at 14:26, Rainer Müller wrote: > On 2018-03-20 12:42, Rainer Müller wrote: >>> netpbm is the most complicated one, tweaking the arguments and commands in >>> order to first check out a sparse working copy and then to update only the >>> two directories we want. I do intend to swi

Getting libc++ for 10.5

Hi, This might be a rhetorical question, but let me ask just in case. I want to build some 32-bit C++11 software on 10.6 with -isysroot /Developer/SDKs/MacOSX10.5.sdk (I would like to make it work on 10.5). Is there any place where I could grab libc++? I know I could bootstrap it myself if I cre

Re: Getting libc++ for 10.5

On 21 March 2018 at 15:41, Mojca Miklavec wrote: > Hi, > > This might be a rhetorical question, but let me ask just in case. > > I want to build some 32-bit C++11 software on 10.6 with -isysroot > /Developer/SDKs/MacOSX10.5.sdk (I would like to make it work on 10.5). > > Is

<    2   3   4   5   6   7   8   >