Currently the Dogtag source code is stored in a single source repository, but they are released as 4 separate packages:
and some of these packages have subpackages (e.g. pki-ca, dogtag-pki-console-them).
The packages are sometimes released separately, so they may have different version numbers. Because of that, tagging the source repository can be difficult because the tag will only match the sources for the package being released, not the other packages not released at the time. It would also be impossible to check out different versions of the packages at the same time since they are in the same source repository.
One options is to use a single main package (i.e. pki-core) and convert the others into subpackages (i.e. pki-console).
Another option is to use separate source repository for each package.
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
Metadata Update from @edewata: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @edewata: - Issue set to the milestone: 10.6.9 (was: UNTRIAGED)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1376
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Log in to comment on this ticket.