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

Re: [DEP5] [patch] Renaming the ‘Maintainer’ field ‘Contact’

Le Fri, Aug 20, 2010 at 10:26:20AM +0800, Paul Wise a écrit :
> On Fri, Aug 20, 2010 at 6:23 AM, Lars Wirzenius <liw@liw.fi> wrote:
> > I therefore intend to keep the fields in the spec, unless there's a wave
> > of opposition. I hope that this is acceptable. (The volume of DEP-5
> > discussion dropped to low enough that it's getting hard to measure
> > consensus. :)
> I'd prefer debian/copyright wasn't overloaded with random upstream
> metadata. It would be better to use one of debian/control,
> upstream-metadata.yaml or DOAP/etc in the upstream tarball.

Hi all,

Here is a quick way to test the upstream-metadata system. For instance, I will
add Name data for the libdata-stag-perl package.

First, let's check that the system does not yet know about the package:

  curl http://upstream-metadata.debian.net/libdata-stag-perl/Name
  # (returns nothing)

Then, let's add the data in the source package's repository:

  # Checkout the package
  debcheckout -a libdata-stag-perl
  cd libdata-stag-perl

  # Enter the data
  cat > debian/upstream-metadata.yaml <<__HOPLA__
  Name: Data::Stag

  # Commit
  svn add debian/upstream-metadata.yaml
  svn commit -m "Added Name upstream metadata for libdata-stag-perl"

Et voila! It is in the upstream-metadata system.

  curl http://upstream-metadata.debian.net/libdata-stag-perl/Name
  # (Returns ‘Data::Stag’)

My current approach, for which I hope show some proof of principle soon, is to
export the data in a public directory, for loading in the Ultimate Debian
Database, that would be the reference for the data. Currently, I have loaded
some bibliographic information about scientific packages in a local copy of the
UDD. We want to incorporate this information in the “web sentinel” pages
produced by the Blends framework.

Have a nice day,

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

Reply to: