Source: python-debian Version: 0.1.30 Severity: wishlist Now that .buildinfo files are more common, it would be appropriate for a standardised library to parse them to appear in python-debian.
This can mostly be a very thin layer around the existing Deb822 types, using the existing Changes code for the file listings, the existing PkgRelations code for the package listing and gpg_* functions for signature handling. Are there any other fields that should be split/interpreted rather than simply handled as opaque data? - Environment: line split? split at = too? (how are newlines in values encoded within these environment lines?) - Binary: space split? (these are not split for .changes files) - Architecture: space split? (this is not done for .changes files) On the basis that it is much harder to change an API after it is uploaded than before, it would be great if potential consumers could make suggestions now. If existing consumers such as buildinfo.d.n already have implementations that would fit into python-debian, then even better. cheers Stuart _______________________________________________ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds