-----BEGIN PGP SIGNED MESSAGE-----
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  
rpmbuild)
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  
against
the file system, not against added package file lists.

73 de Jeff


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFGm80duHNkGyA5spERAnCQAKC42c/NyV1P+M0N26dIWqQuvff7LACeJkD2
bayOZLo84zsokTfYjo1YFmA=
=V1is
-----END PGP SIGNATURE-----