Re: gmake and trace mode

On Feb 1, 2019, at 20:04, Joshua Root wrote: > On 2019-2-2 12:59 , Ryan Schmidt wrote: >> >> On Feb 1, 2019, at 19:53, Joshua Root wrote: >> >>> It only works when using default settings -- cmake-1.1 allows using >>> ninja in which case this wo

Re: OSX10.7 buildbot build failed due to 'no space left on device'

On Feb 2, 2019, at 04:58, Christopher Jones wrote: > I am seeing a build failure on OSX10.7 that looks like an issue with the > buildbot. > > /opt/local/var/macports/build/_opt_bbl

Re: [macports-ports] branch master updated: nrpe, nsca: remove outdated ports

On Feb 2, 2019, at 10:35, Marcus Calhoun-Lopez wrote: > Personally, I am hesitant to delete unmaintained ports as long as the > upstream project is alive. Even if a port has no upstream anymore, that alone is not a reason to delete the port, in my opinion. Somebody at some point took the eff

Re: Google Summer Of Code

On Feb 27, 2019, at 17:07, Mojca Miklavec wrote: > > Now it's really time to: > - Put a short news with a logotype on at least https://www.macports.org > (Ryan?) I don't think I was involved in that before; I don't know what we've done before. I would ask that someone else do it.

Re: Buildbot issues

On Mar 14, 2019, at 14:12, Chris Jones wrote: > Hi, > > Is there an issue with the buildbots ? I am seeing a lot of update failures, > such as > > https://build.macports.org/builders/ports-10.9_x86_64-watcher/builds/22908/steps/selfupdate/logs/stdio > > https://build.macports.org/builders/j

Re: Buildbot issues

On Mar 14, 2019, at 15:42, Ryan Schmidt wrote: > On Mar 14, 2019, at 14:12, Chris Jones wrote: > >> Hi, >> >> Is there an issue with the buildbots ? I am seeing a lot of update failures, >> such as >> >> https://build.macports.org/builders/po

Re: Buildbot issues

On Mar 14, 2019, at 16:50, Ryan Schmidt wrote: > On Mar 14, 2019, at 15:42, Ryan Schmidt wrote: > >> On Mar 14, 2019, at 14:12, Chris Jones wrote: >> >>> Hi, >>> >>> Is there an issue with the buildbots ? I am seeing a lot of update >>>

Re: How to check for generic python variant?

> On Mar 17, 2019, at 11:42, Ruben Di Battista wrote: > > To be clear, what I would like to achieve is: > > If {[variant_isset python{27,35,36,37}]} > Do something > > I’m not a ninja with TCL, so I’m asking what is the right way of doing this. > Do I need to have an if condition for each

Re: Buildbot 10.6_x86_64 Xcode Issues

On Mar 22, 2019, at 13:55, David Evans wrote: > Some builds are failing on ports-10.6_x86_64_legacy-builder due to apparent > Xcode installation issues. > > In my case (gtk3): > > DEBUG: Sourcing PortGroup compiler_blacklist_versions 1.0 from > /opt/bblocal/var/buildworker/ports/build/ports

Re: Buildbot failures on 10.11

On Mar 22, 2019, at 18:38, Chris Jones wrote: > I am seeing an odd build failure on the 10.11 builder. > > https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/98142/steps/install-port/logs/stdio > > I have tested the port in question on a 10.11 VM I have and it builds

Re: Buildbot failures on 10.11

On Mar 23, 2019, at 04:37, Christopher Jones wrote: >> The log says: >> >> >> xcrun: warning: cache file >> '/var/folders/b3/_c47r31s23q0mgj1jvy64bkwgp/T/xcrun_db' appears to be >> corrupted (21, 2090430, 327680); resetting it >> cache: 0x10217d000 >> .magic: XR1L >> .

Re: fake azure pipeline failures

On Mar 23, 2019, at 04:45, Christopher Jones wrote: > Also, it makes no sense the travis builds timeout - The build should not take > anything close to 50mins - and again these builds seem to offer no > explanation in any log I can find as to why they timeout, i.e. what’s > exactly where th

Re: Unsubscribe me from this list

The lists are self-service. You subscribe and unsubscribe yourself at https://lists.macports.org But I have unsubscribed you now. -Ryan

Re: how to deal with large data files

On Mar 27, 2019, at 19:38, Mark Anderson wrote: > > It’s an optional port? I think marking it non-distributible the the way to go > for now, but we should think about adding a “mirror no” “force_remote” or > something that is more semantic. The distributability of a binary is separate from the

Re: how to deal with large data files

On Mar 27, 2019, at 23:12, Joshua Root wrote: > As a port, even if it's not mirrored, it's still going to be taking up > gigabytes per OS version on the builders I would indeed want to avoid keeping it installed on the buildbot workers; see https://trac.macports.org/ticket/57464 > and in th

Re: Disc space low on darwin 12 and 14 builders

On Mar 30, 2019, at 12:07, Chris Jones wrote: > Could someone clear out a bit the osx 10.8 and 10.10 builder discs ? I am > seeing a number of failures on these due to disc space issues. 10.7 is also > probably low... I've cleaned up a little bit, but it's going to continue to be a problem u

Re: Dependencies on non-default variants

On Mar 25, 2019, at 01:56, Mojca Miklavec wrote: > would prefer if he or she would perhaps spend time adding novel > functionality, which could even be allowing user comments on each port > (which you could use to explain why the port appears to be broken) The ability to add comments on web pa

Re: Dependencies on non-default variants

On Mar 25, 2019, at 08:48, Craig Treleaven wrote: > On Mar 24, 2019, at 4:05 PM, Mojca Miklavec wrote: > >> I now checked the first two random MythTV ports, which basically boils down >> to: >> >> require_active_variants qt5-mysql-plugin mariadb55 >> require_active_variants p${perl5.major}-d

Re: Mail delivery of macports-changes disabled for Gmail users

This happened again yesterday. > On Feb 25, 2019, at 13:53, Rainer Müller wrote: > > Hello, > > if you are using Gmail or a Google hosted mail service for your domain, > your subscription to the macports-changes mailing list was likely > disabled on 2019-02-22 by mailman due to "excessive or fa

Re: force specific Qt5 version install?

On Apr 4, 2019, at 16:03, Michael Dickens wrote: > On my build computers, I have OSX 10.5 PPC and Intel 10.6 through 10.14; I'm > still working on 10.4 PPC and 10.5 Intel (I don't think I have the partition > space for 10.4 Intel, even if I wanted to install it, which I'm not sure I > do). I

Re: force specific Qt5 version install?

On Apr 5, 2019, at 14:30, Michael Dickens wrote: > Thank you, Ryan, for that info. I'll have to poke at the Qt5 PortGroup more & > see what it says about OSX 10.12 and 10.13 since that's where my current > issues are. > > A quick followup from yesterday for this issue on OSX 10.13: I was sur

FYI: Buildbot workers are offline for a few hours

I've taken the buildbot workers offline as a precaution due to thunderstorms. I'll start them back up later today. \r

Re: FYI: Buildbot workers are offline for a few hours

On Apr 7, 2019, at 08:57, Ryan Schmidt wrote: > I've taken the buildbot workers offline as a precaution due to thunderstorms. Back online now. \r

Re: Use ISO 8601 dates in Portfile comments

On Apr 7, 2019, at 13:25, Christopher Chavez wrote: > Currently, comments in Portfiles containing dates, such as for when remove > something in the future, are specified in whichever scheme preferred by the > port maintainer or whoever inserted the date. Some of these schemes are > region-sp

Re: [off-topic] remove app association from file extension

On Apr 19, 2019, at 16:25, Helmut K. C. Tessarek wrote: > I want macOS to let me choose the app every time I double click on an > .md file. I don't think macOS has this capability built-in. I just created a new file with an unusual extension. I opened it in the Finder and it said there's no

Re: mirrors.shu.edu.cn Down?

On Apr 28, 2019, at 05:59, Ruben Di Battista wrote: > `Error: Failed to fetch py37-resumable-urlretrieve: Failed to connect to > mirrors.shu.edu.cn port 443: Connection refused` I agree, the server isn't responding to https requests or pings. I've reported the problem to the server's administra

Re: mirrors.shu.edu.cn Down?

On Apr 28, 2019, at 07:33, Ruben Di Battista wrote: > Here it is the log. Thanks for the fast answer... > > :debug:fetch Fetching distfile failed: The requested URL returned error: 404 > Not Found > :notice:fetch ---> Attempting to fetch resumable-urlretrieve-0.1.6.tar.gz > from > http://jog.

Re: mirrors.shu.edu.cn Down?

On Apr 28, 2019, at 07:57, Ruben Di Battista wrote: > I’m sorry, the port is a port I’m writing to comply to a recent PR I’m trying > to get done (for the port py-pew). I generally redact the username in my > logs. Don’t know if it’s effectively a good practice. I’m sorry if made your > effor

Re: Blackist mirrors.shu.edu.cn from CI?

On May 10, 2019, at 17:58, Clemens Lang wrote: > >> On Fri, May 10, 2019 at 06:49:56PM +0200, Ruben Di Battista wrote: >> That mirror is making some of the builds fail because it is >> unreachable. Inability to reach or resolve any one mirror will not cause a build to fail. MacPorts will try oth

Re: PRs

On May 19, 2019, at 18:14, Mark Anderson wrote: > > Using our own buildbot servers would be pretty cool, where are they hosted? > And they go pretty far back, don't they. The buildbot servers are at my house. I currently have 4 Xserves running VMware ESXi. One is the buildmaster and the othe

Re: Advice for Boost CMake scripts

On May 19, 2019, at 10:13, Michael Dickens wrote: > I'm looking for advice on how to move forward with Boost 1.70.0's CMake find > scripts: do we just not install them? Or do we patch them via what upstream > has already done? Or do we just wait for 1.70.1 -- which will contain those > fixes

Re: URGENT -- massive merge commit on macports/macports-ports

On May 23, 2019, at 03:13, Chris Jones wrote: > On 22/05/2019 10:41 pm, Jann Röder wrote: >> On 22/05/2019 at 22:37 Joshua Root wrote: >>> >>> Discussion on IRC indicates it was done from the GitHub web UI. >>> >> The github app. I don't think you can even rebase in that. > > If that is inde

Re: Packaging buildbot-www

On May 28, 2019, at 02:11, Rajdeep Bharati wrote: > I am packaging buildbot 2.x as a port. That's great, thanks. I would suggest updating (and where applicable renaming) the existing buildbot ports. I would not make new "buildbot2" ports, since buildbot 2.x is not different from buildbot 1.x

Re: Packaging buildbot-www

On May 29, 2019, at 06:21, Rajdeep Bharati wrote: > On Wed, May 29, 2019 at 1:12 AM Rainer Müller wrote: > >> Out of curiosity, where does this screenshot come from? > > It's present in the UI: https://nine.buildbot.net/#/about >> To me it looks like all of these (minified) JavaScript libra

Re: `port select python` and qtwebengine

On Jun 2, 2019, at 10:03, René J.V. Bertinwrote: > I just learned that the QtWebEngine build process has a hard dependency on > python 2 and cannot be configured to use a specific python interpreter > exclusively. In other words, it fails if a user apparently used `port select > python` to m

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

On May 31, 2019, at 17:27, Rajdeep Bharati wrote: > On Sat, Jun 1, 2019 at 2:01 AM Mojca Miklavec wrote: > >> What does >> port installed '*buildbot*' >> say? > > It's giving None of the specified ports are installed. It should show you all ports that are installed whose names contain th

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

On May 29, 2019, at 13:29, Mojca Miklavec wrote: > As an intermezzo I want to explain one thing. Initially we had one single job > (which could run for days), and it built all the ports in a single job. > However one could not infer any information about what worked and what failed > without

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

On Jun 2, 2019, at 11:30, Rajdeep Bharati wrote: > One thing is that when I install the new py37-buildbot, the command that I > get to use is `buildbot-3.7`. > What changes do I need to make in the port to use the command `buildbot`? As Rainer explained in https://github.com/macports/macport

Re: `port select python` and qtwebengine

On Jun 2, 2019, at 12:06, Joshua Root wrote: > On 2019-6-3 01:59 , Ryan Schmidt wrote: >> As a side note, as I understand it, it is a user error to make "python" a >> symlink to Python 3; it should always be Python 2. Going forward, use a >> "python2"

Re: `port select python` and qtwebengine

On Jun 3, 2019, at 04:20, René J.V. Bertin wrote: > > Would it be possible (and acceptable) to prevent the kind of build failure > we're talking about here by setting up a temporary symlink to a sanctioned > python interpreter in a build-specific tmp directory and prepend that > directory to

Re: GSOC 2019 project: Improvements of Buildbot views (@ MacPorts)

On Jun 3, 2019, at 15:51, Mojca Miklavec wrote: > > On Sun, 2 Jun 2019 at 18:46, Ryan Schmidt wrote: > >> Buildbot is a program that we want to use for its own sake, so its port name >> should not begin with "py-" and it should be in a primary category that &

Re: upt-macports project update and feedback request

On Jun 5, 2019, at 21:36, Karan Sheth wrote: > 1. The naming convention of Python ports > For upt to be able to process dependencies correctly and add missing packages > recursively, it is important to have a consistent naming scheme for ports. > Currently, that is not completely the case, al

Re: upt-macports project update and feedback request

On Jun 6, 2019, at 21:11, Renee Otten wrote: > Looking at your comments I must admit I am a little confused, but that is > probably because I am not understanding some (basic) MacPorts things > correctly… For example, I didn’t realize (probably never tried) that “port > info py-sphinx” and "por

Re: openssl source install with trace mode bugged

On Jun 6, 2019, at 17:23, Rainer Müller wrote: > On 03.06.19 15:50, Mihir Luthra wrote: >> I noticed that on a “new" MacPorts installation, if we try to install >> openssl with flags -st, it will fail. >> >> Problematic lines in main.log with debug on are :- >> >> :info:configure darwintrac

Re: Peculiar perl version issue

On Jun 12, 2019, at 10:26, Bruce Miller wrote: > [This is motivated by the LaTeXML port, > but is a general question about perl portgroup] > > A colleague suggested the clever shebang line > #!/usr/bin/env perl > as a way to easily allow testing against different > versions of perl, running i

Re: Peculiar perl version issue

On Jun 12, 2019, at 13:41, Bruce R Miller wrote: > On 6/12/19 1:14 PM, Ryan Schmidt wrote: >> On Jun 12, 2019, at 10:26, Bruce Miller wrote: >> >>> So, apparently the perl portgroup replaces shebang >>> lines that it recognizes with a call to the specific &

Re: Xcode INSTALL_PATH and framework paths

On Jun 13, 2019, at 02:01, Aaron Madlon-Kay wrote: > I am working on a portfile for Sequel Pro (https://sequelpro.com/) and > am reaching the limits of my understanding of the Xcode build system. > > Sequel Pro contains several framework subprojects, which get built > along with the main target.

Re: Xcode INSTALL_PATH and framework paths

On Jun 13, 2019, at 09:37, Aaron Madlon-Kay wrote: > Now I have another issue: after installation the port is flagged as broken > with the following message. > >> sequelpro-devel is using libstdc++ (this installation is configured to use >> libc++) > > As I understand it, the reason is that

Re: Suggestion to slightly simplify pypi ports

On Jun 23, 2019, at 02:52, Mojca Miklavec wrote: > I would like to suggest providing simplification for the following four lines: > > namepy-foo > version 1.2.3 > master_sitespypi:[string index ${python.rootname} > 0]/${python.rootname} > distname

Re: Deprecating support for ports

On Jun 23, 2019, at 16:42, Adam Mercer wrote: > I work as part of the LIGO project and for a while now we've used > MacPorts to provide support for our collaboration members running our > software under macOS. For various reasons we are in the process of > switching over to Conda as this allows

Re: Suggestion to slightly simplify pypi ports

On Jun 23, 2019, at 05:02, Mojca Miklavec wrote: > I guess this then changes my question into: how could we get rid of > these two rows? > >master_sitespypi:[string index ${python.rootname} > 0]/${python.rootname} >distname${python.rootname}-${version} > > We still

Re: Docker container with MacPorts

On Jun 25, 2019, at 02:52, Mojca Miklavec wrote: > And I ended up with a totally stupid error: > > $ port info > Error: Current platform "linux 4" does not match expected platform "linux 5" > Error: If you upgraded your OS, please follow the migration > instructions: https://trac.macports.org/

Re: macOS 10.15 Read Only root

On Jun 29, 2019, at 19:53, Mark Anderson wrote: > Do we have any plans with how to deal with 10.15 not allowing us to create > /opt if it doesn’t exist? Or does /opt just come with the file system? I > can’t remember. macOS does not come with an /opt directory. I was not aware that macOS Catal

Re: flang port

On Jul 8, 2019, at 14:37, Jack Howarth wrote: >Since the legacy header support for avoiding the availability attribute > has been dropped from the 10.15 SDK... > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835 > > and it is unclear when and if the missing availability attribute supp

Re: Setting up port builds on Azure using master branch of macports

On Aug 1, 2019, at 10:50, Blair Zajac wrote: > On Aug 1, 2019, at 2:01 AM, Mojca Miklavec wrote: > >> Is anyone willing to set up one Azure build instance running macports >> master when building the ports? >> >> This could help us spot any potential issues with our code in the >> master bran

Re: build failure - odd compiler selection

On Aug 5, 2019, at 14:02, Christopher Jones wrote: > OK, I’ve worked out what was going on. > > The problem is the port uses the cxx11 port group, which internally sets the > whitelist to include *only* macports-clang-5.0. This is then used instead of > the fallback list below to pick a compile

Re: 10.7 buildbot disk space issues

On Aug 12, 2019, at 09:56, Chris Jones wrote: > Hi, > > Looks like the 10.7 bot is low on disc space again.. > > > > cheers Chris As you can see from the cleanup step's output,

Re: Is the buildbots filesystem case-sensitive?

On Aug 14, 2019, at 13:04, Ruben Di Battista wrote: > I’m hitting strange file not found errors on the paraview build on the > buildbots, but not locally nor on Azure; so I was wondering: do they run on a > case sensitive filesystem? Yes. P.S: Please make sure you write to our new list add

Re: 10.7 buildbot disk space issues

On Aug 14, 2019, at 08:28, Christopher Jones wrote: >> As you can see from the cleanup step's output, there was 21GiB of space >> available when the build failed. >> >> https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/108375/steps/cleanup/logs/stdio >> >> How much

Re: Retiring ports.php

On Aug 15, 2019, at 09:06, Mojca Miklavec wrote: > On Thu, 15 Aug 2019 at 15:27, Joshua Root wrote: >> >> I think ports.macports.org is already clearly superior to ports.php, so >> we should change the Available Ports link to point there. However, we >> should not remove ports.php so as not to

Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

On Aug 18, 2019, at 03:56, Dmitri Zaitsev wrote: > 3. What kind of build error is that and how to deal with it? Rust does not build on an OS X version as old as you are using. Software developers frequently remove support for older operating systems from their projects, on the assumption tha

Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

On Aug 19, 2019, at 05:22, Chris Jones wrote: >> It could be that switching to the latest compiler would help. You can >> try building with >> sudo port -v build rust configure.compiler=macports-clang-7.0 >> or something like that (I'm not 100% sure if the command is exactly >> right as I'm

Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

On Aug 20, 2019, at 02:19, Dmitri Zaitsev wrote: > Just trying to understand it better, does it mean when I attempted to access > those file, their mirroring had been initiated but it took many hours before > the completion? Is it documented somewhere? When a change to a port is committed, o

Re: Preparing for 2.6.0 beta

On Aug 23, 2019, at 22:45, Joshua Root wrote: > I think we're pretty close to being ready to make a new stable branch > and tag a beta. Clemens is going to make one more change related to > Xcode checking; are there any other changes that really need to go in > before the beta? It would be nic

Re: Preparing for 2.6.0 beta

On Aug 24, 2019, at 08:55, Joshua Root wrote: > On 2019-8-24 21:59 , Mojca Miklavec wrote: > >> I would be grateful for addressing these: >> >> https://trac.macports.org/ticket/50448 > > Way too late to do anything about that in base. The plan is as described > in comment 16. I didn't reali

Re: 10.6.8 i386 buildbot offline

On Sep 7, 2019, at 09:17, Ken Cunningham wrote: > just a heads-up that this buildbot appears to have been offline a couple of > days now Thanks for letting me know. I've fixed it.

Re: https://build.macports.org/ down ?

I was also having trouble accessing it. The "kernel_task" and "master" processes were using over 50% CPU each, which didn't seem normal. So I restarted the server. Seems ok now. (Where "slow" must unfortunately be classified as "ok".) -Ryan > On Sep 15, 2019, at 07:44, Chris Jones wrote: > >

Re: scope of configure.optflags, configure.compiler etc. command line variables

On Sep 12, 2019, at 03:46, René J.V. Bertin wrote: > I hope I didn't ask this before: > > Is there a way to let command line options like the ones in the subject apply > to all ports on the command line, instead of only to the one given just > before of the option in question? I would guess

Re: [guide] 5.3 missing keywords

On Aug 31, 2019, at 07:31, Bjarne D Mathiesen wrote: > A description of the "build.dir" & "configure.dir" keywords are missing > > I only discovered these keywords by accident by looking in a Portfile > for help with exactly these issues : changing into a directory before a > python install >

Re: libraw updates because fetch gives 404

On Aug 26, 2019, at 04:25, Christopher Jones wrote: > On 26 Aug 2019, at 8:49 am, Riccardo Mottola wrote: > >> Hi, >> >> since yesterday I am trying to update... but... >> >> Is something wrong with our mirrors? > > The mirrors themselves seem fine. Just looks like the 0.19.5 update dist fi

Re: Port variants for deps

On Sep 15, 2019, at 22:31, Eric F (iEFdev) wrote: > What would be better (ie good “portiqette”)… Adding subports (keeping the > variants), or replacing variants with subports? Provide only one way for a user to install a feature. Convert variants to subports, if appropriate. Usually if a va

Re: scope of configure.optflags, configure.compiler etc. command line variables

I don't want to discuss this at great length, but I'll answer these questions: On Sep 16, 2019, at 02:22, René J.V. Bertin wrote: > On Sunday September 15 2019 20:25:59 Ryan Schmidt wrote: > >> Setting such options on the command line is intended as a debugging >

Re: scope of configure.optflags, configure.compiler etc. command line variables

On Sep 17, 2019, at 03:08, René J.V. Bertin wrote: > I continue to think that compiler choice and options should be something the > user can set the default for, without having to replace the standard system > compiler drivers (/usr/bin/clang{,++}) with wrapper scripts. As you know, we don't

Re: Port variants for deps

On Sep 16, 2019, at 17:01, Eric F (iEFdev) wrote: > On 9/16/19 23:20 , Ryan Schmidt wrote: >> On Sep 15, 2019, at 22:31, Eric F (iEFdev) wrote: >> >>> What would be better (ie good “portiquette”)… Adding subports (keeping the >>> variants), or

Re: scope of configure.optflags, configure.compiler etc. command line variables

On Sep 17, 2019, at 03:26, René J.V. Bertin wrote: > On Monday September 16 2019 16:26:12 Ryan Schmidt wrote: > >> There should be no need for you to specify anything ccache-related on the >> command line. You can enable ccache globally in macports.conf. Individual >&

Re: Preparing for 2.6.0 beta

On Aug 24, 2019, at 23:20, Joshua Root wrote: > On 2019-8-25 03:00 , Mojca Miklavec wrote: >> Would it be possible to set up at least one builder with 10.6 running >> MacPorts master, building all ports with libc++ (apparently default by >> now in master), just not uploading the archives to the

Re: Preparing for 2.6.0 beta

On Aug 24, 2019, at 12:00, Mojca Miklavec wrote: > Independent from the stdlibc++ vs. libc++ question I still believe > that it would be really nice to be able to easily include/exclude the > set of macOS versions. Say that we organize the meeting with very poor > internet connectivity (which i

Re: Preparing for 2.6.0 beta

On Sep 19, 2019, at 20:45, Joshua Root wrote: > On 2019-9-20 11:38 , Ryan Schmidt wrote: >> >> >> On Aug 24, 2019, at 23:20, Joshua Root wrote: >> >>> On 2019-8-25 03:00 , Mojca Miklavec wrote: >>>> Would it be possible to set up at least on

Re: Preparing for 2.6.0 beta

On Sep 19, 2019, at 21:22, Mojca Miklavec wrote: > On Fri, 20 Sep 2019 at 03:38, Ryan Schmidt wrote: >> >> >> >> On Aug 24, 2019, at 23:20, Joshua Root wrote: >> >>> On 2019-8-25 03:00 , Mojca Miklavec wrote: >>>> Would it be pos

Re: scope of configure.optflags, configure.compiler etc. command line variables

On Sep 20, 2019, at 02:23, René J.V. Bertin wrote: >> Storing a separate cache for each port would quickly eat up a lot of disk >> space. > > Evidently, but > - ccache doesn't use more space than needed > - the ccache directory compresses extremely well with afsctool, a background > cleanup

Re: RFC: MacPorts policy should be that docs should not be built or installed by default

On Sep 19, 2019, at 23:40, Ken Cunningham wrote: > the documentation that comes along with many ports often seems like a heavy > and arguably needless burden: > I vote we expect ports to not include anything but a few man pages. > Everything else should be either left out, or an optional var

Re: Publishing links to non-encrypted websites for MacPorts downloads

On Sep 25, 2019, at 00:43, Mojca Miklavec wrote: > I already mentioned this in the past, but I would like to repeat. > When someone opens our homepage and wants to download MacPorts using > Safari on, say, 10.6, the download link from GitHub doesn't work, and > it's not trivial for users to fin

Re: Publishing links to non-encrypted websites for MacPorts downloads

On Sep 26, 2019, at 00:04, Mojca Miklavec wrote: > On Thu, 26 Sep 2019 at 06:26, Ryan Schmidt wrote: > >> On Sep 25, 2019, at 00:43, Mojca Miklavec wrote: >> >>> I already mentioned this in the past, but I would like to repeat. >>> When someone open

Re: 2.6.0 features

On Oct 5, 2019, at 07:14, Joshua Root wrote: > It has now been the customary 2 weeks since the release of MacPorts > 2.6.0, so the new features can be freely used in portfiles. In particular: > > * New compiler selection options. You can specify required C or C++ > standard versions, and/or sp

Re: 2.6.0 features

On Oct 5, 2019, at 08:37, Ken Cunningham wrote: > I have come across several ports where variant c++ standards are needed, like > gnu++11 for example, so perhaps setting the std automatically could lead to > troubles... Yeah. I had assumed that the MacPorts base feature had been implemented

Re: implementation of configure.env-append

On Oct 6, 2019, at 14:05, Ken Cunningham wrote: > I think I have tried this enough ways to be close, but I just want to be > certain. > > I want to *append* a value onto an existing environment variable from a > Portfile. I don’t want to overwrite what is there in the environment variable >

Re: CatalinaProblems added

On Oct 8, 2019, at 06:10, MacPorts Wiki wrote: > Page "CatalinaProblems" was added by jmroot > Content: > Ensure you have Xcode 11.0 or greater installed and selected (e.g. `sudo > xcode-select -s /Applications/Xcode.app/Contents/Developer`), and that you > have the command line tools instal

Re: Upgrade cctools unexpectedly failing

On Oct 8, 2019, at 10:34, Chris Jones wrote: > On 08/10/2019 6:52 am, Ken Cunningham wrote: >>> I wonder if the SDK path is >>> baked into llvm-config-mp-7.0? >> Yep -- sheesh. Is there no end to this? >> Ken >> $ llvm-config-mp-7.0 --cflags >> -I/opt/universalnew/libexec/llvm-7.0/include -pipe -O

Re: Upgrade cctools unexpectedly failing

On Oct 8, 2019, at 20:44, Joshua Root wrote: > On 2019-10-9 02:48 , Ryan Schmidt wrote: >> If we used the "MacOSX.sdk" (instead of the versioned one) the fact that it >> gets baked into things wouldn't be a problem*. We should do this, but it >> will

Re: CatalinaProblems added

On Oct 8, 2019, at 20:22, Joshua Root wrote: > On 2019-10-9 02:34 , Ryan Schmidt wrote: >> >> >> On Oct 8, 2019, at 06:10, MacPorts Wiki wrote: >> >>> Page "CatalinaProblems" was added by jmroot >>> Content: >> >>> En

Re: implementation of configure.env-append

On Oct 9, 2019, at 12:04, Ken Cunningham wrote: > On Tue, Oct 8, 2019 at 1:59 AM Ryan Schmidt wrote: > >> No... it's the other way around... >> >> If you want to modify LDFLAGS, do so by modifying configure.ldflags. >> MacPorts will set the LDFLAGS e

Re: implementation of configure.env-append

On Oct 9, 2019, at 10:57, Ken Cunningham wrote: > On Tue, Oct 8, 2019 at 9:25 AM Blair Zajac wrote: > >> Maybe the MacPorts could raise an error if one attempts to set a variable >> like LDFLAGS outside of configure.* ? Yes, MacPorts could do that. I don't think anybody's tried to write code

Re: Lazarus port

On Oct 11, 2019, at 09:13, Karl-Michael Schindler wrote: > Hi. > > I am working on the Portfile for Lazarus, an integrated IDE for FreePascal > similar to Delphi. Besides some smaller issues, which I am sure I can > address, a major issue shows up that was suggested to present here for > di

Re: Perl module Privileges::Drop Portfile Fails to Build on Azure

On Oct 12, 2019, at 10:20, Steven Smith wrote: > I see that the build is trying to download CPAN stuff Add the needed dependencies so that that does not happen.

Re: pymol crashing under Qt on Catalina

On Oct 16, 2019, at 17:36, Jack Howarth wrote: > > ps Do the binary servers retain the older versions of the python27 packages? > I am tempted to walk back through them and see if I can find a version that > still works. I recently ran a cleanup script that deleted most of the old archives. Her

Re: 10.15 builder

On Oct 17, 2019, at 08:07, Jack Howarth wrote: >I noticed that https://build.macports.org/builders doesn't show a 10.15 > builder yet. Is there a schedule for when one will become available? I have not started setting up a Catalina build worker yet. I may need to archive the recently-ret

Re: Index Broken on 10.5

On Oct 19, 2019, at 16:55, Fred Wright wrote: >> That's probably not actually the index being broken, but a circular >> dependency. See . >> >> The issue causing the circular dependency is that all the system >> compilers are blacklisted by whatever port

Re: replacing OpenGL with MoltenVK

On Oct 21, 2019, at 12:19, Jack Howarth wrote: > > Are there any plans for using the MoltenVK package in MacPorts as a > replacement for the macOS OpenGL support that is slated for depreciation? I haven't heard of any such plans.

How to handle ports that are still broken because of the icu upgrade

icu was recently updated to a new major version. As a result its install_name changed and anything that links with it needs to be rebuilt against the new version. All ports that declare a dependency on icu already had their revisions increased for this reason. So if you are encountering a port

Re: How to handle ports that are still broken because of the icu upgrade

On Oct 23, 2019, at 08:56, Daniel J. Luke wrote: > On Oct 22, 2019, at 9:49 PM, Ryan Schmidt wrote: >> Or does the port use libxml2? If so, it may be using a bad method of finding >> libxml2. One bad method of finding libxml2 is using the xml2-config script. > > Should w

<    1   2   3   4   5   6   7   8   9   10   >