BUG: Cyberduck 2.3.3 fails to build

[lmhfzuobimed@…]

Cyberduck build fails - see attached logfile

[markd@…]

Cyberduck is way out of date and broken. I think version 2.6.2 would fix the port, but for some strange reason they stopped releasing source tarballs several version ago. Hopefully they will again, but if and until then you'll have to try the binary on the cyberduck site.

[ryandesign (Ryan Carsten Schmidt)]

I tried to fix the Cyberduck port. Here's what I learned:

• A tarball for the 2.6 source code is available. Tarballs of the 2.6.1 and 2.6.2 source are not available; see this bug:

​http://trac.cyberduck.ch/ticket/934

2.6.1 and 2.6.2 source are available via the Cyberduck Subversion repository, but I did not feel like changing the port to download from Subversion, nor do I think it's a good idea to make the Cyberduck port depend on the Subversion port.

• The 2.6 source code is missing an essential file so I had to modify the port to additionally download that one file from the Cyberduck Subversion web repository browser.

• 2.6 compiles, but then seems to want to be tested by junit. I don't want to have to install junit and apache-ant just to install Cyberduck.

• Even if I make Cyberduck depend on junit and apache-ant, I get fatal errors ("junit/framework/Test (Unsupported major.minor version 49.0)"). I think this is because I have Java 1.5 installed, which presumably gets used by junit, but Cyberduck itself uses Java 1.4.2, which is incompatible.

• I am attaching a patch to the portfile to update it to 2.6.0. The only step left would be to figure out how to make it skip the junit test bit, and remove the dependency on the apache-ant and junit prots.

• I cannot understand why anyone would want to build Cyberduck through MacPorts when they could much more easily just download the disk image of the pre-compiled binary from the Cyberduck web site. It seems to me that the Cyberduck port should be deleted.

[markd@…]

Cyberduck 2.7.1 is released and source code is now available. If someone wants to update the port to that it would be fine. Otherwise, I'd agree it should be deleted.

[ryandesign (Ryan Carsten Schmidt)]

I noticed that, and simplified my patch. But I'm still left with the problem of not knowing how to tell it not to use junit to try to test the thing after it's built, since it complains and does not complete.

Note that Cyberduck now includes an easy auto-update function. It checks at launch whether a new version is available. If so, it prompts you to let you automatically download and install it and launch the new version, all with a single click. Even if we were to successfully update the port to the latest 'duck, we would always lag behind the official releases; as soon as the next official release came around, the auto-update feature would entice the user to upgrade in that manner, rather than the MacPorts way.

The MacPorts "easy" update (sudo port upgrade cyberduck) was the only advantage I could see to installing Cyberduck via MacPorts rather than from the official disk image. Now that Cyberduck has such an excellent update mechanism built-in, I can see no advantage to using MacPorts to install it. Unless anyone can suggest an advantage I'm not seeing, let's delete the port.

[ryandesign (Ryan Carsten Schmidt)]

partial fix to update the portfile to cyberduck 2.7.1

[markd@…]

This port has been deleted. For this app it is easier and better to install with a binary disk image.