Re: DEP 12: Per-package machine-readable metadata about Upstream

2013-01-04 Thread Enrico Zini
On Thu, Jan 03, 2013 at 04:51:02PM -0800, Russ Allbery wrote: > My point, rather, is that a bunch of the stuff that's being discussed as > relevant to debian/upstream can change independent of any functional > change in the package, and therefore the proposal raises the question of > whether we wa

Re: DEP 12: Per-package machine-readable metadata about Upstream

2013-01-03 Thread Russ Allbery
Paul Wise writes: > On Fri, Jan 4, 2013 at 12:59 AM, Russ Allbery wrote: >> Of course, the other issue that this DEP raises is how much sense it >> makes to put all this stuff in the source package, either in >> debian/control or in a new file, given that most of these fields (even >> including M

Re: DEP 12: Per-package machine-readable metadata about Upstream

2013-01-03 Thread Paul Wise
On Fri, Jan 4, 2013 at 12:59 AM, Russ Allbery wrote: > Of course, the other issue that this DEP raises is how much sense it makes > to put all this stuff in the source package, either in debian/control or > in a new file, given that most of these fields (even including Maintainer, > although movin

Re: DEP 12: Per-package machine-readable metadata about Upstream

2013-01-03 Thread Paul Wise
On Thu, Jan 3, 2013 at 11:57 PM, Guillem Jover wrote: > I guess we could have a discussion about the possibility/advantages of > having one index file (ex. Packages) containing exclusively machine > consumable metadata (for package managers), to favour small/embedded > systems, and another one wit

Re: DEP 12: Per-package machine-readable metadata about Upstream

2013-01-03 Thread Russ Allbery
Enrico Zini writes: > On Thu, Jan 03, 2013 at 04:57:56PM +0100, Guillem Jover wrote: >> option. The first fields that come to mind could be Homepage, >> Maintainer and Description (and for the latter this has already happened >> somewhat). But then this does not require a split in the source form

Re: DEP 12: Per-package machine-readable metadata about Upstream

2013-01-03 Thread Enrico Zini
On Thu, Jan 03, 2013 at 04:57:56PM +0100, Guillem Jover wrote: > option. The first fields that come to mind could be Homepage, > Maintainer and Description (and for the latter this has already happened > somewhat). But then this does not require a split in the source format, > but only in the arch

Re: DEP 12: Per-package machine-readable metadata about Upstream

2013-01-03 Thread Guillem Jover
On Thu, 2013-01-03 at 10:29:13 +0800, Paul Wise wrote: > On Thu, Jan 3, 2013 at 9:11 AM, Charles Plessy wrote: > > The source package control files and some of their derivatives are > > currently > > used to document the URL of the home page of the work that is packaged > > ("upstream"). Howev

Re: DEP 12: Per-package machine-readable metadata about Upstream

2013-01-02 Thread Raphael Hertzog
On Thu, 03 Jan 2013, Paul Wise wrote: > > The source package control files and some of their derivatives are > > currently > > used to document the URL of the home page of the work that is packaged > > ("upstream"). However, this approach is hard to extend to other > > information > > descri

Re: DEP 12: Per-package machine-readable metadata about Upstream

2013-01-02 Thread Paul Wise
The idea in general (providing more metadata about our upstreams) is a good one. On Thu, Jan 3, 2013 at 9:11 AM, Charles Plessy wrote: > The source package control files and some of their derivatives are currently > used to document the URL of the home page of the work that is packaged > ("ups

DEP 12: Per-package machine-readable metadata about Upstream

2013-01-02 Thread Charles Plessy
Dear all, I am starting the Debian Enahncement Proposal (DEP) number 12 together with Andreas Tille who kindly accepted to co-drive this work. For general information about DEPs, please see http://dep.debian.net/deps/dep0/ The puropose of this proposal is to store in source packages some metadat