diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20100926/000271.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20100926/000271.html | 111 |
1 files changed, 111 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20100926/000271.html b/zarb-ml/mageia-dev/20100926/000271.html new file mode 100644 index 000000000..6524d8fb1 --- /dev/null +++ b/zarb-ml/mageia-dev/20100926/000271.html @@ -0,0 +1,111 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Will this work for a build system? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Will%20this%20work%20for%20a%20build%20system%3F&In-Reply-To=%3CAANLkTinnunRcMO%2Bc3icdS25HGA1gNUg9GpYpXp49yTQw%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000269.html"> + <LINK REL="Next" HREF="000262.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Will this work for a build system?</H1> + <B>Giuseppe Ghibò</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Will%20this%20work%20for%20a%20build%20system%3F&In-Reply-To=%3CAANLkTinnunRcMO%2Bc3icdS25HGA1gNUg9GpYpXp49yTQw%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Will this work for a build system?">ghibomgx at gmail.com + </A><BR> + <I>Sun Sep 26 19:14:15 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000269.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI>Next message: <A HREF="000262.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#271">[ date ]</a> + <a href="thread.html#271">[ thread ]</a> + <a href="subject.html#271">[ subject ]</a> + <a href="author.html#271">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>2010/9/26 nicolas vigier <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">boklm at mars-attacks.org</A>> + +><i> On Sun, 26 Sep 2010, joris dedieu wrote: +</I>><i> +</I>><i> > 2010/9/26 Olivier Blin <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at blino.org</A>>: +</I>><i> > > +</I>><i> > > Because there are some authentication and integrity issues which are +</I>><i> not +</I>><i> > > simple to solve: we have to be sure that the binary packages really +</I>><i> come +</I>><i> > > from the unmodified SRPM (so that it does not contains malware). +</I>><i> > +</I>><i> > This can be avoid by +</I>><i> > - building every package twice (also useful for integrity check) +</I>><i> +</I>><i> Then you can still do it with two hosts adding malware instead of one. +</I>><i> +</I> +What this means? Two RPMs built at different time will result different, +even the executable binaries when built on the same hardware at different +time might be different (because of timestamps, etc.). + +IMHO the idea of the cloud is not that bad but need to be rethinked. I don't +see so much flaws for security. If you inspire to what repsys is right now, +the cloud would be like having several svn repositories mirrored around the +world each one with a local iurt/repsys building system (it might be even +partial, e.g. there could be BIG ones holding the whole svn|git tree, and +smaller one holding just the latest release or the latest two releases, +etc.). Each building system around the world will sign packages they build +with their own signing keys and you know where they come from. And packages +won't be resigned by a supposed master. Of course you have to trust their +administrators, exactly like you right now have to trust single users +submitting sources to the svn and bulding packages. + +The most difficult things IMHO would be building from the same syncronized +data. In that case you might choose a master server and several mirrors. The +master might have multiple internet access points (e.g. from two providers) +and will be the only one who might receive svn commits. Or a model without a +master, I guess inspiring to a model what UseNET is (was), I think a lot +more complicate. But in that case you have two direction of feeding and if +two libraries are submitted in different user in nearest time, you need a +system to check for coerency and set alarms in some cases. + +IMHO one of the building problems was not massive automatic rebuilding but +avoid bottenlecks to the users when building goes wrong. + +Bye +Giuseppe. +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-dev/attachments/20100926/88900d00/attachment.html> +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000269.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI>Next message: <A HREF="000262.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#271">[ date ]</a> + <a href="thread.html#271">[ thread ]</a> + <a href="subject.html#271">[ subject ]</a> + <a href="author.html#271">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |