AquaLess fails to install because it is looking for AquaLess.app in the wrong place

[m@…]

Oceanus:~ nathan$ port install AquaLess ---> Fetching AquaLess ---> Attempting to fetch AquaLess-1.4-src.tar.gz from ​http://voxel.dl.sourceforge.net/aqualess ---> Attempting to fetch AquaLess-1.4-src.tar.gz from ​http://kent.dl.sourceforge.net/aqualess ---> Verifying checksum(s) for AquaLess ---> Extracting AquaLess ---> Configuring AquaLess ---> Building AquaLess ---> Staging AquaLess into destroot Error: Target com.apple.destroot returned: error copying "/opt/local/var/db/dports/build/ file._opt_local_var_db_dports_sources_rsync.rsync.opendarwin.org_dpupdate_dports_aqua_AquaLess/ work/AquaLess-1.4-src/build/AquaLess.app": no such file or directory

The problem is that ..build/AquaLess.app is in ...build/Default/AquaLess.app

So it seems either it is being told to build in the wrong place or it is trying to install from the wrong place.

[m@…]

In the Portfile changing:

destroot { xinstall -d -m 755 ${destroot}/Applications/DarwinPorts

file copy ${worksrcpath}/build/${name}.app \

${destroot}/Applications/DarwinPorts/${name}.app

}

to

destroot { xinstall -d -m 755 ${destroot}/Applications/DarwinPorts

file copy ${worksrcpath}/build/Default/${name}.app \

${destroot}/Applications/DarwinPorts/${name}.app

}

allows it to install successfully.

[matt@…]

I can't test this as i don't have any Mac OS X 10.4 machine. Actually there's no problem there on a Mac OS X 10.3.9 machine.

Would you like to be AquaLess's maintainer?

Thanks for reporting the issue.

[m@…]

Would you like to be AquaLess's maintainer?

I do not have much experience, I will do what I can to help out, but I can't be a maintainer.

I don't really understand how this could be a 10.4 induced bug, I am looking around.

[mww@…]

fixored with: ---

set appdir build platform darwin 8 {

set appdir build/Default

}

....

file copy "${worksrcpath}/${appdir}/Aqualess.app ..."

[dominique.marie@…]

(In reply to comment #3)

I don't really understand how this could be a 10.4 induced bug, I am looking around.

I pointed this on the list, this behavior is induced by xcode 2.1

I can't test it but it seems that this fix won't work on 10.4 with xcode 2.0