Mike Frysinger wrote:
On Friday 17 August 2007, Rod wrote:
  
Is anyone aware of any tools based on portage that can identify which
files in a package are required by the run-time as opposed to those only
required for the build?
    

RDEPEND vs DEPEND ?
-mike
  
Thanks for the reply.

I don't mean the package dependencies, I mean the files with a package. My run-time environment won't have portage or the tool chain to build packages, so it doesn't need any of the build stuff, only the run-time stuff.

For example, the following command:

# equery files =dev-libs/openssl-0.9.8d

shows the following files, among many others:

/usr/include/openssl/aes.h
/usr/include/openssl/asn1.h
/usr/include/openssl/asn1_mac.h
/usr/include/openssl/asn1t.h
/usr/include/openssl/bio.h
/usr/include/openssl/blowfish.h
/usr/include/openssl/bn.h
/usr/include/openssl/buffer.h
/usr/include/openssl/cast.h
/usr/include/openssl/comp.h
/usr/include/openssl/conf.h
/usr/include/openssl/conf_api.h

I don't think I need any of these header files for run-time.

The question is how to identify all such files in a package.


Thanks,
Rod



-- 
[EMAIL PROTECTED] mailing list

Reply via email to