> Because midgard-config.in has those settings. And I think that one has > it because default CVS checkout does that. I've added a command to > configure to make it executable. > > > And why after "rules binary" it is supposed to be > > in tmp/usr/bin as other midgard-* files? > > Because it's a script?
I mean, why it is to be copied from tmp/usr/bin while it is not created there? make[3]: Entering directory `/root/midgard/midgard-lib-1.4_CVS200203010203/test' /bin/sh ../mkinstalldirs /root/midgard/midgard-lib-1.4_CVS200203010203/debian/tmp/usr/bin /usr/bin/install -c -o root -g root midgard-pageresolve /root/midgard/midgard-lib-1.4_CVS200203010203/debian/tmp/usr/bin/midgard-pageresolve /usr/bin/install -c -o root -g root midgard-snippet /root/midgard/midgard-lib-1.4_CVS200203010203/debian/tmp/usr/bin/midgard-snippet /usr/bin/install -c -o root -g root midgard-owner /root/midgard/midgard-lib-1.4_CVS200203010203/debian/tmp/usr/bin/midgard-owner make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/root/midgard/midgard-lib-1.4_CVS200203010203/test' make[2]: Leaving directory `/root/midgard/midgard-lib-1.4_CVS200203010203/test' make[2]: Entering directory `/root/midgard/midgard-lib-1.4_CVS200203010203' make[3]: Entering directory `/root/midgard/midgard-lib-1.4_CVS200203010203' /bin/sh ./mkinstalldirs /root/midgard/midgard-lib-1.4_CVS200203010203/debian/tmp/usr/bin /usr/bin/install -c -o root -g root midgard-config /root/midgard/midgard-lib-1.4_CVS200203010203/debian/tmp/usr/bin/midgard-config this line above is not be done Should midgard-config be created in test directory as other midgard-* scripts? > > mkdir for /tmp/usr/bin is making twice . > > I don't know what part of the script does that. As above Piotras --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
