RPM Community Forums

Mailing List Message of <rpm-users>

Re: How does bash-provides work?

From: Jeff Johnson <n3npq@mac.com>
Date: Mon 16 Jul 2007 - 21:54:59 CEST
Message-Id: <694D3710-AB4C-4910-8435-68B884ED7407@mac.com>
Hash: SHA1

On Jul 16, 2007, at 3:29 PM, Eric MSP Veith wrote:

> I'm using a patched version of bash to get executables and  
> functions required
> for running a shell script, which works well. However, creating  
> provides
> doesn't seem to be possible that way, and /usr/lib/rpm/ 
> executabledeps.sh is
> not really a help:
> case $1 in
> - -P|--provides)
>     cat > /dev/null
>     exit 0
>     ;;
> Is there any way to automatically create a list of exectuable() and  
> function()
> provides?

Depends on what you are expecting.

The set
	Provides: executable(...)
is exactly the files with executable bit set found in directories  
included in PATH.

The implementation in rpm does that search at install time, not at  
build time.

You seem to want (because you're looking at executabledeps.sh used by  
to want to automagically generate dependencies to be added to packaging.

That's not what the executable(...) dependency name space was  
intended for,
and the only implementation atm uses access(2) as a run-time probe  
the file system, not against added package file lists.

73 de Jeff

Version: GnuPG v1.4.1 (Darwin)

Received on Mon Jul 16 21:55:36 2007
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.