Bug 786

Summary: In Suse11.2, source file need to give the more detailed path
Product: [Yocto Project Subprojects] ADT Reporter: liping Ke <liping.ke>
Component: adtAssignee: Jessica <jessica.zhang>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: dexuan.cui, lianhao.lu, poky.adt.watcher, poky.watcher, sgw
Version: 1.0   
Target Milestone: 1.0 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description liping Ke 2011-02-28 23:47:41 UTC
I found in SUSE, when source $file, we need better give a detailed path. Otherwise, it will not look for the file which is located@$PWD path.

Thanks & Regards,
criping
Comment 1 Dexuan Cui 2011-03-01 00:19:42 UTC
Copy a section from "man bash":

source filename [arguments]
              Read and execute commands from filename in the current shell environment and return the exit status of the last command exe-
              cuted  from  filename.   If  filename does not contain a slash, file names in PATH are used to find the directory containing
              filename.  The file searched for in PATH need not be executable.  When bash is not in posix mode, the current  directory  is
              searched  if no file is found in PATH.  If the sourcepath option to the shopt builtin command is turned off, the PATH is not
              searched.  If any arguments are supplied, they become the positional parameters when filename is  executed.   Otherwise  the
              positional  parameters are unchanged.  The return status is the status of the last command exited within the script (0 if no
              commands are executed), and false if filename is not found or cannot be read.
Comment 2 liping Ke 2011-03-06 17:47:30 UTC
According Dexuan's description, add "./" should also works.
Anyway, give a full path name is ok. The patch is already in upstream:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=9e6b1ac4b85df82e0351d4375345c450bdb11008