On Sunday 17 February 2008 11:37:54 am David Paleino wrote: > Il giorno Sun, 17 Feb 2008 11:02:21 -0500 > > Andres Mejia <[EMAIL PROTECTED]> ha scritto: > > On Sunday 17 February 2008 4:04:41 am Bas Wijnen wrote: > > > On Sun, Feb 17, 2008 at 02:39:03PM +0900, Emmet Hikory wrote: > > > > > > To find the path, $(dir $_)/script can be used, to make sure it works > > > from any directory. (Attribution: I learned that from reading your > > > uscan invocation below. ;-) ) > > > > Thanks. This was exactly what I wanted to do. > > > > This had me stumped for a long time but now I'm free to use whatever > > scripting language I want and supply whatever options I want for the > > external scripts. > > > > One thing though, the line could be written as "$(dir $_)script" since an > > extra "/" is added at the end for "$(dir $_)". I tested this using > > "@echo $(dir $_)". > > Why not using $(CURDIR)? It should give you the dir where debian/ is > located (i.e. $(CURDIR) == debian/../). I've always used it in my > debian/rules files, and never had any problem. > > Kindly, > David
$(CURDIR) gives you the current working directory you are in, not where debian/ would reside unless you were in the package's top directory anyway. -- Regards, Andres -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
