Hi David on 08.06.2011 18:41, davidMbrooke wrote: ...
> > Note that some applications do not follow the naming convention of > DIRECTORYNAME.tar.gz which I presume is why the tools/getdirname.pl > script was created. This actually looks inside the file to see what the > directory is called. Right, I was not aware of that script and my deduction of the directory name is just valid for a single package. I am a bit weary of the perl approach though, as perl is IMHO just a wrapper around shell in many cases and again IMHO vastly overvalued. basically the same could be achieved with # basename `tar tzf openswan-2.6.33.tar.gz | head -1` openswan-2.6.33 Mhhh... hardly worth to write a tool :-) Thanks for the hint, will implemnent this in buildtool.mk Just tested it, in haserl it looks like HASERL_DIR:=$(shell basename `tar tzf $(HASERL_SOURCE) | head -1`) and works fine. I believe we should go one step further and remove the XXX_DIR convention completely to replace it with a generic term. In the long run we might be able to get close to a generic makefile. like SOURCE_DIR=$(shell basename `tar tzf $(iSOURCE_TARBALL) | head -1`) again for haserl <File haserl-0.9.25.tar.gz> Server = localrepo Revision = HEAD Directory = haserl envname = SOURCE_TARBALL </File> cheers Erich ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
