Last Changes

01/10/15

• BepFileProjectTargets (diff)

09/08/14

• MailingList (diff)

12/07/13

• Installation (diff)

08/26/13

• WikiStart (diff)

08/20/13

• HaikuPorterForPM/ConvertingBepToRecipe

08/14/13

• JoinHaikuPorts (diff)

07/15/13

• HaikuPorterForPM/BuildRecipes (diff)

06/13/13

• HaikuPorterForPM/HandlingRequirements (diff)

06/12/13

• HaikuPorterForPM/PortsTree (diff)
• HaikuPorterForPM (diff)
• HaikuPorterForPM/Repository (diff)

06/11/13

• HaikuPorterForPM/PortsAndPackages
• HaikuPorterForPM/Usage
• HaikuPorterForPM/HaikuPortsConf (diff)

03/30/13

• net-wireless/wpa_supplicant/2.0/1
• net-wireless/wpa_supplicant/2.0

03/07/13

• dev-qt

03/02/13

• games-engines/gemrb/0.7.2/1 (diff)
• games-engines/gemrb/0.7.2

01/27/13

• PythonRegressionTests (diff)

01/25/13

• media-libs/sdl-sound (diff)
• sys-devel/flex (diff)
• sys-devel/sparse (diff)
• dev-util/bzr (diff)
• net-misc/wput (diff)

Welcome to BePorts

BePorts is a centralized collection of software ported to the  BeOS platform. Each port contains the BeOS-specific patches to the original source code. Along with a Subversion repository to store all patches, this Trac site eases cooperation on porting efforts. There is also a mailing list for the discussion of the project. The BePorter? tool is provided to ease the fetching, patching and building of source code.

Objective

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 an older version of a software package didn't provide a patch and seems to have disappeared from the face of the earth.

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 Guidelines should be followed.

BePorter? can be compared to a slim version of  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.

Platforms

Unfortunately there are a couple BeOS platforms: R5, BONE, Dano, Zeta and  Haiku. 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.

Getting Started

To install the BePorts system on your BeOS installation, see Installation.

For information on how to add a BePort? to the tree, see AddingPorts. Don't forget to read the Guidelines! Milestone M1 lists a set of the most common/important software packages. It is recommended (recent versions of) these are ported first.

 

For questions and comments, contact brecht -at- mos6581 -dot- org