Thanks, Ben. Sounds like I'm going to need to rethink a few things to
make sure --libdir works sanely. I can imagine how it may work correctly
right now from a source-only installer. rustc may need some tweaks to
make it work more generally.
On 03/22/2014 11:49 AM, Ben Noordhuis wrote:
On Sat, Mar 22, 2014 at 12:55 AM, Brian Anderson bander...@mozilla.com wrote:
I'm in the process of rewriting most of the installation code and I'm at the
point where it's almost done, and I'm looking at the options to configure
that affect installation destinations and wondering which really must be
implemented.
configure supports a variety of standard options that impact install
directories, most of which we ignore because we have nothing to put into
them, and some of which just can't work currently given Rust's installation.
The relevant options that might affect Rust's installation are:
--mandir - changes where man pages go
--libdir - changes where libraries go
--rustlibdir - changes the *name* of rust's own directory under lib/
First of all, having `--rustlibdir` as an option is probably just wrong and
I don't intend to support it; I don't see any reason to make this
configurable.
Changing `--libdir` will almost certainly make rustc break since it depends
on being able to find the lib directory as a relative path from the bin
directory.
Packagers will be unhappy about the absence of a --libdir switch. For
example, x86_64 Fedora requires that normal libraries are installed to
/usr/lib64, not /usr/lib.
Finally, `--mandir` is an option that I suspect *actually works* in the
current implementation, but I don't know if there's any reason ever to not
install to `share/man`.
FreeBSD? It has man pages in /usr/man rather than /usr/share/man.
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
