I'm using this spec for installing my installer files to the iso:

=================================================================
<?xml version="1.0"?>
<package name="paldo-installer">
<description>[Paldo-Installer by Amnon82]</description>
<releases>
<release version="20070512" revision="1" branch="stable" arch="x86">
<deps>
<dep name="tcl"/>
<dep name="tk"/>
<dep name="xkmap"/>
<dep name="gparted"/>
<dep name="gdk-pixbuf"/>
<dep name="smooth-themes"/>
</deps>
<build>
<script>
<archive name="$NAME-x86-$VERSION">
<!-- it creates installer-folder in upkg-folder -->
<cmd>mkdir -p /paldo</cmd>
<cmd>cp -R installer /paldo</cmd>
<cmd>chmod a+x /paldo/installer/*</cmd>
<cmd>chmod a-x /paldo/installer/pinstaller.xpm</cmd>
<text dest="/usr/share/applications/pinstaller.desktop"><![CDATA
Encoding=UTF-8
Name=Install Paldo
Comment=This installs paldo to your hdd
Exec=/paldo/installer/paldoinstaller
Icon=/paldo/installer/pinstaller.xpm
Terminal=false
Type=Application
Categories=Application;System;
StartupNotify=true
]]></text>
</archive>
</script>
</build>
</release>
=============================================================



Upkg can't handle that. I got always broken binariy-files of my installer.
Maybe this helps:

cp -a installer /paldo

It was the stripping:

<dep name="gdk-pixbuf"/>
</deps>
<build strip="no">
<script>
<archive name="$NAME-x86_64-$VERSION">
<!-- it creates installer-folder in upkg-folder -->

These are my stripcmds:

<!-- strip binaries -->
<cmd>find $CHROOTDIR{,/usr}{/bin,/lib,/sbin} -name '*.a' -o -name '*.o' -o -name '*.ko' -type f -exec /usr/bin/strip --strip-debug '{}' \;</cmd>
<cmd>find $CHROOTDIR{,/usr}{/bin,/lib,/sbin} -not -name '*.a' -not -name '*.o' -not -name '*.ko' -not -name '*.exe' -not -name '*.dll' -type f -exec /usr/bin/strip --strip-unneeded '{}' \;</cmd>

do they also affect the folder /paldo/installer or is it a cp problem?