|
From: Justin M. F. <jmf...@li...> - 2007-11-11 20:22:49
|
On Thu, 2007-11-08 at 18:21 -0800, Elliot Lee wrote: > Thanks for the explanation. I think a .d scheme would be very useful and > very easy to do. Can't promise it for the next release (which I'm hoping > will be ready in a week or so), but I'll try if there's time. The main thing > I'd like feedback from others on is the actual directory path that these > scripts will be dropped into. I'm thinking of either > > Scriptsdir="`dirname $0`"/scripts/`basename $0`.d" > > (to match your current setup) or just > > Scriptsdir=$0.d > > The main constraint is that it has to work properly even if the scripts are > in /usr/local/etc or /var/fooblah. > Right, so the scripts really have to be in a set place at build time, by default that is $sysconfdir/vmware-tools. It seems to make the most sense to me that we look in that tree for the user scripts. Scriptsdir="`dirname $0`"/scripts/`basename $0`.d" would work just fine, our actual scripts use %(sysconfdir)s/vmware-tools/ and use conary macro substitution to place that as /etc/vmware-tools at build time. Of course if the builder has those set elsewhere, that is fine too. Justin |