Bug #1212

Windows: modify installer to prepend BornAgain location to system PATH instead of appending to it

Added by pospelov over 5 years ago. Updated about 5 years ago.

Status:ArchivedStart date:15 Oct 2015
Priority:NormalDue date:
Assignee:pospelov% Done:

0%

Category:-
Target version:Sprint 29

Description

I have just discovered the user, who has 3 versions of Bornagain (1.0, 1.1 and 1.3) installed on Windows 7.
Seems that GUI is working well, but Python, naturally, always uses libraries from BornAgain-1.0 location.

How to fix:
  • modify Windows installer in such a way that BornAgain would prepend its location to the PATH, so that the last installed version always loaded first.
  • Warn user about it in installation instruction

Second possible solution: modify installer so it would suggest the user to uninstall previous version. Might be hard to achieve, consider usage of Qt installer framework.

History

#1 Updated by pospelov about 5 years ago

  • Status changed from New to Sprint
  • Assignee set to pospelov
  • Target version set to Sprint 29

#2 Updated by pospelov about 5 years ago

  • Status changed from Sprint to Resolved

#3 Updated by pospelov about 5 years ago

  • Status changed from Resolved to Archived

Also available in: Atom PDF