OS X Installer

Anders F Björklund afb at algonet.se
Sun Aug 2 01:43:52 PDT 2009


Michel Fortin wrote:

> Well, given that this is Mac OS X we could also put this in 
> /Library/D/dmd and /Library/D/dmd2, two directories which aren't hidden 
> by the file browser. Then put symlinks in /usr/local/bin and 
> /usr/local/lib pointing there. Users will then be able to upgrade 
> without an installer by simply replacing the folder at /Library/D/dmd & 
> dmd2 with a newly downloaded one.

That's how the zip files work, yes ? Possibly PATH instead of symlinks.

Main difference between /Library/D and ~ is that it requires "admin"
privileges while anyone can install into ~/dmd (even if not an admin)

The /usr installer for GDC requires root, so it auths as admin first.

Then again that gdc needed to be installed into system gcc locations,
so it wasn't really relocatable like the upstream tarball from dgcc.

> I think that's better than /opt, as /opt isn't present by default on Mac 
> OS X, isn't hidden by the Finder when present (contrary to all other 
> "UNIX" directories at the root) and thus would look a little out of 
> place on the hard drive. And there's already /Library/Python, 
> /Library/PHP and /Library/Ruby in that /Library directory to set a 
> precedent.

I think /Library/{Python,Perl,Ruby} are mostly used for user modules ?

The actual interpreters are normally installed under /usr or /usr/local
Possibly symlinked, in case of a framework installation (like Python's)

You could also use the /Developer hierarchy for installing compilers.

But I would use a "commandline" directory for a commandline tool, rather
than having it Finder-browsable. It might make sense for docs and such.

--anders



More information about the Digitalmars-d mailing list