Opened 10 years ago

Closed 10 years ago

#779 closed defect (fixed)

wvware.pl script to launch wvware in correct env

Reported by: ak19 Owned by: ak19
Priority: moderate Milestone: 2.85 Release
Component: GLI Severity: major
Keywords: Cc:

Description

On Ubuntu, GLI's file associations like evince %1 and gedit %1 all fail to work since LD_LIBRARY_PATH has been set globally with setup.bash so that wvware can use gnome-lib libs. These libs are, however, incompatible with Ubuntu's inbuilt versions of its GUI libraries. These GUI libraries are needed for gedit, emacs, evince and the rest to display their GUI windows.

Since only wvware really needs the LD_LIBRARY_PATH set to these different libraries, the idea is to no longer have setup.bash set this env variable for all of Greenstone and GLI, but to instead launch an intermediate file wvware.pl instead of a direct executable. The wvware.pl will launch the wvware executable after setting the LD_LIBRARY_PATH to what wvware needs. This will then restrict the env that wvware requires to itself instead of forcing all of Greenstone and GLI to be stuck with the same environment. (At present running setup.bash in an x-term means we can't run evince or gedit or emacs on a file from that same x-term, for the same reason that GLI's file associations also fail to launch registered programs.)

Change History (7)

comment:1 by ak19, 10 years ago

Milestone: 2.85 Release

comment:2 by ak19, 10 years ago

wvware.pl will need to check for the existence of GSDLHOME (die otherwise) and run wvware.

Further issues: Some Linux machines require gnome-lib-minimal to compile wvware. Eg. Ubuntu, Mac.

On these machines, still get gnome-lib-minimal. The configure and compile cycle requires you to "source devel.bash" from ext/gnome-lib-minimal, as usual. However, we must ensure that the setup.bash files in the various versions of the gnome-lib-* packages in trac do not get run when Greenstone's main setup.bash is sourced: running a gnome-lib setup.bash is what messes up the environment.

  1. Need the Greenstone 2 (and gs2build) top-level setup.bat and setup.bash files to ignore calling the gnome-lib(-minimal)'s setup.bat/bash files when cycling through the packages in the ext folder.
  1. In wvware.pl, need the perl code to set the env to the same thing as what the gnome-lib setup.bash and .bat files do.
  1. wvware.pl should call wvware after setting the environment. And it should work from the command line and for replace_src_doc_with_html, and still work on Windows too.

comment:3 by ak19, 10 years ago

Renamed setup.bat and setup.bash files in http://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk/src and the tar.gz files in its trunk area.

This ticket is now essentially closed.

Still need to test greenstone2/setup.bash works as greenstone3/gs2build setup.bash and then commit the bash and bat file versions using the svn:externals command so that all Greenstone toplevel setup scripts become equivalent.

comment:4 by ak19, 10 years ago

Resolution: fixed
Status: newclosed

Changesets for wvware.pl, gsConvert.pl and changes to gnome-lib (whose setup scripts have been renamed to _old suffixes): revisions 24371 and 24376-24378.

GS3\gs2build's setup.bash, setup.bat, setup.csh have been removed, with the svn:external property on the gs2build folder set to point to these setup scripts in greenstone2. Revisions: 24381-24385.

comment:5 by ak19, 10 years ago

Resolution: fixed
Status: closedreopened

comment:6 by ak19, 10 years ago

Owner: changed from nobody to ak19
Status: reopenednew

comment:7 by ak19, 10 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.