Changes between Version 11 and Version 12 of WikiStart
- Timestamp:
- 08/16/07 07:56:55 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v11 v12 1 1 == Welcome to !BePorts == 2 2 3 !BePorts is a centralized collection of software ported to the [http://en.wikipedia.org/wiki/BeOS BeOS] / [http://haiku-os.org/ Haiku]. Each port contains the BeOS-specific patches to the original source code. The BePorter tool is provided to ease the fetching and patching of source code. Along with a [SubversionRepository Subversion repository] to store all patches, this Trac site eases cooperation on porting efforts. There is also a [MailingList mailing list] for the discussion of the project.3 !BePorts is a centralized collection of software ported to the [http://en.wikipedia.org/wiki/BeOS BeOS] platform. Each port contains the BeOS-specific patches to the original source code. Along with a [SubversionRepository Subversion repository] to store all patches, this Trac site eases cooperation on porting efforts. There is also a [MailingList mailing list] for the discussion of the project. The BePorter tool is provided to ease the fetching and patching of source code. 4 4 5 5 == Objective == 6 6 7 The main objective of the !BePorts project is to centralize ports of software to the BeOS / Haiku. This avoids reinvention of the wheel when the person that ported the previous version of a software package didn't provide a patch and seems to have disappeared from the face of the earth.7 The main objective of the !BePorts project is to centralize ports of software to the BeOS platform. This avoids reinvention of the wheel when the person that ported the previous version of a software package didn't provide a patch and seems to have disappeared from the face of the earth. 8 8 9 Also, solutions to problems faced when porting one application can be valuable for porting another. For this purpose, the Trac tickets and the CommonProblems page can be consulted when facing problems. Moreover, the Subversion repository and the Trac site ease cooperation on porting efforts. A history of changes to a BePort is kept in it's PortLog.9 More importantly, solutions to problems faced when porting one application may be valuable when porting another. For this purpose, the PortLog, Trac tickets and the CommonProblems page can be consulted when facing problems. To make this work, some [wiki:Guidelines] should be followed. 10 10 11 11 BePorter can be compared to a slim version of [http://www.gentoo.org/main/en/about.xml Gentoo Portage]. It fetches the original source code, applies the BeOS-specific patches, builds, and optionally installs the port. This package management aspect, however, is by no means the essence of the !BePorts project. 12 12 13 == Platforms == 14 15 Unfortunately there are a number of differences between the various BeOS platforms: R5, BONE, Dano0, Zeta and now [http://haiku-os.org/ Haiku] when porting software. A BePort should ideally build on all of these. While the older platforms are still of importance now, focus will eventually shift to Haiku as it matures. 16 13 17 == Getting Started == 14 18 15 To install the !BePorts system on your BeOS or Haikuinstallation, see [wiki:Installation].19 To install the !BePorts system on your BeOS installation, see [wiki:Installation]. 16 20 17 If you want to have a short at porting an application yourself, first read the PortingTips. 18 19 For information on how to add a BePort to the tree, see AddingPorts. 21 For information on how to add a BePort to the tree, see AddingPorts. Don't forget to read the [wiki:Guidelines]. 20 22 21 23 ----
