diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20100926/000268.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20100926/000268.html | 129 |
1 files changed, 129 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20100926/000268.html b/zarb-ml/mageia-dev/20100926/000268.html new file mode 100644 index 000000000..1091cd489 --- /dev/null +++ b/zarb-ml/mageia-dev/20100926/000268.html @@ -0,0 +1,129 @@ +<!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=%3C1285517056.2698.14.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000265.html"> + <LINK REL="Next" HREF="000269.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Will this work for a build system?</H1> + <B>Michael Scherer</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=%3C1285517056.2698.14.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Will this work for a build system?">misc at zarb.org + </A><BR> + <I>Sun Sep 26 18:04:16 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000265.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI>Next message: <A HREF="000269.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#268">[ date ]</a> + <a href="thread.html#268">[ thread ]</a> + <a href="subject.html#268">[ subject ]</a> + <a href="author.html#268">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le dimanche 26 septembre 2010 à 17:04 +0200, joris dedieu a écrit : +><i> 2010/9/26 Olivier Blin <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at blino.org</A>>: +</I>><i> > R James <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">upsnag2 at gmail.com</A>> writes: +</I>><i> > +</I>><i> >>> BTW, I once calculated (test plus extrapolation) how long it would take +</I>><i> >>> to rebuild every package in Mandriva on a low end 2 GHz Celeron server +</I>><i> >>> that I had available and it came to about 80 days. +</I>><i> > +</I>><i> > With a reasonably good machine, we used to be able to rebuild most of +</I>><i> > "main" in about one day. +</I>><i> > +</I>><i> >> Perhaps I was naive in thinking that compiling the distro could be +</I>><i> >> done with distcc or even a simple queuing system that distributes +</I>><i> >> SRPMs to nodes in the community swarm. As each node returns its +</I>><i> >> completed binary package, the queuing system could send it another +</I>><i> >> SRPM to build. +</I>><i> >> +</I>><i> >> It would be cool if it could be done that way. Why pay for data +</I>><i> >> center space, hardware, electricity and big bandwidth when you could +</I>><i> >> have a community-provided "cloud" for free? :o) +</I>><i> > +</I>><i> > Because there are some authentication and integrity issues which are not +</I>><i> > simple to solve: we have to be sure that the binary packages really 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> +What if a package has changed between the first build and the second in +such a way that it impact the compilation ? + +This would either requires to resubmit the packages ( which will be +quickly annoying ) or this would requires 3rd compilation, maybe a 4th +one. + +what if the binary include hostname, build date and so on ? + +then the build will be seen as different no matter you do ( ie, md5, +sha1 ) because it will have different contents. + + +><i> - randomize build order +</I>><i> - timedout jobs +</I>><i> +</I>><i> It's not a trivial problem but imho distribute tools advantages +</I>><i> (price, scalability, availability ...) should be seriously considered. +</I>><i> Has a single build system in a single datacenter should be a single +</I>><i> point of failure. +</I> +there will be a single point of failure, no matter you do : + +There is a reference vcs, and a single job dispatcher. We can maybe +double them or work around issues but this would lead to more complexity +which may not really compensate a potential datacenter problem. + +Fedora had been compromised once and had to shut down their +infrastructure, or had to move servers sooner this year, they coped with +the downtime. + +Debian had problem ( like security.debian.org who burned in 2002, or the +famous openssl problem in 2008 ) too, without trouble. + +Launchpad is often down for database upgrade, and still, Ubuntu is +there. + +-- +Michael Scherer + +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000265.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI>Next message: <A HREF="000269.html">[Mageia-dev] Will this work for a build system? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#268">[ date ]</a> + <a href="thread.html#268">[ thread ]</a> + <a href="subject.html#268">[ subject ]</a> + <a href="author.html#268">[ 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> |