[haiku-web] Re: Reviewing/Updating/Combining howto guides for building/installing Haiku
- From: Matt Madia <mattmadia@xxxxxxxxx>
- To: haiku-web@xxxxxxxxxxxxx
- Date: Fri, 1 May 2009 22:39:46 +0000
On Tue, Apr 28, 2009 at 9:13 PM, Jorge G. Mare <koki@xxxxxxxxxxxxx> wrote:
> Ditto to this. Propose a breakdown of the guides that you want, and I
> will try to configure the website accordingly.
How to prioritize the presentation
currently, the four main points : About, Building, Installing,
Contributing, are chronologically sorted for someone wanting to do
everything from scratch. This requires people to skip over parts they
aren't interested in.
It's been pointed out that sorting it for a general user or young
developer may prove to be more attractive, warming, inviting. eg,
About, User Guide, TryIt-TestIt-InstallIt (from easiest to most
complex methods), Where to get Software, Where & How to Develop
3rdparty software, Develop Haiku itself.
On another note, it's been pointed out, that we should simply focus on
just the Building Haiku & Installing Haiku sections, as that is the
highest priority right now.
My intention for listing *all* possible documents is simply to be thorough.
Haiku's Design Goals
"Inspired by BeOS" vs. "*is* BeOS"
Not linux, not BSD. why not?, linux is l33t!
Human Interface Guideline
sensible defaults, limit options.
*note, most of this is currently in /about or faq or can be added to them.
Building Haiku From Source
Pre-requisite software
Getting source code
Configuring & building
building from external object directory
configure options
build profiles, UserBuildConfig
editing the code to enable/disable components
-aag, ata vs ide driver, debugging
jamming
-command options : -q, -a, -j#
-build targets: @alpha-raw, haiku-cd, ...
Installing Haiku
Preparing partitions
*This is where my mind enters a cyclic dependency.
I'm not sure how to break up the documents for Installing from
and
Installing to
Install From
Source
ImageFile
Haiku
cross-compile environment
BeOS/Zeta
Install To:
USB, ImageFile for virtualization, CD, HardDisk
Booting
When makebootable, makebootabletiny is needed
Bootman
Configuring Grub
XOSL--as easy to configure alternative
Virtualized
Qemu
VMWare
others
Known workrounds/limitations for various hardware (?)
Contributing to Haiku
Bug Tracker
sample of verification email that gets in spam
reporting bugs
limitations of bugtracker
Creating Patches
Submitting Patches
Source Repository Commit Access
Working on 3rd party software -- what the sites focus on, why you
want to use them.
HaikuPorts
OSDrawer
Sites to upload software
Creating an OptionalPackage,
Writing Documentation
Offering IRC+Email support
Distributing Haiku
Distribution Guidelines
TODO: Sort the following.
linking to the userguides & other documentation in SVN
"Browse with HTTP" seems to be fast enough.
http://svn.berlios.de/svnroot/repos/haiku/haiku/trunk/docs/
Welcome to Haiku!
Haiku User Guide
GCC2 vs GCC4 vs GCC2hybrid vs GCC4hybrid
which optional packages are gcc independent
the pros and cons of each
gcc4 -- less stable, due to being newer.
current issues with hybrids
-issue with Translators for eg, presenting gcc4 Translators to
gcc2 programs
Source repository layout
API & other programming documentation
Coding Guidelines
Icon Guidelines
HIG
Mailing Lists
nettiquette
mention what type of discussions is appropriate for each list
no attachments.
IRC Channels
nettiquette
haiku.pastebin.com
more than 1 word per line.
NO CAPS
echelog, who and what it is.
#haiku = general chat
#haiku-dev = programming questions, not using build system.
#haiku-web
locale-specific channels, #haiku-au, -br, -de, -es, -fr, -jp, -it
#haiku-support = web based IRC ... ToBeImplemented
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List
Other related posts: