#15392 closed enhancement (fixed)
Guide and install.php should be synced and subversion installs expanded
| Reported by: | wsiegrist@… | Owned by: | wms@… |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | guide | Version: | |
| Keywords: | guide documentation website | Cc: | ryandesign (Ryan Carsten Schmidt) |
| Port: |
Description
The installation instructions in the guide should be synced with whats in install.php. Also, the instructions for subversion installs should make it obvious which step in the source install to go to after the checkout (only) step is performed from install.php. The guide does not mention installing from an svn checkout at all.
Change History (6)
comment:1 Changed 17 years ago by markd@…
comment:2 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
| Milestone: | → Website & Documentation |
|---|
There are instructions for building MacPorts from the Subversion trunk in the wiki howto page RunningTrunk. Perhaps that could be used as the basis for the new Guide information.
We sorely need a single document for installation instructions. I wouldn't even mind if install.php were nothing but a single sentence directing people to the relevant page in the Guide.
See also #17359.
comment:3 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|
comment:4 Changed 16 years ago by wsiegrist@…
r44116 added the new section to the guide. I think we should leave the "Keeping up to Date" section in HOWTO, and replace the top half with a link to the guide. Then we can replace the section in install.php with a link to the guide.
comment:5 Changed 16 years ago by wsiegrist@…
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I removed the obsolete sections from the HOWTO and install.php. See r45346 and the wiki change.
comment:6 Changed 16 years ago by (none)
| Milestone: | Website & Documentation |
|---|
Milestone Website & Documentation deleted
I'd favor rolling the "other platforms" information into a separate html page that is linked in both docs, since the readership is small it should not be obtrusive, and it also provides a single source. The install section of the guide does need info on subversion installs. It could easily be tucked into the "source installs" section. I'll add something for that in the next few days. If we could agree on when we have an adequate guide install section, perhaps we could just transform the xml of the guide's install section into install.php, thereby also giving a single source.
I think install.php has too much information subject to change (v2.4.1, v 3.0, "Panther PPC", etc) that can be simplified ("latest Xcode _here_"). But then I wrote the install section of the guide and so I'm not an unbiased observer. I favor a minimalist approach, and some questions will always have to be answered by the mailing list anyway.