The RPMS installation issue is fixed in the new release. The RPMS are called
opendx-4.0.10-1.i386.rpm opendx-docs-4.0.10-1.i386.rpm rpm -q now will show opendx-4.0.10-1 and opendx-docs-4.0.10-1 (according to RedHat RPM conventions). If you downloaded using Netscape, then you may consider configuring the Netscape for RPM downlaod under Edit prefereces. Suhaib Peter Denisevich wrote: > Suhaib, > > Thanks for all your work on Linux. I just want to confirm that the CVS > (mine is Jan 28) source builds under RH6.1 without the interactor > problem -- no environment variables needed to be set. I would still > like to use your rpms as they seem to have more complete modules built > in (e.g. BSpline) than what I get from the CVS files. The comments > below about rpms and install locations seem valid to me, too. An > additional problem with some of the distributions comes from changing > the install locations (/usr/.. or /usr/local/..): it's really easy > for someone like me to end up with multiple versions of DX and get > really confused as to which version has which problems, etc. > > My plan is to try to work through as many of the samples as I can, > noting which ones do and don't work -- I get frequent server disconnects > with some of them, too. I'll try to compile a list of the results. > > BTW - I downloaded a copy of your rpm yesterday (2/17) but it seems to > be corrupted -- rpm won't query it or install it. It's probably just a > bad download -- the phone system at Stanford yesterday was all fouled up > -- calls to 415-555-1212 directory assistance went to Phoenix... ;-) > > Suhaib Siddiqi wrote: > > > David, > > Thanks. i will have patched binary ready sometimes duyring next > > week. > > > > Suhaib > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] Behalf Of David > > > Thompson > > > Sent: Thursday, February 17, 2000 2:42 PM > > > To: [email protected] > > > Subject: Re: [opendx-dev] RE: problems with OpenDX RPM files > > > > > > > > > Suhaib, > > > > > > The fix is actually with adding a command line option to > > > your compiler for > > > Linux. I deduced that trunc did not work right when > > > linked with 4.0.10. In > > > order to link properly, -D_GNU_SOURCE must be added to > > > the compile lines > > > to get it to function. I've added the check for this in > > > configure so the > > > cvs version now does this correctly. > > > > > > David > > > > > > On Thu, 17 Feb 2000, Suhaib Siddiqi wrote: > > > > > > > > > > > > > > > Thanks, I will incorporate suggestions into RPMS spec files. > > > > > > > > Regarding bugs of interactor and steppers: I was > > > unable to find a > > > > fix in DX code... and I am not sure where in the MOTIF > > > code I should > > > > look. > > > > > > > > Suhaib > > > > > > > > > > > > > -----Original Message----- > > > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > > > > > Behalf Of Douglas N. Arnold > > > > > Sent: Thursday, February 17, 2000 1:19 PM > > > > > To: Suhaib M. Siddiqi > > > > > Cc: [email protected] > > > > > Subject: problems with OpenDX RPM files > > > > > > > > > > > > > > > > > > > > I just installed the opendx RPMs from opendx.org on > > > my RedHat 6.1 > > > > > machine. Thanks for making RPMs available! However > > > I did come > > > > > across some problems I wanted to let you know about. > > > > > > > > > > 1. There still seems to be an interactor problem. Dials > > > > > and steppers > > > > > don't work. > > > > > > > > > > 2. There is also a small bug. The rpm installs into > > > /usr, but the > > > > > script /usr/bin/dx and script in /usr/dx/bin still > > > > > specify the prefix > > > > > /usr/local. > > > > > > > > > > 3. Finally, I wanted to mention that your naming > > > > > conventions are not > > > > > usual for RPMs and cause some problems. You associated > > > > > the following > > > > > names to the RPMs (in the spec file, I imagine): > > > > > > > > > > OpenDX > > > > > opendx-4.0.10-redhat-6.x-linux-docs > > > > > > > > > > The second name is surely not right. The version > > > number 4.0.10 is > > > > > separate from the name. If I ask my system to list > > > my installed > > > > > rpms (rpm -qa), it now gives the redundant info > > > > > "opendx-4.0.10-redhat-6.x-linux-docs-4.0.10-1". > > > > > > > > > > I would suggest names > > > > > > > > > > opendx > > > > > opendx-docs > > > > > > > > > > for the two RPMs. Of course the version number would be > > > > > 4.0.10 and the > > > > > release number 1 (or 2). Then, conventionally, the name > > > > > of the rpm > > > > > files would be name-version-release.i386.rpm, i.e., > > > > > > > > > > opendx-4.0.10-1.i386.rpm > > > > > opendx-docs-4.0.10-1.i386.rpm > > > > > > > > > > These names, especially the one associated to the RPM > > > in the spec > > > > > file, are important, since to query the rpm the user must > > > > > supply the > > > > > name. E.g., if I want to find out what opendx docs there > > > > > are I would > > > > > type, under my suggested scheme, > > > > > > > > > > rpm -ql opendx-docs > > > > > > > > > > It would be tough for me to remember your long name and type > > > > > > > > > > rpm -ql opendx-4.0.10-redhat-6.x-linux-docs > > > > > > > > > > By the way it is possible to put OS information in the > > > > > release number, > > > > > like 1rh6.1, if you insist, but it is not usually done. > > > > > > > > > > > > > > > > > > > > > > ---------------------------------------------------------- > > > ---------- > > > David L. Thompson e-mail:[EMAIL PROTECTED] > > > University of > > > Montana/CS Department > > > Missoula, MT 59812 > > > Work Phone : > > > (406)243-4793
