Le Wed, Apr 06, 2011 at 10:53:55PM -0700, Russ Allbery a écrit : > > However, is the control file really the right place for that? I guess we > don't have a better place right now, but this doesn't feel like package > metadata that needs to be put into the Sources file.
Hi, there is my pet project about upstream metadata: http://wiki.debian.org/UpstreamMetadata The key concept is to store ‘Field: value’ data in a file called debian/upstream-metadata.yaml, and to access it from the VCS where the package is stored (that is, not from the source package itself). This allows: - To update the data without uploading the package; - to distribute a reasonnably up-to-date copy with our source packages. I have not yet found time to push for finishing the proof of principle, which is to collect bibliographic information for the Blends websites through that system via the UDD, but it would be straightforward to use it right now for packages managed in Git and Subversion. Adding support for other VCSes should be trivial. For packages that are not managed in a VCS, I think that the most realistic solution would be to maintain the metadata in a special flat file on collab-maint. (And I also support deprecating the non-use of VCS for managing source packages). The biggest difficulty would be to agree on field names. The best would be to be compatible with some pre-existing RDF ontologies, like DOAP. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110407081113.gd9...@merveille.plessy.net
