[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#694326: ITP: perl-cross-debian -- Cross build support for Debian perl configurations



Package: wnpp
Severity: wishlist
Owner: Neil Williams <codehelp@debian.org>

* Package name    : perl-cross-debian
  Version         : 0.0.1
  Upstream Author : Neil Williams <codehelp@debian.org>
* URL             : https://github.com/codehelp/perl-cross-debian
* License         : GPL
  Programming Lang: Perl
  Description     : Cross build support for Debian perl configurations

 This package provides the configuration values for selected
 versions of perl, compatible with the Debian configuration of
 that version of perl, to avoid detection of these values during
 a cross-build.
 .
 Also provides a helper script to push the relevant configuration
 files into the cross-build using support in debian/rules within
 perl.

<end of long description>

Notes for debian-devel readers:

The homepage links to the initial ideas for this package on my
blog and I'll add more as the package develops. This package
requires some changes in perl upstream and in the Debian perl
package - details of those changes will be finalised prior to
upload of this package to experimental.

The intent is that this package will have a strict dependency on
the latest version of perl which is supports or any lower version
so that the version of perl in Debian testing should always cross
compile for the list of supported architectures.

Initially, the only supported architectures in perl-cross-debian
will be armel and armhf with expected support for arm64. Join the
team to support other architectures.

The cross-build support in this package is specific to the Debian
configuration of the specific version of upstream perl on the
supported architectures. All cross-builds need the full list of
build-dependencies for perl installed plus a suitable cross-compiler
(not currently in Debian) and cross-dependencies (likely via
dpkg-cross until MultiArch can handle -dev packages cleanly).


Reply to: