No need to reply to this thread ... the problem has been solved over a month ago.
Quote:
Originally Posted by rworkman
When we were preparing for the 12.1 release, we compile tested everything in the repo (I say "we" when really David Somero did the *vast* majority of that work), and stardict was one of the things that failed.
|
The Slackbuilds.org script was for Stardict-3.0, and
if it worked on Slackware-12.0,
it should have worked on Slackware-12.1. Check it's error log, if it writes one.
Quote:
Originally Posted by rworkman
We have over 900 applications in our repository for 12.1. We probably didn't have quite that many at the time, but it was more than 800 for sure. With that many applications, we simply don't have time to investigate *why* things are failing to compile - we just know that they *are* failing to compile. We posted a note on our mailing list with everything that failed to build and asked for maintainers and/or other individuals to investigate.
Unfortunately, nobody stepped up to handle stardict, so... there you go.
|
That's too much for one man, or a few individuals, to check out. The person who wrote
the SlackBuild in the first place should be the one to maintain it.
Again, check
Alien Bob's repository first. He writes and tests his own scripts and packages,
and if one fails to build you can email him and he will fix it; not post "it doesn't build." He
has Slackware packages, too, not just scripts.
As noted earlier in this thread, I built Stardict-3.0.1 by editing Alien Bob's script from
Slackware-12.0 during the Slackware-current cycle, after Patrick had updated GTK+2 to a
2.12 version sometime at the first of this year. But Stardict-3.0 should never have had a
problem building on 12.1.
You're right ... there we go ... we built it ourselves.