Skip to content

Conversation

@trustbyte
Copy link
Contributor

@trustbyte trustbyte commented Nov 8, 2025

Description

Type(s)
  • bugfix
  • enhancement
  • security fix
Tested on

macOS 26.1 25B78 arm64
Command Line Tools 26.1.0.0.1.1761104275

Verification

Have you

  • followed our Commit Message Guidelines?
  • squashed and minimized your commits?
  • checked that there aren't other open pull requests for the same change?
  • referenced existing tickets on Trac with full URL in commit message?
  • checked your Portfile with port lint?
  • tried existing tests with sudo port test?
  • tried a full install with sudo port -vst install?
  • tested basic functionality of all binary files?
  • checked that the Portfile's most important variants haven't been broken?
@macportsbot
Copy link

Notifying maintainers:
@JacksonIsaac for port duck.

@trustbyte
Copy link
Contributor Author

How to check the rev-upgrade part on this new release?

@reneeotten
Copy link
Contributor

How to check the rev-upgrade part on this new release?

what do you mean by "check the rev-upgrade part". If there is a rev-upgrade after you install something it likely means that there was a change in library name somewhere and a dependent is now broken. That's typically just solved by increasing the revision of the dependent. You shouldn't see this when just updating a port...

@trustbyte
Copy link
Contributor Author

Sorry, I should have mentioned that there is a comment inside the file that has something added that should be checked at upgrade..
rev-upgrade is mentioned.

@barracuda156
Copy link
Contributor

This port should be built from source, but install an opaque pre-built stuff, there is no justification for that.

@trustbyte
Copy link
Contributor Author

Okey, is it this, right? https://github.com/iterate-ch/cyberduck
Building with mvn/ant? Oh boy, oh boy. Let's see how it goes.

Draft.

@trustbyte trustbyte marked this pull request as draft November 15, 2025 20:36
@trustbyte
Copy link
Contributor Author

Any ideas how to fix DerivedData?
I tried quite a few, none worked on my machine..

@barracuda156
Copy link
Contributor

@trustbyte If I had a working portfile, I would have just referred to it. I didn’t try building this yet, since it uses Java, and on powerpc that would be tricky, if possible at all (we only got headless JDK atm). I also got no experience with Java builds on x86.

build.cmd xcodebuild
build {
set env(HOME) ${workpath}
set env(DEVELOPER_DIR) /Applications/Xcode.app/Contents/Developer
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This holds only for some macOS versions. I don’t think it should be hardcoded in the portfile, you can pick the value from macports.conf.

set env(DEVELOPER_DIR) /Applications/Xcode.app/Contents/Developer

system -W ${worksrcpath} \
"/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This path also gonna be wrong, when developer_dir is elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

5 participants