Re: The future of the Golang Portgroup ― what to do with offline builds?

I’m the author of go2port and the original author of the golang-1.0 port group. The reasons for preferring “offline” builds have been discussed ad nauseam, but the discussions that I am aware of are dispersed across Trac, GitHub, the mailing list, etc., so it would probably be a good idea to

Re: Commit Messages

Thank you for pointing this out. This has been an annoyance for me, too. I think perhaps some contributors may be unaware of the issue due to differences in tooling or perhaps just not noticing, but I thought illustrating the problem might help. If you don’t include a blank line after

macOS 13 minimum required Xcode

Hi all. I have just upgraded to macOS 13 and am attempting to migrate my MacPorts installation. When I try to install a port I get the following error: > Error: The installed version of Xcode (14.0.1) is too old to use on the > installed OS version. Version 14.1 or later is recommended on

Re: Announcement: macports.el, an Emacs porcelain for MacPorts

On Mon, May 2, 2022 at 14:53 Michele Venturi wrote: > Thanks! Did you record it with ASCII-cinema?  > I did! Then I converted it to SVG with https://github.com/marionebl/svg-term-cli -Aaron

Announcement: macports.el, an Emacs porcelain for MacPorts

Hello all. I just wanted to announce for any Emacs users that I have published an Emacs package for interacting with MacPorts. macports.el: an Emacs porcelain for MacPorts https://github.com/amake/macports.el (What is a “porcelain”? See

Re: Recent OpenSSL changes and CA certs

enssl11 | grep cert.pem > Oberon ~/Projects/MacPorts/ports > > > Chris > > On 13 Oct 2021, at 5:58 am, Aaron Madlon-Kay wrote: > > Hi all. > > I know there are some important changes being made to the OpenSSL > ports. Today I updated my ports and now have the f

Re: Recent OpenSSL changes and CA certs

Forget all that stuff I mentioned about rbenv and ruby-build. I can reproduce this with the ruby30 port: % /opt/local/bin/ruby3.0 -r net/http -e 'Net::HTTP.get(URI("https://www.apple.com;))' /opt/local/lib/ruby3.0/3.0.0/net/protocol.rb:46:in `connect_nonblock': SSL_connect returned=1 errno=0

Recent OpenSSL changes and CA certs

Hi all. I know there are some important changes being made to the OpenSSL ports. Today I updated my ports and now have the following installed: % port installed name:openssl The following ports are currently installed: openssl @1.1_0 (active) openssl10 @1.0.2u_2 (active) openssl11

Re: Should CI/buildbot report rev-upgrade errors?

On Tue, Sep 7, 2021 at 4:42 AM Eric Gallager via macports-dev wrote: > > I agree that this behavior would be helpful, however, doing so would > require keeping the results of previous builds installed, whereas I > think the current behavior is to do all builds from a fresh > environment... While

Re: emacs-app-devel build fail on master not detected by buildbot

For the general case an update to MacPorts base would be required, but for the purposes of any given port shouldn't it be sufficient to do `depends_fetch-append port:git`? And my apologies; it wasn't you, Dan, who took the position I described earlier, it was another commentator:

Re: emacs-app-devel build fail on master not detected by buildbot

> all it does is save a bit of bandwidth during the fetch In the case of Emacs, it saves *gigabytes* during fetch. The depth restriction was a lifesaver when I worked on the nativecomp variant a while back. -Aaron

Re: emacs-app-devel build fail on master not detected by buildbot

I proposed in a past PR to emacs-app-devel to use a modern git flag that lets you specify a depth based on commit date. That would be the “real” solution in the direction you’re going. However it was rejected by the maintainer because he *wants* the current setup. If the port no longer builds

Swift Package Manager

Hello all. A port I maintain, Sequel-Ace, has recently switched from including a dependency with CocoaPods (which vendors all dependency code alongside the main project in the same repo) to Swift Package Manager (which fetches at build time): https://github.com/Sequel-Ace/Sequel-Ace/pull/586

Re: Force Xcode SDK instead of CLI SDK?

On Fri, Nov 20, 2020 at 11:47 PM Joshua Root wrote: > Unfortunately it isn't really. The result of not using an SDK matching > your OS version is that autoconf (and cmake etc.) detects functions that > aren't available at runtime, causing crashes because checking for > weak-linked symbols is very

Re: Force Xcode SDK instead of CLI SDK?

> 1. Your configuration value for developer_dir in macports.conf (I'm >assuming it's the default). It's the default (commented out in macports.conf). > 2. Whether >${developer_dir}/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk >exists on your system. I take

Re: Force Xcode SDK instead of CLI SDK?

> That surprises me... > > So what's the build failure when using the CLT SDK? The summary has two errors: > The following build commands failed: > DataModelCompile > /opt/local/*snip*/work/Sequel-Ace-2.3.1/build/Release/Sequel\ > Ace.app/Contents/Resources/ >

Re: Force Xcode SDK instead of CLI SDK?

(Replying to list as well this time) > > Is there a way to force use of the Xcode SDK? > > use_xcode yes Sorry, I should have mentioned that I tried that, but the result was that it still used the CLI SDK: SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' I am on macOS 10.15.7

Force Xcode SDK instead of CLI SDK?

Hi all. I have a port (Sequel-Ace) that builds with the SDK in Xcode, e.g. /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk ...but not with the CLI SDK, e.g. /Library/Developer/CommandLineTools/SDKs/MacOSX11.0.sdk Is there a way to force use

Announcement: System fonts port tree

Hi all. In case anyone is interested in installing system fonts through MacPorts, I’ve set up an unofficial ports tree here: https://github.com/amake/macports-fonts See the readme for setup instructions. - What are “system fonts”? Simply, fonts

Re: Looking for help with kustomize port (Go)

It's common in Go to specify version strings as linker flags. Grep the ports tree like so to see existing ports that successfully set these flags. It's not uncommon to use the string 'unknown' for e.g. the git commit when it is redundant or not readily available. % grep -R -- "-ldflags '-X" .

Re: Upgrade cctools unexpectedly failing

> [-Wmissing-sysroot] > :info:build clang: warning: no such sysroot directory: > '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk' I had the same errors with poppler. I fixed it by copying the MacOSX10.14.sdk from Xcode 10 into my Xcode 11

Re: Xcode 11 & SDKROOT on macOS 10.14

> xcrun can't find cdtool on my system even without specifying an SDK: I don't know anything about it except that the error occurs when using CLT and doesn't happen when using the Xcode SDK. > The Xcode tools are another matter, and we should be setting DEVELOPER_DIR > correctly to allow them

Re: Xcode 11 & SDKROOT on macOS 10.14

> Which port? sequelpro-devel > You mean SDKROOT in the environment? I mean the SDKROOT=${configure.sdkroot} that is added to the build-phase args in the xcode-1.0 portgroup (see xcode::get_build_args). > Does that mean you're running master? I assume you're asking about my MacPorts version.

Xcode 11 & SDKROOT on macOS 10.14

Hi all. I have a port that was previously working with Xcode 10.x on macOS 10.14 but is not working with Xcode 11. I have tracked the issue down to the fact that SDKROOT is getting set to the Command Line Tools path (/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk) even when setting

Re: Dealing with unstable -devel port

I ended up bumping the epoch. -Aaron

Dealing with unstable -devel port

Hi all. I maintain the libusbmuxd-devel port that tracks the upstream master branch. I just discovered that recent versions are subtly broken, and I need to roll back to a previous version. I can handle this fine on my machine for my own purposes, but what should I do about the port? The

Re: Xcode INSTALL_PATH and framework paths

Thanks, all. I got it working and pushed the new port. -Aaron On Fri, Jun 14, 2019 at 2:17 AM Joshua Root wrote: > > On 2019-6-14 02:28 , Ryan Schmidt wrote: > > > > > > On Jun 13, 2019, at 09:37, Aaron Madlon-Kay wrote: > > > >> Now I have another issue:

Re: Xcode INSTALL_PATH and framework paths

t; On Jun 13, 2019, at 17:58, Ryan Schmidt wrote: > > 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. >> >

Xcode INSTALL_PATH and framework paths

Hi all. 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. If I build the project normally outside of MacPorts

Re: Appropriateness for inclusion in MacPorts

8 PM Rainer Müller wrote: > > On 2017-09-04 14:46, Aaron Madlon-Kay wrote: > > 1. Some OSS Java applications > > > > There are some Java applications I use that have both GUI and CLI > > components. One of them is bundled by default with a JRE. A trivial port &

Netbeans port

Hi all. I was thinking of making a Netbeans port since recent versions aren't packaged nicely for Mac. The distfile is 303MB, which would make it one of the heaviest ports I could find (looking at `size` entries). Is this too big? If so, would it be acceptable with e.g. special license

Re: GitHub post-extract shenanigans

t extracted, which should among > other things make the github portgroup shenanigans unnecessary. (See > https://github.com/macports/macports-base/pull/55) > > \r > > > > On Oct 17, 2018, at 01:22, Aaron Madlon-Kay wrote: > >> After poking around some more I t

Re: GitHub post-extract shenanigans

Aaron Madlon-Kay wrote: > > Hello all. > > The github 1.0 portgroup does some post-extract shenanigans to > normalize the result of extracting the distfile: e.g. a GitHub project > `me/myproject` will, as retrieved from GitHub, extract to > `me-myproject-0123abc`; this is mov

GitHub post-extract shenanigans

Hello all. The github 1.0 portgroup does some post-extract shenanigans to normalize the result of extracting the distfile: e.g. a GitHub project `me/myproject` will, as retrieved from GitHub, extract to `me-myproject-0123abc`; this is moved to `myproject` via globbing:

Re: Golang dependencies and glide

> As an example, look at the cargo and cargo_fetch port groups that implement dependencies for rust this way Mojca suggested essentially the same thing to me off-list. > The peco port is already using this approach and I think it is the right way to go foward. The snippets from that port should

Re: Golang dependencies and glide

Hi Mojca. Thanks for the info. > But the main question boils down to: assuming that one dependency (of > dashing, let's say) gets updated tomorrow. Will the resulting binary > still be the same if you rebuild it the day after tomorrow? In the presence of a glide.lock file, it appears the answer

Golang dependencies and glide

I have created a portfile for a tool written in golang: https://github.com/amake/macports-ports/blob/dashing/textproc/dashing/Portfile I was lazy and used glide (a golang package manager, which we have a port for) to grab the dependencies. I note that no other golang port seems to use glide;

Re: New project member: amake

Thanks, Rainer. Glad to be on board! -Aaron

Re: Java port maintainers: What should be installed on the buildbot workers?

> You had mentioned Java 9 introducing changes that were not backward > compatible. Does that only apply to the JDK, and not the JRE? Should the Java > 9 JRE be able to run stuff made with any earlier Java version? Compared to previous updates, Java 9 breaks a lot of things and no, a lot of

Re: Java port maintainers: What should be installed on the buildbot workers?

> Ok. Then my plan is to install the Apple Java 6 JDK and the Oracle Java 7, 8 > and maybe 9 JDK, and the Oracle Java 8 JRE. Does that cover all the bases for > now? The JDKs will install the JRE automatically, and since I don’t think it ever downgrades, you will end up with the Java 9 JRE

Re: Java port maintainers: What should be installed on the buildbot workers?

> Thanks, you've cleared up another misconception I had. I had read that Java 7 installations were being automatically upgraded to Java 8, so I thought there was no point to trying to install Java 7. The system-default Java will prompt for updates, but I don't think I've seen it replace an

Re: Java port maintainers: What should be installed on the buildbot workers?

> Do you think there is any value to installing Apple Java 6 first, then installing Oracle Java 8, so that both JDKs are there? I'm just thinking of ancient ports that might be hardcoded to look for the old version that used to be bundled with macOS. The order of installation doesn't really

Re: Java port maintainers: What should be installed on the buildbot workers?

> Huh. The system requirements linked from the download page say "Intel-based > Mac running Mac OS X 10.7.3 (Lion) or later.” Very interesting. I was able to install JDK 8u161 in my OS X 10.7.5 VM. Apparently Oracle has had contradictory advice about this for a long time, and they never

Re: Java port maintainers: What should be installed on the buildbot workers?

> I'm not very familiar with Java open source project best practices, but > maybe it is common practice to specify the -source and -target options > anyway, so that our choice of JDK version wouldn't matter? This is what I was talking about being “frowned upon”. Even if you specify -source and

Re: Java port maintainers: What should be installed on the buildbot workers?

> Oracle Java 7 and 8 are compatible with Lion and later. Java 8 requires Mountain Lion: http://www.oracle.com/technetwork/java/javase/certconfig-2095354.html > My understanding is that one must choose either Apple's Java 6 or Oracle's > Java 7 or 8; they can't coexist. I’m not aware of any

Appropriateness for inclusion in MacPorts

Hi all. I was wondering if there was any official guidance on what kinds of software was appropriate for inclusion in MacPorts, beyond the phrase "command-line, X11 or Aqua based open-source software” on macports.org. Specifically I have two things that seem borderline inappropriate, but that

Re: Conflicting binary in dependency

new port the dependencies are not upgraded, so the hack is required. Thanks, Aaron > On Jan 13, 2017, at 22:46, Joshua Root <j...@macports.org> wrote: > > On 2017-1-12 18:58 , Aaron Madlon-Kay wrote: >> Hi all. I was hoping to get some advice: >> >> I wan

Re: Conflicting binary in dependency

he conflict So it seems like the deactivate hack code will never be run. Thanks, Aaron > On Jan 13, 2017, at 8:52, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Jan 12, 2017, at 01:58, Aaron Madlon-Kay wrote: >> >> Hi all. I was hoping to get some advice: &g

Re: Conflicting binary in dependency

yan Schmidt <ryandes...@macports.org> wrote: > > On Jan 12, 2017, at 01:58, Aaron Madlon-Kay wrote: > > > > Hi all. I was hoping to get some advice: > > > > I want to make the sqlite3-tools package available via MacPorts > (binaries available at https://sqlite.o