Source: dh-r
Standards-Version: 4.7.4
Maintainer: Debian R Packages Maintainers <r-pkg-team@alioth-lists.debian.net>
Uploaders:
 Gordon Ball <gordon@chronitis.net>,
 Andreas Tille <tille@debian.org>,
 Dylan Aïssi <daissi@debian.org>,
 Charles Plessy <plessy@debian.org>,
Section: science
Build-Depends:
 debhelper-compat (= 14),
Vcs-Browser: https://salsa.debian.org/r-pkg-team/dh-r
Vcs-Git: https://salsa.debian.org/r-pkg-team/dh-r.git
Rules-Requires-Root: no

Package: dh-r
Architecture: all
Depends:
 ${misc:Depends},
 r-base-dev,
 debhelper (>= 9),
 dctrl-tools,
 libconfig-properties-perl,
 libfile-which-perl,
 libswitch-perl,
 libwww-curl-simple-perl,
Recommends:
 devscripts,
 cme,
 git-buildpackage,
Suggests:
 postgresql-client-common,
Description: Debian helper tools for packaging R libraries
 Provides the R package buildsystem for debhelper.
 .
 Additional tools:
 .
  dh-make-R:       generate packaging skeletons for R packages
  dh-update-R:     update (versioned) dependencies of R packages,
                   Vcs-fields and Maintainer field

Package: pkg-r-autopkgtest
Architecture: all
Depends:
 ${misc:Depends},
 dctrl-tools,
 r-base-dev,
Description: Script for the automatic testing of R packages
 This package contains the pkg-r-autopkgtest script that runs the unit tests
 contained in the source tree from which it is launched. It is intended to be
 used by the support for R packages, which is implemented in autodep8.
 .
 Packages using the tests with autopkgtests in this package need to
 simply set "Testsuite: autopkgtest-pkg-r" in debian/control.

Package: r-pkg-team-core-architecture
Architecture: amd64 arm64 loong64 ppc64el riscv64
Depends:
 ${misc:Depends},
Description: Architecture gatekeeper for R packages in Debian
 The r-pkg-team-core-architecture metapackage defines the set of architectures
 supported by the Debian R Packaging Team. Most r-cran-* packages and all
 r-bioc-* packages depend on it, ensuring that the R ecosystem in Debian is
 redistributed only on architectures that have undergone proper evaluation
 and testing.
 .
 The restriction exists because historically many porting issues could only
 be addressed by the Debian R Packaging Team by disabling regression tests,
 resulting in reduced quality, increased patch maintenance, and disruptions
 during routine updates. Exceptions exist for core service packages central
 to the R dependency graph or for packages maintained by teams with a strong
 record in software engineering (e.g., rlib).
 .
 We ask porters who wish to redistribute the full R package distribution on a
 new architecture to first build and test the full package set outside the main
 Debian archive, using a custom r-pkg-team-core-architecture package. Please
 aggregate the results, identify the main classes of failures, and coordinate
 with the wider R community and the Debian R packages team so that most issues
 can be resolved upstream before enabling redistribution in Debian.
 .
 Main benefits:
 .
 o For users: ensures that any distributed r-cran-* or r-bioc-* package meets
   the same quality standards as on mainstream amd64 and arm64 architectures.
 .
 o For porters: provides control over when to invest effort in porting R
   packages, enabling better prioritisation.
 .
 o For the Debian R Packages Team: reduces patch burden and improves control
   over time spent on porting‑related issues.
 .
 o For the Release Team: reduces delays in testing migration and transitions,
   and increases the quality of the Stable release.
 .
 o For the R community: encourages organised, focused reporting of
   architecture‑specific issues.
 .
 o For the broader Linux ecosystem: prioritises upstream fixes, benefiting
   other distributions as well.