On 18 Sep 2001, Craig Longman wrote:
> On Fri, 2001-09-14 at 02:40, Gordon Messmer wrote:
> > On 13 Sep 2001, Craig Longman wrote:
> >
> > > RPM build errors:
> > > File not found: /var/tmp/unixODBC-2.0.7-root/usr/bin/ODBCConfig
> > > File not found: /var/tmp/unixODBC-2.0.7-root/usr/bin/DataManager
> >
> > Those are QT UI applications. Install the qt-devel package so they can be
> > built.
>
> thanks for the reply, but these files are actually supposed to be built
> by the unixODBC, i'm pretty sure
Yes, I know. I've built unixODBC before. :)
Those applications depend on a minimum version of QT, which you probably
don't have. Check the configure script, INSTALL file, or the unixODBC web
site for more information.
I don't think you have to update QT on all of the target systems, just the
one you're building on. Those programs should come out in a different
package, which you may choose not to transfer to the target systems.
(Unless you also want to update QT there, which shouldn't be any more
trouble than installing unixODBC)
> this has happened too frequently of late. i don't have the resources to
> have my guys spend time upgrading every server every time a new release
> comes out
Nor does anyone. That's not the right solution... What you need is not
to upgrade every machine, but to have *one* machine which you can update
and build packages upon. It should run the same Dist/version as your
servers, and any packages you produce on it should update to the others
without hassle. Further, you can script the whole thing, so that your
packages are pushed from the devel machine after testing. (I do... it
kicks ass!)
> , and having had this problem numerous times lately, i have
> decided that it is finally time to bite the bullet and change
> distributions. debian appears to do everything i want, a stable set for
> the highest reliability, and a testing set containing exactly the
> programs i want which i can install on an as-needed basis without having
> to waste time trying to recompile it.
If that's the route you feel you need to take, then I wish you luck.
However, I don't think you're going to instantly solve all of your
problems. I find rpm packages far more often than .deb packages, and I
still haven't found a good resource on building deb's. (Maximum dpkg,
anyone?)
Next time you need a package that's not available for your specific Debian
version, or one with a dependancy you'll have to update (like QT >= 2.3),
I don't see how you'll overcome that more quickly on Debian than on Red
Hat.
> so, me and my company will be switching over to that over the next few
> weeks. i feel bad, as redhat does quite a bit for the linux community
> in general, but i am trying to run a business.
So am I. :)
Don't make the switch in haste. I've given Debian a go several times, and
haven't produced a working system yet :( Not everything you know about
Red Hat will transfer over directly, and "several weeks" may not be enough
time to adjust. Or it may. I don't know. :)
-MSG
--
If I had a dollar for every brain that you don't have,
I'd have one dollar. - Squidward to SpongeBob
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
