First questions...

Syd Polk
Mon Aug 7 10:58:00 GMT 2000

At 06:27 PM 8/7/00 +0200, Thomas Heller wrote:
> > >    It also installs a TON of executables in the main bin dir.  Why not
> > >    have it install them in its own share/SN/bin dir and add the path
> > >    the main executable is loaded?
> > >
> > > What you are suggesting doesn't conform to the GNU directory layout.  If
> > > there are a lot of executables in the bin/ directory, perhaps we need to
> > > look at moving them to libexec if they aren't programs that a user would
> > > invoke directly themselves.
> >
> > The problem with that is that making a libexec directory makes it really
>hard to
> > launch from Windows. It makes it necessary to put some of the sourcenav
> > directories on the path. It is not really feasible.
>Would not a key in the registry under
>"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths"

The only registry entries that SN makes right now are setting up the Start 
Menu. The actual exe does not depend on any path or registry values. This 
means you can move SN around to anywhere on your file system.

In general, after 12 years of Windows programming, I really want all of my 
.exe and .dll files in the same directory. It just makes things so much easier.

Syd Polk
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.

More information about the Sourcenav mailing list