Portability in dpkg is very important, to be able to support downstreams and people who use it on other systems, or even package it in other (non-GNU/Linux) distributions. But currently porting to many of those is done purely through documentation, so catching build or run-time issues is clearly a reactive process, although it would be nice to switch to a more proactive model.

So it would be very much appreciated if either interested parties could provide access to such systems, or setup some kind of continuous integration system from git. Barring anything else, sending build and test suite success or failure reports from time to time would be also appreciated.

Please get in contact with the mailing list or IRC channel if you can offer resources (or privately to GuillemJover if you'd rather remain anonymous).

The following systems are of particular interest:

System

Resource

Sponsor

non-glibc Linux

{X} none

Mac OS X

(./) ssh access

Justin F. Hallett (on behalf of the Fink project)

Solaris

{X} none

illumos

(./) ssh access

Igor Kozhukhov (on behalf of the DilOS project)

FreeBSD

(./) ssh access

Jesse Smith (on behalf of DistroWatch), GCC Compile Farm

NetBSD

(./) ssh access, local VM

GCC Compile Farm

OpenBSD

(./) ssh access, local VM

GCC Compile Farm

Minix

(./) local VM

Haiku

(./) local VM

HP-UX

{X} none

AIX

(./) ssh access

GCC Compile Farm

Teams/Dpkg/Porting (last modified 2017-05-27 21:26:09)