Bug 9775 - Navigator is registered as Communicator via vreg
Summary: Navigator is registered as Communicator via vreg
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: netscape   
(Show other bugs)
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-02-25 09:31 UTC by Moritz Barsnick
Modified: 2014-03-17 02:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-03-20 17:27:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Moritz Barsnick 2000-02-25 09:31:06 UTC
I don't really know whether the "registration" via "vreg" is of any
importance, but:

In netscape-4.7-6, registration is done for the netscape-communicator
binary, even when packaging the netscape-navigator:

--snip from spec file--
echo 'Communicator,,/usr/lib/netscape' > /tmp/infile
./vreg $RPM_BUILD_ROOT/usr/lib/netscape/registry /tmp/infile

This "registry" file is then packaged into netscape-common.

According to the README.install in the new 4.72 Navigator tar.gz, the
registration string should be something like

BTW, IMHO, "/tmp/infile" should either have some more unique filename, or
be in $RPM_SOURCE_ROOT or the likes. (e.g.

On another note, I would "install -m755" vreg instead of "cp -a"ing it. But
who really cares...

Comment 1 Bill Nottingham 2000-02-25 15:12:59 UTC
AFAIK, it doesn't affect anything. We could move it
to the -communicator/-navigator subpacakges, but then
that would mean they would conflict with each other
if you had both installed.

Note You need to log in before you can comment on or make changes to this bug.