#2923 Spec templates cleanup
Closed: fixed 6 years ago Opened 6 years ago by edewata.

The spec files included in the source repository are actually only generic templates. The current development build process (with compose scripts) relies on them, but they are not actually used to create the official OS releases.

To avoid confusion, they probably should be renamed with .in suffix, for example:
https://github.com/freeipa/freeipa/blob/master/freeipa.spec.in

The change log entries should be removed from these templates since they are irrelevant for development. Actual change log entries may be OS-specific so they belong in the actual OS-specific spec files.

The source tarball should include these spec templates since they are needed if someone downloads the source tarball and wants to create a development build.


Metadata Update from @edewata:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

6 years ago

The patched_* and hybrid_* options for compose scripts can be removed.

The following spec file templates need to have a "BuildRequires: gcc-c++" dependency added due to their use of CMake (which apparently checks for the existence of C/C++ compilers):

  • dogtag-pki-theme.spec.in
  • pki-console.spec.in

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.6.0 (was: 10.6)
- Issue status updated to: Closed (was: Open)

6 years ago

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/3041

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata