Hi Jaap,
Fixed in cvs. Thanks for pointing that out. Now, buildpacket should not chmod any symlinks anymore (since chmod can't change the permissions of a link anyway).When running buildpacket, it follows the symlink usr/sbin/in.ntalkd and chmod's what it points to and not the symlink itself.
Well, there are two reasons why I wouldn't like such a change.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.
- it would mean extra work coding that, and making sure it actually works (read, I'm lazy ;-))
- more importantly, it would introduce an inconsistency - every other filename is specified relative to / in the package (or relative to the buildtool staging dir for the source file) - and the only thing that would be different would be links. To me, it would seem harder to understand why links are treated differently than everything else.
Martin
------------------------------------------------------- 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
