Red Hat Bugzilla – Bug 870201
Request to update to Publican 3
Last modified: 2012-12-19 10:48:38 EST
Description of problem:
This is a request to add publican 3, as used for internal Red Hat content development, to RHEL 7. Publican is a tool for generating documentation output in a number of formats from a single HTML source. Publican is used to generate Red Hat's online documentation, Fedora's online documentation, and documentation for several packages that appear in RHEL itself.
Distribution of this major release of publican with RHEL 7 would assist layered products wishing to deploy documentation to customer sites with a consistent look and feel to that of the online documentation.
Looking at this, it would require at least 25 additional perl modules above and beyond what's currently in RHEL 7.
Is this something we might be able to ship in some sort of common tools for LP repo, rather than maintaining the perl infrastructure for the full RHEL lifecycle?
Possibly, my only question is how that meshes with having publican 2.8 in base-RHEL (mind you 2.8 which is what appears to be built for el7 right now is still a significant and much appreciated step up from what was in RHEL 6 which from memory was publican 2.1).
Hm, some of those may already be built there for RHEL 7 - I am going off the compsoed tree, which as of last week didn't have those modules (nor publican-2.8 itself).
I suspect this is because none of the in-RHEL docs packages that require publican to build have been done for RHEL 7 yet.
(In reply to comment #3)
> Hm, some of those may already be built there for RHEL 7 - I am going off the
> compsoed tree, which as of last week didn't have those modules (nor
> publican-2.8 itself).
Right, I was just looking/guessing from brew where I can see publican-2.8-4.1.el7 tagged into rhel-7.0.
> I suspect this is because none of the in-RHEL docs packages that require
> publican to build have been done for RHEL 7 yet.
The one example I did find that is already being built (or at least, attempting to be built ;)) was the Systemtap docs (see Bug # 849985).
I cannot grasp idea why to keep publican 2 in RHEL-7 while having publican 3 in separate repository.
Perl maintenance herd recognized public 2 as the only reverse dependency of another 31 perl packages which could go away from RHEL-7 if we moved publican 2 into separate repository.
(In reply to comment #5)
> I cannot grasp idea why to keep publican 2 in RHEL-7 while having publican 3
> in separate repository.
Ideally I would actually prefer to just have one version, Publican 3, in RHEL-7 without having to use a separate repository/channel at all.
> Perl maintenance herd recognized public 2 as the only reverse dependency of
> another 31 perl packages which could go away from RHEL-7 if we moved
> publican 2 into separate repository.
I don't see how removing publican from RHEL-7 completely is a viable solution given it is used/required by other packages (systemtap docs, release notes, etc.). The decision required is more around which version to carry and who maintains it.
Yeah, I was assuming it was request-to-replace, not request-to-add.
I'm happy to be the maintainer of any publican deps the "Perl maintenance herd" don't want to cover.
There are a bunch of non-perl deps for P2 that could also go away by moving to P3, like FOP and a bunch of related Java packages.
Wait, make both the perl and java teams' load lighter? I think we have a winner.
Do you have a test build releng can import? F18 still has 2.8.
could you specify exact package names and branches to be merged to rhel-7.0?
publican is not in comps definition file. Should it be?
No, the intention is that it's there in the optional repo and the build root for our documentation to use.