Abiword 2.1.0 has been released, it is in a development branch, so it can be slotted. The binary for this release is abiword-2.2 while previous ones were abiword-2.0 so they can both live together. Reproducible: Always Steps to Reproduce:
later date, 2.0.2 still crashes enough.
*** Bug 36189 has been marked as a duplicate of this bug. ***
bah, I'll try to make an ebuild later. It's a development release, the point is that people test it.
oh happy users.. what a <politeness snip> attitude we got here. Yeah i'm happy i'm putting a lot of hours in this distro now, all the gratitude you get is just so rewarding. Lets dump the tree full of testing stuff, because thats what testing alpha/beta/cvs releases are for. Broken systems for everyone, see who complains then.
I must say, that final comment was not only uncalled for, but really does not show a full understanding of portage. While I know you do fully understand portage, you seem unwilling to take advantage. Last time I checked, there are MULTIPLE way to mask a package, as has been done with certain things (ie. gimp unstable), while the ebuilds were still in the tree. Of something is masked an keyworded, and someone decides to circumvent both methods, they had damn well better know what they are doing, and should it cause instability in their machine (which is unlikely, the worst could be that Abiword-2.2 does not function), then they can reverse the action, and do as they please. Furthermore, as stated, Abiword-2.0 and Abiword-2.2 can be installed on a machine at the same time, so should Abiword-2.2 be unstable, said user can always continue using the stable release. The kind of attitude seen above seems to stiffle open source contribution (I myself decided to make a script and build nightly), because some people are unwilling to use the jewel of gentoo as the PERFECT method to easily and safely install versions of software to test.
Created attachment 27052 [details] abiword-2.1.0.ebuild This is slightly broken; it doesn't do any patching, nor does it actually do anything with the abiword-docs directory. There's no makefile in that directory. It DOES install abiword-2.1.0 properly, and alongside 2.0.3. Both appear to remain separate, i.e. /usr/share/AbiSuite-2.0 vs /usr/share/AbiSuite-2.2 It didn't crash on startup, and can load an rtf, and looks alright. I'll use it omre intensively later. For now, this build is functional enough for those who want to get it up-and-running with all plug-ins on at least an amd k7 athlon xp.
actually, it is a perfectly valid attitude after this spring. No, hard-masking isn't a good solution for the beginning of an unstable tree, we usually take in massively popular development releases -at the end- of the development process for a state in hard masked status. However, policy (whooo, shiney. ) doesn't allow for using package.mask for every package that just enters development process.
*** Bug 46705 has been marked as a duplicate of this bug. ***
