Heikki Toivonen wrote:
>
> I somehow find the software hierarchy odd... And I
> would expect build instructions on the dev hierarchy.
Build instructions are more closely associated with
download/installation than with the developing the
software's internals IMO. Remember, mozilla.org
produces source. Thus building is a regular part of
acquiring the software.
/dev isn't targeted at someone who's just going to
download and use the source as is, and non-developers
shouldn't need to wander around in there to look for
build instructions.
One could argue that building is a regular part of
development, too, but that doesn't apply to modifying
the chrome. In any case, developers, like anyone else
getting Mozilla by source, still have to download,
build, and install the software. So, like everyone
else, they can get all the instructions for doing that
from the same place.
> Should there be download hierarchy for readily
> available binaries and other products?
This is what /software is for--acquiring software.
Source and/or binaries.
