Difference between revisions of "PKI Components Collectively via Subversion"

From Dogtag
Jump to: navigation, search
(Building All PKI Components Collectively as a Group)
(Building All PKI Components Collectively as a Group)
Line 26: Line 26:
  
 
All non-UI PKI RPMs will be created in '''src/pki/release/pki/base/{component}/dist/rpmpkg/RPMS/{arch}''' and '''src/pki/release/pki/base/{component}/dist/rpmpkg/RPMS/noarch''', while all PKI UI components will be created in '''src/pki/release/pki/{flavor}/{component}/dist/rpmpkg/RPMS/noarch'''.  All PKI RPMs will also be automatically installed on the system.
 
All non-UI PKI RPMs will be created in '''src/pki/release/pki/base/{component}/dist/rpmpkg/RPMS/{arch}''' and '''src/pki/release/pki/base/{component}/dist/rpmpkg/RPMS/noarch''', while all PKI UI components will be created in '''src/pki/release/pki/{flavor}/{component}/dist/rpmpkg/RPMS/noarch'''.  All PKI RPMs will also be automatically installed on the system.
 +
 +
 +
When you have finished, make sure you have all the packages installed:
 +
rpm -qa | grep -i pki- | sort
 +
You'll see output like this:
 +
pki-ca-ui-1.0.0-1.fc8
 +
pki-common-ui-1.0.0-1.fc8
 +
pki-console-ui-1.0.0-1.fc8
 +
pki-kra-ui-1.0.0-1.fc8
 +
pki-manage-1.0.0-1.fc8
 +
pki-migrate-1.0.0-1.fc8
 +
pki-native-tools-1.0.0-1.fc8
 +
pki-ocsp-ui-1.0.0-1.fc8
 +
pki-ra-1.0.0-1.fc8
 +
pki-ra-ui-1.0.0-1.fc8
 +
pki-setup-1.0.0-1.fc8
 +
pki-tks-ui-1.0.0-1.fc8
 +
pki-tps-ui-1.0.0-1.fc8

Revision as of 22:29, 28 March 2008

Building PKI Components Collectively via Subversion

Checking out PKI Source Code via Subversion

Follow the instructions to checkout a read-only copy of the PKI source code using subversion:

Building All PKI Components Collectively as a Group

In order to build all PKI components collectively as a group, the sudo executable must be available on the development machine. If present, then all PKI components can be built collectively through the use of two scripts, prepare_pki and build_pki, by becoming the root user and adding the following two lines to the /etc/sudoers file:

{username}  ALL = NOPASSWD:       /bin/rpm
{username}  ALL = NOPASSWD:       /usr/bin/yum

First, become the desired {username}, and change directories into the scripts directory:

cd src/pki/{flavor}/scripts      where "{flavor}" equals "linux"

Next, invoke the preparation script to install all PKI support packages:

script -c ./prepare_pki typescript.prepare_pki

NOTE: While the script command is optional, the user may find it useful for debugging purposes.

Finally, issue the following command to build all PKI components:

script -c ./build_pki typescript.build_pki

NOTE: While the script command is optional, the user may find it useful for debugging purposes.

All non-UI PKI RPMs will be created in src/pki/release/pki/base/{component}/dist/rpmpkg/RPMS/{arch} and src/pki/release/pki/base/{component}/dist/rpmpkg/RPMS/noarch, while all PKI UI components will be created in src/pki/release/pki/{flavor}/{component}/dist/rpmpkg/RPMS/noarch. All PKI RPMs will also be automatically installed on the system.


When you have finished, make sure you have all the packages installed:

rpm -qa | grep -i pki- | sort

You'll see output like this:

pki-ca-ui-1.0.0-1.fc8
pki-common-ui-1.0.0-1.fc8
pki-console-ui-1.0.0-1.fc8
pki-kra-ui-1.0.0-1.fc8
pki-manage-1.0.0-1.fc8
pki-migrate-1.0.0-1.fc8
pki-native-tools-1.0.0-1.fc8
pki-ocsp-ui-1.0.0-1.fc8
pki-ra-1.0.0-1.fc8
pki-ra-ui-1.0.0-1.fc8
pki-setup-1.0.0-1.fc8
pki-tks-ui-1.0.0-1.fc8
pki-tps-ui-1.0.0-1.fc8