However, if I set up a target that does include the debian devkit, but I don't actually install it for the target, and I run an executable that use /var/tmp, which doesn't exist, the executable fails, complaining that it can't write the file. If I then 'sb-conf install -d', a /var/tmp dir is created (along with several other /var subdirs) and the executable succeeds.
Note that this only happens when the debian devkit is included in the target setup. If I include just the cputransp devkit and/or the perl devkit, this doesn't happen -- no /var/tmp exists (nor is one created when I later do a 'sb-conf install -d'), but the executable runs fine.
Can someone explain this to me?
Thanks,
Diane
_______________________________________________ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
