168052 - GRE enable regxpcom.exe...

Status: RESOLVED FIXED

(Core :: XPCOM, defect)

Description

[Chak Nanga]

Currently regxpcom registers components only in the "components" directory 
relative to where it's run from.

We need the ability for regxpcom to register components in a specified GRE 
directory also.

Comment 1

[Doug Turner (:dougt)]

what is wrong with what it does now?

usage: regxpcom directory-to-register
       regxpcom -u directory-to-unregister

Comment 2

[Ken]

what exactly does the -u option do? Does it delete both components.reg and 
xpti.dat? What does it do if the .xpt files are zipped up?

Comment 3

[Doug Turner (:dougt)]

>what exactly does the -u option do? 

-u calls AutoUnregister for give directory or component. 
   This calls trickes down to calling UnregisterSelf on 
   each of the give components.  AutoUnregister also
   removes all references to the given components from 
   the compreg.dat file.

>Does it delete both components.reg and xpti.dat? 
    No.  

> What does it do if the .xpt files are zipped up?
    Currently it does not touch xpt files, but this is a bug.  

Comment 4

[Chak Nanga]

Since you can currently specify just one components dir to register, that can be
used to rergister either just the applicaction specific components dir or the
MRE's components dir - not both.

Or am i still missing something?

Comment 5

[Doug Turner (:dougt)]

do you want to be able to specify multiple directories?  

Comment 6

[Chak Nanga]

I guess being able to specify multiple component dirs will probably solve the
issue of autoreg when running in a GRE based env. 

Doug : Do you think that's the way to go or are there any other approaches you'd
prefer/reccommend?

Comment 7

[Doug Turner (:dougt)]

chak, are you working on this?  If not, please reassign it to me.

Comment 8

[Chak Nanga]

->Doug

Comment 9

[Juan José Mata]

EDT triage: talked to Doug, and it seems like he needs to clean up regxpcom
before embedding clients can make effective/complete use of it.  Plussing
topembed nomination.

Doug, can you please describe the scenarios under which the current
implementation is insufficient for embedding customers which we plan on
addressing in this bug?

Comment 10

[Doug Turner (:dougt)]

the fix in bug 183075 gives you many more options.  

Usage: regxpcom [options] [file-or-directory]

Options:

-x path

Specifies the location of a directory containing the
xpcom library which will be used when registering new
component libraries. This path will also be added to
the "load library" path. If not specified, the
current working directory will be used.

-c path

Specifies the location of the compreg.dat file. If
not specifed, the compreg.dat file will be in its
default location.

-d path

Specifies the location of the xpti.dat file. If not
specifed, the xpti.dat file will be in its default
location.

-a

Option to register all files in the default component
directories. This is the default behavoir if regxpcom
is called without any arguments.

-h

Displays this help screen.

-u

Option to uninstall the files-or-directory instead of
registering them.

-q

Quiets some of the output of regxpcom

Marking as fixed.  Chak, please verify that with these options, the scenarios
you had in mind are addressed.

Comment 11

[Benjamin Smedberg]

dougt: so regxpcom will not automatically find the GRE... you need to specify -x
PATH_TO_GRE to get it working?

Comment 12

[Doug Turner (:dougt)]

regxpcom will assume the GRE is in the CWD if no GRE location is specified.