Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
DEP11 is CANDIDATE now!
0 views
Skip to first unread message
Matthias Klumpp
Mar 20, 2012, 7:00:01 AM3/20/12
to
Hi!
I just wanted to announce that DEP11[1] has the status of a candidate
now, since all necessary bits are discussed and we're now working on a
first impementation.
It would be cool if someone could change it's status on dep.d.n too :)
Kind regards,
Matthias
------
[1]: http://wiki.debian.org/AppStreamDebianProposal
--
To UNSUBSCRIBE, email to debian-proj...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/CAKNHny_pVh86kJwLy95kF754=o=5X1+HfKa_zs...@mail.gmail.com
I just wanted to announce that DEP11[1] has the status of a candidate
now, since all necessary bits are discussed and we're now working on a
first impementation.
It would be cool if someone could change it's status on dep.d.n too :)
Kind regards,
Matthias
------
[1]: http://wiki.debian.org/AppStreamDebianProposal
--
To UNSUBSCRIBE, email to debian-proj...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/CAKNHny_pVh86kJwLy95kF754=o=5X1+HfKa_zs...@mail.gmail.com
Charles Plessy
Mar 24, 2012, 11:50:01 PM3/24/12
to
Le Tue, Mar 20, 2012 at 11:34:50AM +0100, Matthias Klumpp a écrit :
>
> I just wanted to announce that DEP11[1] has the status of a candidate
> now, since all necessary bits are discussed and we're now working on a
> first impementation.
Dear Matthias,
>
> I just wanted to announce that DEP11[1] has the status of a candidate
> now, since all necessary bits are discussed and we're now working on a
> first impementation.
it is nice to see this project advance. While I think that I have a rough
understanding of the goals in general, I am still missing key points about the
scope of DEP 11 and the proposed implementation.
Is it accurate to summarise DEP 11 by saying that it a specification of an
AppStream metadata file in Debian's control data format, and the specification
of this file's locations in the Debian archive ?
I still wonder about the flow of information. Is the plan to have dak scan the
packages for FreeDesktop menu entry files and generate the ComponentMetadata
index files ?
Together with Andreas Tille, we are finalising the first proof of principle of
using debian/upstream files in YAML format to store additional metadata. Our
current approach is only tracking the latest version of a package (in Sid), and
only tracking source packages that are managed in a VCS, so it may not be
compatible with your project. But perhaps you can have a look (note that the
spec is not stable yet).
http://wiki.debian.org/UpstreamMetadata
In addition to the debian/upstream files, we are also collecting Debian
copyright files. The gatherer is still in construction, so the collection is
still quite limited. But in theory, it could be extended to collect
FreeDesktop menu files if you are interested.
http://anonscm.debian.org/viewvc/collab-qa/packages-metadata/a/
Have a nice Sunday,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
--
To UNSUBSCRIBE, email to debian-proj...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Andreas Tille
Mar 26, 2012, 3:20:02 AM3/26/12
to
On Sun, Mar 25, 2012 at 12:42:25PM +0900, Charles Plessy wrote:
> Together with Andreas Tille, we are finalising the first proof of principle of
> using debian/upstream files in YAML format to store additional metadata. Our
> current approach is only tracking the latest version of a package (in Sid), and
> only tracking source packages that are managed in a VCS, so it may not be
> compatible with your project.
Remark: The fact that we currently only respect packages managed in a
> Together with Andreas Tille, we are finalising the first proof of principle of
> using debian/upstream files in YAML format to store additional metadata. Our
> current approach is only tracking the latest version of a package (in Sid), and
> only tracking source packages that are managed in a VCS, so it may not be
> compatible with your project.
VCS is not really a requirement (at least as far as I do things) but
rather a because it makes fetching those files quite easy in the current
infrastructure of Debian. I perfectly could imagine some mechanism in
parallel to the process which creates Contents-<arch>.gz which parses
Debian source archives and creates some Contents-Source.gz files which
could have a lot of interesting other uses. Once this might exist it
could be easy to obtain such information. To continue the raw thinking
a bit further I could imaging
Contents-OrigSource.gz (containing all the content of original sources)
Contents-Debian.gz (containing everything in debian/)
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-proj...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Paul Wise
Mar 26, 2012, 4:10:02 AM3/26/12
to
On Mon, Mar 26, 2012 at 3:09 PM, Andreas Tille wrote:
> infrastructure of Debian. I perfectly could imagine some mechanism in
> parallel to the process which creates Contents-<arch>.gz which parses
> Debian source archives and creates some Contents-Source.gz files which
> could have a lot of interesting other uses. Once this might exist it
> could be easy to obtain such information. To continue the raw thinking
> a bit further I could imaging
>
> Contents-OrigSource.gz (containing all the content of original sources)
> Contents-Debian.gz (containing everything in debian/)
Half way there:
> infrastructure of Debian. I perfectly could imagine some mechanism in
> parallel to the process which creates Contents-<arch>.gz which parses
> Debian source archives and creates some Contents-Source.gz files which
> could have a lot of interesting other uses. Once this might exist it
> could be easy to obtain such information. To continue the raw thinking
> a bit further I could imaging
>
> Contents-OrigSource.gz (containing all the content of original sources)
> Contents-Debian.gz (containing everything in debian/)
http://ftp.debian.org/debian/dists/sid/main/Contents-source.gz
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-proj...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Andreas Tille
Mar 26, 2012, 4:30:02 AM3/26/12
to
Hi,
On Mon, Mar 26, 2012 at 04:04:55PM +0800, Paul Wise wrote:
> >
> > Contents-OrigSource.gz (containing all the content of original sources)
> > Contents-Debian.gz (containing everything in debian/)
>
> Half way there:
>
> http://ftp.debian.org/debian/dists/sid/main/Contents-source.gz
Cool! I was not aware of this. Charles, IMHO this
$ zgrep debian/upstream[^/^.] Contents-source.gz
is a quite interesting reading. We should check whether some upstream
files are "hidden" from our VCS approach. We also know which packages
should probably uploaded in the next couple of monthes to make the
upstream-metadata.yaml move complete. And finally we should probably
make sure that debian/upstream is a reserved name because some packages
are using "debian/upstream/" (thus the exclusion of '/' in the regexp
above).
Paul, thanks for the useful hint
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-proj...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20120326082...@an3as.eu
On Mon, Mar 26, 2012 at 04:04:55PM +0800, Paul Wise wrote:
> >
> > Contents-OrigSource.gz (containing all the content of original sources)
> > Contents-Debian.gz (containing everything in debian/)
>
> Half way there:
>
> http://ftp.debian.org/debian/dists/sid/main/Contents-source.gz
$ zgrep debian/upstream[^/^.] Contents-source.gz
is a quite interesting reading. We should check whether some upstream
files are "hidden" from our VCS approach. We also know which packages
should probably uploaded in the next couple of monthes to make the
upstream-metadata.yaml move complete. And finally we should probably
make sure that debian/upstream is a reserved name because some packages
are using "debian/upstream/" (thus the exclusion of '/' in the regexp
above).
Paul, thanks for the useful hint
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-proj...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages