[Bioc-devel] Shouldn't we distinguish between package-specific and dependency errors?]

Philipp Angerer philipp.angerer at helmholtz-muenchen.de
Fri Sep 25 09:27:13 CEST 2015

On Thursday 24 September 2015 19:54:04 Ludwig Geistlinger wrote:
> Well, I guess, Dan, that basically means that breaking cannot happen
> within Bioc (as broken packages do not propagate to the repository) and
> such cases are exclusively due to breaking of external dependencies such
> as observed with KEGGREST and KEGG (where we can hardly do much about 
> Thus, it remains to clarify on the purpose of the “build” shield as
> Wolfgang pointed out.
> While it is surely helpful for the developer to grasp what is going on at
> a glance, this might be misleading for users and reviewers as described
> earlier.
> Ludwig

The build sheet isn’t completely indicative of a package being good to go or 
not: As the team has assured me, builds failing because the “perceval” 
machine can’t handle C++11 are no problem.

Best, p
Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
Aufsichtsratsvorsitzende: MinDir'in Baerbel Brumme-Bothe
Geschaeftsfuehrer: Prof. Dr. Guenther Wess, Dr. Nikolaus Blum, Dr. Alfons Enhsen
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671

More information about the Bioc-devel mailing list