[Bug 504063] Toolchain next steps

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=504063


John J. McDonough <wb8rcr at arrl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wb8rcr at arrl.net




--- Comment #1 from John J. McDonough <wb8rcr at arrl.net>  2009-06-04 08:22:25 EDT ---
I wonder a bit about that description.

In the process of preparing f-r-n for F11, there were only three things I could
have used from a next generation toolchain: 1) Create .omf files, 2) deal with
language merge/unmerge, and 3) package.

I think we know wnat f-d-u does, at least "well enough" since we are leaving it
behind.  If we are also leaving yelp to history, which it sounds as if we will,
then almost all of f-d-u's magic is irrelevant.

I think we have concluded we want to use Publican pretty much everywhere, at
least, I thought that's what I heard.

So, that leaves us with just a few questions, pretty much around Publican.

1) Partly because of Publican weirdness, but also because we were clinging on
to Gnome help, we manually produced the RPM for f-r-n. How hard do we want to
push to get upstream to produce useable RPMs?  My spin is that with a single
document the process is simple enough that getting it fixed in Publican is more
work than just doing it.

2) If we are going to simply point to an html from the menu, how do we handle
languages?  I know it can be done, I just don't know how.  We need to identify
that and document it.

3) Is there really any issue with languages once we have the new Transifex.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.