To the buildtool developers,
I tried to build and package a package using the buildtool buildpacket
scripts, when I found a problem in buildpacket.
I created a package definition in the package buildtool.cfg file,
including a symlink definition, as follows (only relevant parts):
<Package>
<talk>
<Permissions>
Files = 644
Directories = 755
</Permissions>
<Owner>
Files = root:root
Directories = root:root
</Owner>
<Contents>
<File>
Source = usr/sbin/talkd
Filename = usr/sbin/in.talkd
Type = binary
Type = list
Permissions = 755
</File>
<File>
Filename = usr/sbin/in.ntalkd
Target = usr/sbin/in.talkd
Type = link
Type = list
</File>
</Contents>
</talk>
</Package>
When running buildpacket, it follows the symlink usr/sbin/in.ntalkd and chmod's what it
points to and not the symlink itself.
Another point (and why I found this): I first used "Target = in.talkd", but this fails,
because it makes a symlink to /in.talkd. Wouldn't it be easier and clearer to have
Target
contain the absolute or relative path the symlink should point to in the final package?
Then one could also use parent-dir. references for example.
For the rest, this buildtool is working quite nice, great work!
Jaap Eldering
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
