[SOLVED] Best package of Openoffice on slackware64

darksaurian · 06-05-2010, 07:21 AM

I don't know about Slack 64. I installed OOo from slackbuilds for Slack 13.1 32 bit. It installed super fast because it used the debian package, it didn't need to compile. Works fine as far as I can tell.
EDIT:
Oh wait OOo slackbuild uses the RPM package not the Debian one. Oops.

business_kid · 06-05-2010, 08:55 AM

Quote:

Originally Posted by masinick

For what it's worth, isn't Slackware 13.1 either released or at the very least out with a second (or third) potential release candidate? Would a backup of relevant personal data (unless you have your /home partition separate, which can be a good idea), then a fresh installation of the latest 13.1 kit (with Open Office 3.2), possibly help out?

You indicate possible conflicts between X server libraries and application interfaces. It seems to me that you should be able to get something pretty recent from RC1, RC2, or the latest, whatever is closest to final release that works for you.

I can certainly download slack64-13.1 from heanet. I think I'll stand back for a month or two, let my wife see a little more of me, enjoy what little there is of the fleeting Irish summer, and certainly do a clean install from there once all the versions have settled out.

business_kid · 06-05-2010, 09:04 AM

Marking this one solved. This post is simply to thank everyone who bent their minds to offering me advice on this. Good advice, all of it.

There's nothing wrong with the packages, OO or xfce. There's a lot wrong with my particular install, and I have strayed too far from the norm to make it worth trying to sort out. And, on mature reflection, I don't want to sort it out, because the next program I install is going to be another nightmare.
Feel free to post flames, but I'll not be rising to many of them.

rworkman · 06-05-2010, 11:43 PM

Well, I *love* to flame people, but I don't see any valid reason to flame you. Good conclusion to the thread, and I wish you the best in family time and getting things sorted later :-)

business_kid · 06-09-2010, 01:35 PM

Just found the main reasons why this ATI graphics update didn't work.

1. According to this

Quote:

The power management voltage support comes by means of four patches:

- patch default power state with default clocks/voltages on r6xx+
- radeon_set_power_state fixes
- voltage fixes
- add support for SetVoltage cmd table

Right now these are just patches sitting on the DRI mailing list. These patches potentially could still end up in the Linux 2.6.35 kernel otherwise they will make it in the Linux 2.6.36 kernel a few months later.

The patches to the kernel are coming in 2.6.35, but I'm on 2.6.33

2. Apparently some of the r600 development work was going on on a personal git tree that someone took at some point. The main tree moved on, however. Somebody has now married them up and put it in a third git tree. This third tree was located here
http://cgit.freedesktop.org/~mareko/mesa/log/?h=r600g<http://cgit.freedesktop.org/%7Emareko/mesa/log/?h=r600g>

3. Jerome Glasse of Red Hat is working on a r600g driver that will be added in there and be a boon for r600 owners. He's got it working more or less, but rather less than more, and it was not in a fit state for diehard alpha testers yet.

4. Apparently tiling support is also for 2.6.35

Quote:

Hopefully the DRM bits for this tiling support, which can lead to performance enhancements, will land still in the Linux 2.6.35 kernel thus allowing the tiling support to appear in most Linux distribution updates this fall.

So my idea of taking the summer off, and trying again in the autumn seems to have been a good idea because these guys will be putting different bits of this together.

Maybe 2011, we'll have decent ati drivers bedded down. I did automate an update to slackware-current, but the results weren't encouraging. Despite an upgradepkg --reinstall on everything. Too many compiles thrown in on top, I imagine.