I did this by hand, and there were no dependency problems. 2.0.1 can be compiled and run on FC5 just fine, so it should be backported.
It's a major version upgrade, which is frowned upon. (See also: OO.o version 2, gnome upgrades, etc.)
Hmm... I can't think of a good argument to that exactly. I can say that it introduces no file incompatibilities that I'm aware of and largely just looks and acts a lot nicer. But it is true that a good portion of the UI code was re-written, so it's definitely a pretty major change. My main thing is that I support a few friends, and some of them have asked me about a finance program, and gnucash is ugly and kind of unfriendly, and kmymoney2 is KDE, and they use all GNOME stuff. So it would be nice if gnucash could be nicer looking and friendlier, especially without me having to make them a nice package to install out of the normal flow of using 'pup'.
Note that one reason that backporting fully to FC5 is tricky is that OFXDirectConnect support (one of the new features) requires a newer, ABI-incompatible, libofx than what ships in FC5, and we cant' really change that since other apps use libofx. In the meantime, you may be interested in: http://people.redhat.com/notting/gnucash/2.0/FC-5/
Hey, thanks. That is pretty helpful. And your reasoning is generally sound, so I'm just going to close this bug as 'WONTFIX' and be happy. It would be nice to have a resolution status that made the bug still show up in the default searches though so that other people who really wanted gnucash in FC5 could still find it. But I suppose they can always just modify the search to include some of the resolved statuses. Again, thanks.