From f5f2e183cc9e59f67d7084222aa73c2471aeaa7c Mon Sep 17 00:00:00 2001 From: "martin f. krafft" Date: Thu, 24 Apr 2008 20:31:15 +0200 Subject: [PATCH 1/1] add readme --- README | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 README diff --git a/README b/README new file mode 100644 index 0000000..4d9e40c --- /dev/null +++ b/README @@ -0,0 +1,23 @@ +mbuild README +============= + +The general idea of mbuild is that it's called for new *_source.changes files +that accompany source-only uploads (dpkg-buildpackage -S). Based on the target +suite, it then figures out which architectures reprepro wants and which sbuild +provides (this is to be implemented yet) and fires off sbuild for each. + +When the builds have finished, the source package is handed over to reprepro, +and then each of the binary changes files in turn. + +Finally, a bundle is built with the binary packages from one arch, and the +source package, with changes files merged. The idea is that this bundle can +now be downloaded, inspected, tested, and finally, when it's ready for upload, +the changes file signed and uploaded. + +Right now, no authentication is done on the signature on the *_source.changes +file and the *.dsc file, but that could be hacked in with dscverify. + +All this is very hackish and beta; if you want to hack along: + http://git.madduck.net/v/code/mbuild.git + + -- martin f. krafft Thu, 24 Apr 2008 20:30:51 +0200 -- 2.39.5