Unix Ports and more

This will become the home of all diffs for known Unix ports and also for other ports. The reason we did that is, because is't almost not possible to keep track of the different pages where people provide ports.

Structure

Every port has to be listed at the available ports section below. At a seperate page the app has to be explained (including how to patch and how to build). See explain for how such a page should look like. Every checkin or change to the wiki needs a comment. In the comment the port needs to be included like: "portxy: some comment about what was changed".

Setting up a build env

To start building unix ports we recomend to download Pauls build env ​http://os2ports.smedley.info/index.php?page=build-environment. Just follow the instructions on the above page. We try to create a more flexible gccxxx.cmd in the future, as the provided is a bit unflexible. If you decided to unzip the build env to another drive than u:, then replace all u: in the instructions as well as in gcc335.cmd with the drive you unzipped the build env.

Available ports

• Boost version 1.40.0
• libtorrent version 0.14.12
• djvulibre version 3.5.23
• libjpeg version 8
• lzo version 2.03
• openvpn version 2.1.3
• bzip2 version 1.0.6
• readline version 6.1
• ncurses version 5.7
• gzip version 1.4
• popt version 1.15
• sqlite version 3.7.2
• glib version 2.25.15
• pkgconfig version 0.25
• file version 5.0.4
• cpio version 2.11
• xz version 4.999.9beta
• xml2 version 2.7.7
• curl version 7.21.1
• mmap version 20100929
• pthread version 20100929
• openssl 1.0.0a
• tar 1.2.3
• mercurial 1.6.3
• zip 3.0
• unzip 6.0
• clamav 0.96.4
• coreutils 8.6
• check 0.9.8
• m4 1.4.15
• autoconf 2.65
• poppler 0.14.2

Reporting Bugs

Reporting bugs and requesting new features is done through the ticket system. You can view existing tickets, add comments to them and create new tickets using the corresponding buttons at the top of every page. If you want to submit a new bug or request a feature, please use the Search function first to make sure there is no ticket for this task already created.

Anonymous access to the ticket system has been restricted due to multiple attacks of stupid spammers we've been suffering from during the last month. In order to create a new ticket or comment the existing one, you need to login with your Netlabs login id. If you do not have a login id, you can request one at ​http://www.netlabs.org/en/site/member/member.xml. We are sorry for inconvenience, but at the present time this is the only way to avoid extremely annoying spam.

Credits

• Yuri Dario
• Paul Smedleys
• Herwig Bauernfeind
• Silvan Scherrer

• netlabs.org (hosting & support)

• all the companies and developers from where we ported

Screenshots