[Bug 522204] New Package for Dogtag PKI: dogtag-pki-common-ui

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=522204





--- Comment #6 from Kevin Wright <kwright at redhat.com>  2009-12-15 14:18:14 EDT ---
The "pki-native-tools" package does not own "%{_datadir}/pki/" -- however,
multiple packages do own various subdirectories under "%{_datadir}/pki/":

    # rpm -qf /usr/share/pki
    dogtag-pki-common-ui-1.3.0-2.fc11.noarch  -- sole-owner of
"/usr/share/pki/common-ui/"
    pki-common-1.3.0-4.fc11.noarch -- sole-owner of "/usr/share/pki/scripts/"
    dogtag-pki-ca-ui-1.3.0-2.fc11.noarch -- sole-owner of
"/usr/share/pki/ca-ui/"
    ...

Since Dogtag encompasses "six" distinct servers, but does not require all six
to be installed, many distinct subdirectories will be owned under the common
"/usr/share/pki/" directory, and we therefore follow the rule as described in:
"https://fedoraproject.org/wiki/Packaging/Guidelines#File_and_Directory_Ownership" 

> 2)why obsoletes and provides included here?
> Provides:       pki-common-ui = %{version}.%{release}
>
> Obsoletes:      pki-common-ui < %{version}.%{release}
>
> I can't see package pki-common-ui in fedora.
>
Dogtag directory server includes a "UI" package called "dogtag-pki-common-ui"
whereas Red Hat directory server includes a "UI" package called
"redhat-pki-common-ui".

By providing "pki-common-ui" from both of these packages, we are able to have
the dependent package "pki-common" simply Require "pki-common-ui", and thus can
easily change the runtime "UI" components.

> 3) why following Requires is needed?
> Requires:       bash >= 3.0
>

Seven of the eight "UI" packages contain a single "Require" statement; we used
"Requires:     bash" (removed the >= 3.0) so that rpm would not complain.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.