I'm a long time Slackware user and I run it as my desktop OS. I'm
running AbiWord 2.4.4 built from source on my system and didn't have any
compilation issues at all. I can find nothing matching "*gconf2*" on my
system, so I'm not sure why that was identified as a dependency.
Mr Culleton, if you send me e-mail we can go through a 2.4.4 AbiWord
build from source together and get you up and running. :)
Peace...
Tom
Ryan Pavlik wrote:
>
> From a slackware user's perspective:
> I now use Slackware only as a server OS. If you use it as a desktop
> OS, install a third-party GNOME installation - gconf2 is a very
> standard component of GNOME. The removal of everything related to
> GNOME in Slackware 10.2 (including very minimally-depending libraries
> such as libgnomeprint and libgnomeprint-ui, two libraries which
> AbiWord needs) unfortunately meant the demise of many useful desktop
> applications. If you install libgnomeprint, libgnomeprint-ui, and its
> dependencies (I think just hicolor-icon-theme, although don't quote me
> on that), you should be able to compile a --without-gnome (which I
> think is a default configure switch) GTK+ only version of AbiWord to
> work on Slackware.
>
> Good luck!
>
> (For reference, I now use Ubuntu on the desktop, Slackware on the server)
>
> Ryan
>
> John Culleton wrote:
>>
>> There is nothing in life so simple, so universally understood, so
>> foolproof but that some eager beaver can't complicate it beyond belief.
>>
>> I upgraded my Slack system and in the process Abiword disappeared.
>> No problem, I could just download the latest version and install,
>> right? Wrong. The install directions were a totally new adventure,
>> but I was reassured I only had to do most of it once. After going
>> through all the instructions I got down to the bottom of the page
>> where it said in essence you could just download a tarball and do it
>> the easy way. So, muttering imprecations under my breath I did that.
>> Then I started through the familiar ./configure, make make install
>> sequence.
>> The configure blew up because I didn't have a file called gconf2. The
>> instructions at that point suggested that I find that file or a file
>> with a similar name on my Slack system. None such available.
>> However the old version of Abiword was available on my Slack 10.2
>> disk so I installed that and things went forward as expected.
>>
>> I suggest that if the instructions for a conventional install are
>> given they should be given first. That would save a lot of time. I
>> also suggest that if something called gconf2 is required, and it
>> isn't a standard component in e.g., slackware, then it shold be
>> included in said tarball, or a more readily available file used instead.
>>
>>
>> As for me I will continue to use the old Abiword for such things as
>> converting doc files to rtf and so on. I wasted a lot of time today
>> and finally ended up with the old version anyway. Whatever virtues
>> the newer version has I will never know. It isn't worth the hassle
>> to find out.
>> (end grump)
>>
>> John Culleton
>
>
-----------------------------------------------
To unsubscribe from this list, send a message to
abiword-user-request@abisource.com with the word
unsubscribe in the message body.
Received on Wed Jun 28 03:32:41 2006
This archive was generated by hypermail 2.1.8 : Wed Jun 28 2006 - 03:32:41 CEST