new Portfile for xchataqua

[ToePeu@…]

category: aqua irc

test environment:

• osx10.6
• xcode 3.2.3

[ToePeu@…]

aqua/xchataqua/Portfile

[ToePeu@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Thanks, here is an updated Portfile with the following changes:

• whitespace changes (tabs to spaces, lined up columns)
• fixed maintainer line (unless you are a committer and have an @macports.org email address, the maintainer field needs to contain your full email address, and should be in our obfuscated format)
• removed "variant universal {}" (I think we want to let the xcode portgroup handle it)
• simplified destroot

I'm not committing it yet because it doesn't build on my Snow Leopard machine. I get these errors:

.../xchataqua-0.17-rc2-20100905/plugins/perl/perl.c:124:20: error: EXTERN.h: No such file or directory
.../xchataqua-0.17-rc2-20100905/plugins/perl/perl.c:126:18: error: perl.h: No such file or directory
.../xchataqua-0.17-rc2-20100905/plugins/perl/perl.c:127:18: error: XSUB.h: No such file or directory

and then hundreds of errors stemming from that.

There are also a couple other issues in the log I don't know what to do with, like

sed: 70: .../xchataqua-0.17-rc2-20100905/build/X-Chat Aqua.build/Localization/localesed/pa.sed: RE error: invalid character range

and

Release.xcconfig line 1: Unable to find included file "BuildNumber.xcconfig"

Full log attached.

[ryandesign (Ryan Carsten Schmidt)]

updated portfile by ryandesign

[ryandesign (Ryan Carsten Schmidt)]

build log

[ToePeu@…]

irc/xchataqua/Portfile

[ToePeu@…]

Thank you for fixing my faults!

There was a problem with leopard-perl installation

perl-plugin problem:

while installing, there is a Terminal.app popup requiring sudo password. after password and trying again, it will success. if you know something better way, please help me.

sed errors:

it is not harmful most of users. it just makes pa localization disabled.

Release.xcconfig warning:

it is not good. but it is harmless.

[ToePeu@…]

new file Portfile.3 required. (Portfile.2 dont works well)

[ryandesign (Ryan Carsten Schmidt)]

Replying to ToePeu@…:

There was a problem with leopard-perl installation

perl-plugin problem:

while installing, there is a Terminal.app popup requiring sudo password. after password and trying again, it will success. if you know something better way, please help me.

The first time I tried to install from this Portfile, it popped up a second Terminal window asking me for my password to run "sudo tar xvf "/opt/local/var/macports/build/_Users_rschmidt_macports_dports_aqua_xchataqua/work/xchataqua-0.17-rc2-20100905/contrib/systemlib/Perl-Leopard.tar" -P", but before I could type my password, the original Terminal window showed the "port install" command already failed as I reported before, and I cancelled the tar command. The second time I tried, the second Terminal window appeared and proceeded to extract the tar file without needing my password (I guess it had been less than 5 minutes since I had last given sudo my password) but the "port install" window still failed. On the third try xchataqua installed successfully. But this solution is not going to be acceptable for several reasons. It's not nice to pop up a second Terminal window, nor to make the user attempt the installation multiple times. And it's totally unacceptable for a port to install things into /System; ports should be self-contained within ${prefix} or other approved directories like ${applications_dir} and must not modify directories that are "owned" by Apple. These files were also extracted directly into /System, not into ${destroot}, so they're not registered to the port, which means they won't go away with a "port uninstall"; it's not ok to litter the user's system with files like that.

In MacPorts we like to use our own libraries, so you should be using MacPorts perl instead of the system's perl; this change alone would resolve many of the above issues.

sed errors:

it is not harmful most of users. it just makes pa localization disabled.

There appears to be some confusion in the localization files about what the correct syntax is for the SET command. Is it:

• SET <variable> [<value>]
• SET [-quiet] <variable> [<value>]
• SET [-e] [-or] [-quiet] <variable> [<value>]

SET [-e] [-offon] [-quiet] <variable> [<value>] When inserted into a sed statement, as you do, this last variant becomes invalid sed syntax (and this last variant only appears in the pa localization). "[" and "]" delimit character classes in a sed statement, so for example "[-e]" means "any single character '-' or 'e'". "[-offon]" is not a valid character class. The "-", when it does not appear at the very beginning or end of the character class, is used to indicate a range of characters. In this case, you've asked for the range of characters from "|" to "o" which doesn't work because the ASCII code for "|" (124) is higher than the ASCII code for "o" (111). Clearly in this case you don't want "[" and "]" to be delimiting character classes; you just want the literal square bracket characters to be matched, so they need to be escaped wih backslashes to turn off their special meaning. I believe the attached patch fixes this problem. You should then fix the strings to all use the same syntax for the SET command. Other strings may be out of date as well; I did not evaluate them.

[ryandesign (Ryan Carsten Schmidt)]

patch to fix pa localization issue

[ToePeu@…]

Now it don't install legacy perl library to system anymore. ( not using macport one yet, it maybe next job, include glib, intltool, iconv, openssl, growl, tcl, python, even xchat2 if available ) So every issues about perl are removed.

I am really thank you for sed patch. It is applied and works well.

Portfile.4 please. I now sure it works well!

[ToePeu@…]

aqua/xchataqua/Portfile revision change (minor fix)

[ToePeu@…]

new Portifle

[ToePeu@…]

Hi :) is there any problem to accept this Portfile?

new portfile is supporting 10.5 perfectly.

If there is any problem, please let me know.

Thanks!

[ryandesign (Ryan Carsten Schmidt)]

Sorry, I seem to have forgotten about this port. In the mean time, both the homepage and the master_sites listed in the portfile no longer exist. I found ​https://github.com/xchataqua/xchataqua which seems to have current development, but no version matching "0.17-rc2-20100907" -- it goes from "0.17-rc1" in 2009 straight to "appstore-1.0.1" in 2011. The latest version there is "appstore-1.0.6"; we could try using that. However, it's also probably fairly easy to install xchataqua using the Mac App Store.