You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation is starting to get fairly large, with translations. It would be better to separate it into its own subpackage that can be left off of space-constrained install media like LiveCDs.
I was recently made aware of the --excludedocs argument to RPM. This makes it possible to install an RPM without any contents marked as {{{%doc}}} in the spec file. There's no need to split out the documentation into a subpackage.
I've verified that the {{{%lang}}} routines that we use in SSSD produce proper entries labeled as {{{%doc}}} in the final output.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1302
The documentation is starting to get fairly large, with translations. It would be better to separate it into its own subpackage that can be left off of space-constrained install media like LiveCDs.
Comments
Comment from sgallagh at 2012-04-19 13:56:26
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=814221
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=814221 814221]
Comment from sgallagh at 2012-04-27 15:18:14
Fields changed
keywords: => easyfix
Comment from dpal at 2012-09-24 17:20:25
Fields changed
milestone: SSSD 1.9.0 => SSSD 1.9.1
Comment from jhrozek at 2012-10-05 17:33:34
Fields changed
milestone: SSSD 1.9.1 => SSSD 1.9.2
Comment from dpal at 2012-10-11 15:02:16
Fields changed
milestone: SSSD 1.9.2 => SSSD 1.10 beta
Comment from dpal at 2012-12-20 23:33:42
Fields changed
selected: => Not need
Comment from dpal at 2013-01-02 15:32:09
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
Comment from sgallagh at 2013-06-20 15:35:13
I was recently made aware of the --excludedocs argument to RPM. This makes it possible to install an RPM without any contents marked as {{{%doc}}} in the spec file. There's no need to split out the documentation into a subpackage.
I've verified that the {{{%lang}}} routines that we use in SSSD produce proper entries labeled as {{{%doc}}} in the final output.
changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
resolution: => wontfix
review: => 0
status: new => closed
Comment from sgallagh at 2017-02-24 15:01:17
Metadata Update from @sgallagh:
The text was updated successfully, but these errors were encountered: