Jeffrey Fearn wrote:
Eric Christensen wrote:
I don't know, Jeff. It doesn't appear to fail for us. The Fedora
release notes were built with Publican and then combined to form a
single SRPM using an additional step outside of Publican. We push that
single SRPM out and people end up with the Release Notes on their
desktop in their local language that they selected for the entire
system. Perhaps our implementation is different?
It doesn't fail in the sense of you can't install packages, it fails in
the sense of it's not scalable and fails to meet what are IMHO pretty
basic standards for maintainability.
Using publican to generate arbitrary output is fine, embedding that
process in to publican, requiring us to maintain it and meet the
standards expected of us, is not necessarily fine. In this case I don't
think it's maintainable, so unless you can give me a solution I think is
maintainable it's not going to be embedded in publican ... unless of
course you rustle up someone else to maintain it, in which case, patches
are accepted.
BTW I haven't been able to check the release notes on rawhide because
yelp is broken.
Cheers, Jeff.
bah! stupid reply button, I thought we fixed that :(
--
Jeff Fearn <[email protected]>
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY
_______________________________________________
publican-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/publican-list
Wiki: https://fedorahosted.org/publican
