i386 doesn't NECESSARILY mean anything, but it is supposed to mean that the code was compiled specially for the i686 architecture. As for SuSE RPMS, there is a very slim chance that SuSE RPMs will work on Caldera. SuSE sticks nearly ALL their stuff in different places as opposed to the RH/MDK/COL crew which generally put things in somewhat similar places. I still compile and RPM for each distro I use. It's just cleaner and I know what I did. eg. MDK doesn't have most of the development libs installed by default that COL does, so if I compile something on COL, I might be able to compile in LDAP and SSL functionality which might not work on MDK. This is why I personally find very little use for RPMFIND...
On Thu, 23 May 2002 05:39:17 -0400 "dep" <[EMAIL PROTECTED]> wrote: > begin Keith Antoine's quote: > > | One point and I have seen chatter about it before BUT: What > | difference would an i386.rpm have to an i686 and would it be best > | to do them as i386? Suse rpms will install with Caldera, won't they > | ? > > i686 stuff is (supposedly) optimized for later chips and won't run on > earlier ones; the lowest common denominator is i386. and suse rpms > might or might not work, depending on where suse puts stuff compared > to where ed 2.4 did. among the leading differences is /etc/. > -- > dep > > http://www.linuxandmain.com -- outside the box, barely within the > envelope, and no animated paperclip anywhere. > _______________________________________________ > Linux-users mailing list - > http://linux-sxs.org/mailman/listinfo/linux-users > Subscribe/Unsubscribe info, Archives,and Digests are located at the > above URL. _______________________________________________ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
