The FreeBSD Diary

The FreeBSD Diary (TM)

Providing practical examples since 1998

If you buy from Amazon USA, please support us by using this link.
[ HOME | TOPICS | INDEX | WEB RESOURCES | BOOKS | CONTRIBUTE | SEARCH | FEEDBACK | FAQ | FORUMS ]
 New Topic  |  Go to Top  |  Go to Topic  |  Search  |  Log In   Newer Topic  |  Older Topic 
 Erroneous statement about files
Author: Gerald Stoller 
Date:   27-01-02 11:25

You wrote "I determined this path by inspecting /var/db/pkg/dnetc-2.8010.462_1,1/+CONTENTS. Because it starts with a /, the ports system will know this is the name of a file, not an executable. Therefore, it will not search your $PATH. " All files, even executable ones, have names that start with a / , for the ports system to "know" that files with such names are not executable may be some restriction placed on users of the ports system, but it is not an inherent condition of a UNIX-like system. Once a / is involved in the name of the first file on a command line, the PATH is not searched.

Reply To This Message
 
 Re: Erroneous statement about files
Author: Dan Langille 
Date:   27-01-02 19:19

Gerald Stoller wrote:
>
> You wrote "I determined this path by inspecting
> /var/db/pkg/dnetc-2.8010.462_1,1/+CONTENTS. Because it starts
> with a /, the ports system will know this is the name of a
> file, not an executable. Therefore, it will not search your
> $PATH. "

Yes, I did write that.

> All files, even executable ones, have names that
> start with a / , for the ports system to "know" that files
> with such names are not executable may be some restriction
> placed on users of the ports system, but it is not an
> inherent condition of a UNIX-like system.

Note: I did not say system. I said "the ports system". I maintain my statement is correct. However, I did not state where I obtained this information. Sorry about that. The following extract is from /usr/ports/Mk/bsd.port.mk


# FETCH_DEPENDS - A list of "path:dir[:target]" tuples of other ports this
# package depends in the "fetch" stage. "path" is the
# name of a file if it starts with a slash (/), an
# executable otherwise. make will test for the
# existence (if it is a full pathname) or search for
# it in your $PATH (if it is an executable) and go
# into "dir" to do a "make all install" if it's not
# found. If the third field ("target") exists, it will

> Once a / is
> involved in the name of the first file on a command line,
> the PATH is not searched.

I think we are talking about two different things here.

Reply To This Message
 Forum List  |  Threaded View   Newer Topic  |  Older Topic 


 Forum List  |  Need a Login? Register Here 
 User Login
 User Name:
 Password:
 Remember my login:
   
 Forgot Your Password?
Enter your email address or user name below and a new password will be sent to the email address associated with your profile.
How to get the most out of the forum

phorum.org