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

Re: Bug#551386: Per-package link to upstreams bugtracker

Le Sun, Oct 18, 2009 at 02:34:24PM +0200, gregor herrmann a écrit :
> On Sun, 18 Oct 2009 10:23:02 +0800, Paul Wise wrote:
> > > In order not to bloat the Packages file we where thinking about a
> > > header in debian/copyright (which has, according to DEP5, already
> > > information about the Upstream-Author and Upstream-Source).
> > I'd like to re-iterate my earlier mail on this subject about splitting
> > up the Packages file:
> > http://lists.debian.org/debian-devel/2009/08/msg00057.html
> Another approach would be to make some of our tools more VCS-aware
> (or UDD-aware if UDD imports data from VCSses).

For my packages, I am preparing to test the following workflow: store the
upstream metadata in YAML format in the source package, and make some tools
aware of the content of the file as it is in the VCS containing the source
package. In the Debian Med team we need a mechanism to indicate registration
pages to our users. I have not yet figured out if the best is a spider
mechanism, where the tool checks the file from time to time, or a push
mechanism, with a proper commit hook that will advertise that the changes.

Whichever the implementation, if we manage to move out metadata from
debian/control, it means that we will probably expand the fields a lot. How
about briefly documenting them on a wiki page to avoid collisions? 

Lastly, a radically different solution would be to centralise everything in a
big monolithic file, and give commit access to all DDs for instance. That would
also completely untie the update of upstream metadata from package upload, and
if the file is managed in a VCS, it would be easy to revert mistakes and find
misusers, if somebody ever dares.

Have a nice day

Charles Plessy
Debian Med packaging team,
Tsurumi, Kanagawa, Japan

Reply to: