From: David Craven <david@craven.ch>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: How to get the package metadata as structured data?
Date: Thu, 4 Aug 2016 22:49:37 +0200 [thread overview]
Message-ID: <CAL1_immqXKMgvKx8yFq41-52RiDRJZ_QDODEd4VwZ-iHZtb1cQ@mail.gmail.com> (raw)
Hi Philippe,
Thank you for your interest in guix =)
All package metadata can be accessed easily through scheme. There is
no way to export this data currently, although it probably wouldn't be
too hard to implement.
The approach I was planning on taking is the following:
Take a package, remove all build-phases except unpack, add a phase to
run scancode and add the output json to the store.
This way guix already takes care of fetching and unpacking the package
and caching the result. Unless a build input changes, for example
scancode (an input to the scancode phase) is updated, or a scanned
package is updated, running a tool that I'll call `guix license` for
now will work of the json file that was already generated. This means
that improving the reporting or postprocessing the results doesn't
require rescanning a dependency.
Maybe someone else has other/better ;-) thoughts on this?
Cheers
David
next reply other threads:[~2016-08-04 20:49 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 20:49 David Craven [this message]
2016-08-04 21:08 ` How to get the package metadata as structured data? Ludovic Courtès
2016-08-04 22:03 ` Cook, Malcolm
2016-08-05 10:17 ` David Craven
2016-08-05 11:04 ` David Craven
2016-08-05 12:40 ` Aljosha Papsch
2016-08-05 14:50 ` Philippe Ombredanne
2016-08-05 14:58 ` [PATCH] ui: 'package->recutils' serializes the source field David Craven
2016-08-06 12:35 ` Alex Kost
2016-08-06 12:46 ` David Craven
2016-08-06 15:00 ` Mathieu Lirzin
2016-08-07 10:26 ` David Craven
2016-08-07 11:15 ` Mathieu Lirzin
2016-08-07 11:19 ` David Craven
2016-08-07 12:12 ` David Craven
2016-08-07 13:27 ` Mathieu Lirzin
2016-08-07 21:33 ` David Craven
2016-08-08 0:15 ` Mathieu Lirzin
2016-08-08 11:20 ` David Craven
2016-08-08 17:53 ` Mathieu Lirzin
2016-08-08 18:12 ` David Craven
2016-08-08 19:07 ` Alex Kost
2016-08-08 21:09 ` Mathieu Lirzin
2016-08-08 22:58 ` David Craven
2016-08-08 23:56 ` Mathieu Lirzin
2016-08-09 0:18 ` David Craven
2016-08-10 10:12 ` David Craven
2016-08-10 11:30 ` Mathieu Lirzin
2016-08-10 11:38 ` David Craven
2016-08-10 11:46 ` David Craven
2016-08-10 12:06 ` Mathieu Lirzin
2016-08-10 12:15 ` Ben Woodcroft
2016-08-10 12:27 ` David Craven
2016-08-10 12:53 ` Ben Woodcroft
2016-08-10 13:23 ` David Craven
2016-08-10 13:42 ` Ricardo Wurmus
2016-08-10 14:13 ` David Craven
2016-08-11 14:38 ` Alex Kost
2016-08-11 16:19 ` David Craven
2016-08-11 18:15 ` Ricardo Wurmus
2016-08-12 8:22 ` Alex Kost
2016-08-11 16:42 ` Ricardo Wurmus
2016-08-12 8:33 ` Alex Kost
2016-08-12 8:41 ` Ricardo Wurmus
2016-08-12 10:05 ` David Craven
2016-08-13 7:46 ` Alex Kost
2016-08-13 13:00 ` David Craven
2016-08-13 13:18 ` Leo Famulari
2016-08-14 16:00 ` Alex Kost
2016-08-10 14:25 ` Thompson, David
2016-08-10 17:56 ` Leo Famulari
2016-08-11 10:15 ` Mark H Weaver
2016-08-11 10:21 ` Mark H Weaver
2016-08-11 11:06 ` David Craven
2016-08-11 11:41 ` Mark H Weaver
2016-08-11 11:46 ` David Craven
2016-08-10 11:46 ` How to get the package metadata as structured data? Ricardo Wurmus
2016-08-10 12:14 ` Catonano
2016-08-10 12:52 ` Ricardo Wurmus
2016-08-10 23:40 ` Catonano
-- strict thread matches above, loose matches on Subject: below --
2016-08-04 18:37 Philippe Ombredanne
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL1_immqXKMgvKx8yFq41-52RiDRJZ_QDODEd4VwZ-iHZtb1cQ@mail.gmail.com \
--to=david@craven.ch \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).