install 'qtide' replaced my jQt binaries fine. It may be that I last time I tried this the first time with the jqt still running. That meant that although the test to see if it is possible to write to the ~bin directory passed, when it actually came to replacing the files already in use, that failed. The script doesn't actually check to see if the files get changed and therefore reports success. Adding a check to see if jqt is running, before updating might work?
On Tue, Mar 19, 2013 at 3:38 PM, Ric Sherlock <[email protected]> wrote: > I agree. Last time I upgraded my jqt binaries I ended up manually > installing them because I couldn't seem to get them to overwrite the > existing ones. I have my Windows j8 install in c:\Program > Files\j64-801, and my Linux one in /opt/j64-801. Both need admin > permissions to write to, which may complicate things. > > I can't be absolutely certain I didn't make a stupid error though so > I'll test it out with more care tonight (I see that there are new > binaries available!) > > > On Tue, Mar 19, 2013 at 11:43 AM, chris burke <[email protected]> wrote: >> On Tue, Mar 19, 2013 at 3:39 AM, Ric Sherlock <[email protected]> wrote: >> >>> ... >> >> Looking at the code in install and getqtbin, it may be that in some >>> instances, where old binaries already exist, they aren't being >>> replaced by the new versions. You could try deleting/renaming/moving >>> ~bin/jqt.exe and ~bin/jqt.dll before you run ( install 'qtide' ). >>> >> >> Do you have an example of this? It should not be necessary to delete the >> old jqt binaries first. >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
