Closed Bug 61832 Opened 24 years ago Closed 24 years ago

xmlterm: xmlterm scripts use fixed path to perl

Categories

(Core :: XML, defect, P3)

defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: roland.mainz, Assigned: svn)

Details

mozilla/extensions/xmlterm/scripts/xls & co. do use a fixed path to the perl interpreter (like #!/usr/bin/perl). Unfortunately on some systems perl is only available in /usr/local/bin/perl or in other locations - which causes that xls&co. do not work on such platforms. (Off-topic: Isn't there a BugZilla component for XmlTerm ?)
Reassigning to xmlterm module owner.
Assignee: heikki → svn
I'm aware of the problem, but it is not specific to xmlterm. It is the problem of running scripts under Unix, where there is no registry as in Windows. I'm not aware of any general solution to the problem. xls & co are simply perl scripts executed by whatever Unix shell you are running. Do you have any suggested solutions? Would changing the first line of xls & co to #!/bin/env perl improve things?
Nice solution (never saw this before)... -- snip -- #!/bin/env perl -- snip -- would work (but now my desktop does not recognize these scripts as perl-scrips anymore... ;-( ). I think we could either use this as a workaround or tell those people to link /usr/local/bin/perl to /usr/bin/perl (does anyone know if that works without problems (perl libs/modules not found etc.) ?). Best solution would be to add this to "configure" and let the Makefile "build" the scripts which the correct location of the "perl" binary...
Marking bug as wontfix as there is no easy workaround for the lack of a centralized registry on Unix.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
QA Contact: petersen → rakeshmishra
You need to log in before you can comment on or make changes to this bug.