Cisco Cisco Application Extension Platform for SRE

tcptrace-6.6.7-1.2.fc5.rf.i386.rpm.deps

The .deps file contains all of the dependencies of the RPM file.

To see the dependencies required by the RPM file, type the following: 

[root@fedora deps]# cat tcptrace-6.6.7-1.2.fc5.rf.i386.rpm.deps /bin/sh <enter>

libc.so.6() 

libc.so.6(GLIBC_2.2.5)   

libc.so.6(GLIBC_2.3)   

libc.so.6(GLIBC_2.3.4)   

libc.so.6(GLIBC_2.4)   

libm.so.6()   

libm.so.6(GLIBC_2.2.5)   

libpcap.so.0.9.4()   

rpmlib(CompressedFileNames) <= 3.0.4-1

rpmlib(PayloadFilesHavePrefix) <= 4.0-1

[root@fedora deps]# 

Use the information on scripts and dependencies as shown in the 

To port your application, perform the following steps.

Examine the library and RPM dependencies, gather any new required RPM files, and perform the 
extraction using similar methods to those shown in 

.

After extracting the RPM files using the rpm_extractor.sh tool, copy the output directory to the source 
directory you are using to package your application by entering the following command: 

source-directory/ <enter> 

Examine the pre install, post install, pre uninstall, and post uninstall scripts. Include the appropriate 
scripts in the project source directory.

Package the application and install it on the Cisco AXP service module.

By default, a Linux shell is not provided in the vserver environment by the CLI. 

To configure your application’s virtual instance to have a Linux shell, perform the following steps.

Include a postinstall script and pass it to the Cisco AXP packaging tool during execution of the 
packaging tool.

Create the postinstall script, such as file postinstall.sh, and place the script in a sub-directory under your 
designated source-directory for your application (the directory is /opt/tcptrace/ in this guide).