From: Sebastian Pipping <webmaster@hartwork.org>
To: PackageKit users and developers list <packagekit@lists.freedesktop.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Inviting you to project "PackageMap"
Date: Fri, 12 Jun 2009 09:42:18 +0200 [thread overview]
Message-ID: <4A3206DA.3090907@hartwork.org> (raw)
Hello!
Quick (re-)introduction: My task for Gentoo/Google Summer of Code 2009
is to give Gentoo a Debian popcon equivalent, a tool to collect
statistics on "what package is installed how often". To achieve this
goal I'm extending Smolt (a tool currently doing similar things with
hardware information) by fine-tunable software stats gathering.
The plan we have for Smolt is to make it cross-distro, not just fit
Gentoo or Fedora. One point where the consequences and benefits of such
an approach can be seen clearly is with
counting packages from different distros into the same buckets.
What do I mean by that? Debian's Git counts for Gentoo's Git counts for
Fedora's, you know the list. With packages counted from accross distros
we can suddenly answer questions that we currently cannot answer, among them
- What globally popular packages are missing in distro X?
Let's say we don't have a package for product P. Do other distros
have one? They do, maybe we need one, too? They don't, maybe P is
not that important then?
- How many Linux users are approximately using program X in total?
Not just on Ubuntu or Arch - all across Linux, BSD, Solaris!
- Does distro X have 10 times the packages of Y or is it just
different splitting?
To count into the same bucket we use global identifiers for the
"products" that fall out of a package. Gentoo package "dev-util/git"
can produce product "cpe://a:git:git", Debian's "git-core" can, too.
That string before is a CPE URI [1], a concept close to package naming
in Java. This "intermediate language" allows us to relate package names
from distro X with those of distro Y and answer various questions from
that data.
To do such mapping we need code (or a "service") that does the mapping
for us and base of collected data that the service can operate on. Both
of these is project "PackageMap"
I have started populating the database with packages (currently 312
in number) made from information extracted from the Gentoo tree
and the National Vulnerability Database. Latter holds many CPEs.
Let me state clearly that packagemap is not about Gentoo in particular.
Sure, the initial data has lots of Gentoo in it but the whole point of
the project is to get information and people from different distros
together.
To see what these 312 packages maps look like at the moment you best do
a few clicks through the database folder yourself:
http://git.goodpoint.de/?p=packagemap.git;a=tree;f=database
Also, there are Relax NG schema and DTD for validation, more
documentation than I usually write and a few scripts:
http://git.goodpoint.de/?p=packagemap.git;a=tree
By now I hope you have gained interest in what this can become.
Your active participation is highly appreciated.
A few minutes from everyone can make a huge difference here.
If you want write access to the repo - mail me: sebastian@pipping.org.
Please have a look at the Git repository linked above and ask questions.
I propose to keep the related Gentoo stuff on gentoo-dev and everything
else on the packagekit list. I hope that works out well.
Thanks for reading up to this point.
Sebastian
PS: I'm aware "hartwork.org" might not make a good longterm location for
DTDs, XML namespaces and such for a cross-distro project. Any ideas
where to put them best?
[1] http://cpe.mitre.org/
next reply other threads:[~2009-06-12 7:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 7:42 Sebastian Pipping [this message]
[not found] ` <15e53e180906120130md68cd94nba61fa5560c73eb4@mail.gmail.com>
2009-06-12 9:54 ` [gentoo-dev] Re: [packagekit] Inviting you to project "PackageMap" Sebastian Pipping
2009-06-17 12:08 ` Tiziano Müller
2009-06-12 13:00 ` [gentoo-dev] " Steven J Long
2009-06-13 3:55 ` Sebastian Pipping
2009-07-11 21:38 ` [gentoo-dev] " Steven J Long
2009-06-12 18:27 ` [gentoo-dev] " Petteri Räty
2009-06-12 21:43 ` [packagekit] " Sebastian Pipping
2009-06-13 15:53 ` Petteri Räty
2009-06-13 19:03 ` Sebastian Pipping
2009-06-13 19:16 ` Petteri Räty
2009-06-15 13:52 ` Robert Buchholz
2009-06-15 17:04 ` Sebastian Pipping
2009-06-15 18:24 ` Robert Buchholz
2009-06-15 19:13 ` Sebastian Pipping
2009-06-15 20:27 ` Petteri Räty
2009-06-17 0:34 ` Sebastian Pipping
2009-06-17 9:37 ` Marijn Schouten (hkBst)
2009-06-18 0:09 ` Sebastian Pipping
2009-06-18 9:07 ` Marijn Schouten (hkBst)
2009-06-19 18:53 ` Sebastian Pipping
[not found] ` <1245295820.11471.223.camel@chianamo.mine.nu>
2009-06-18 22:33 ` Sebastian Pipping
[not found] ` <1245382383.14805.281.camel@chianamo.mine.nu>
2009-06-19 17:36 ` Sebastian Pipping
2009-06-19 21:47 ` Sebastian Pipping
2009-06-20 13:16 ` Petteri Räty
2009-06-20 17:28 ` Sebastian Pipping
2009-07-14 16:49 ` Sebastian Pipping
2009-07-20 2:03 ` [GLEP] CPE names in metadata (was Re: [gentoo-dev] Inviting you to project "PackageMap") Sebastian Pipping
2009-06-15 21:27 ` [gentoo-dev] Re: [packagekit] Inviting you to project "PackageMap" Christian Faulhammer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A3206DA.3090907@hartwork.org \
--to=webmaster@hartwork.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=packagekit@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox