summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20100927/000281.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20100927/000281.html')
-rw-r--r--zarb-ml/mageia-dev/20100927/000281.html97
1 files changed, 97 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20100927/000281.html b/zarb-ml/mageia-dev/20100927/000281.html
new file mode 100644
index 000000000..39285f365
--- /dev/null
+++ b/zarb-ml/mageia-dev/20100927/000281.html
@@ -0,0 +1,97 @@
+<!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=%3C4C9FF447.3040709%40roadrunner.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000298.html">
+ <LINK REL="Next" HREF="000289.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Will this work for a build system?</H1>
+ <B>Frank Griffin</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=%3C4C9FF447.3040709%40roadrunner.com%3E"
+ TITLE="[Mageia-dev] Will this work for a build system?">ftg at roadrunner.com
+ </A><BR>
+ <I>Mon Sep 27 03:32:55 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000298.html">[Mageia-dev] Will this work for a build system?
+</A></li>
+ <LI>Next message: <A HREF="000289.html">[Mageia-dev] Will this work for a build system?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#281">[ date ]</a>
+ <a href="thread.html#281">[ thread ]</a>
+ <a href="subject.html#281">[ subject ]</a>
+ <a href="author.html#281">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Giuseppe Ghib&#242; wrote:
+&gt;<i> The most difficult things IMHO would be building from the same
+</I>&gt;<i> syncronized data. In that case you might choose a master server and
+</I>&gt;<i> several mirrors. The master might have multiple internet access points
+</I>&gt;<i> (e.g. from two providers) and will be the only one who might receive
+</I>&gt;<i> svn commits. Or a model without a master, I guess inspiring to a model
+</I>&gt;<i> what UseNET is (was), I think a lot more complicate. But in that case
+</I>&gt;<i> you have two direction of feeding and if two libraries are submitted
+</I>&gt;<i> in different user in nearest time, you need a system to check for
+</I>&gt;<i> coerency and set alarms in some cases.
+</I>&gt;<i>
+</I>&gt;<i> IMHO one of the building problems was not massive automatic rebuilding
+</I>&gt;<i> but avoid bottenlecks to the users when building goes wrong.
+</I>I really like the concept of a distributed build system.
+
+There is the problem that in most home ISP accounts, upload speed is
+pitiful compared to download speed, by design - they don't want home
+users running servers. However, it should be possible to design
+something along the lines of the SETI project. Have the prospective
+servers rsync their captive build environments prior to build, and build
+in a chroot, returning the results. I'd be happy to provide a machine
+on my home LAN to do this, and it would be interesting to design the
+control system for it. Given many machines which have been rsync'd to
+the correct build environment, a distributed *make* could export
+individual compiles or groups of compiles to the cloud systems. Just as
+we have &quot;committer&quot; rights now, we could have cloud build rights that
+involve key pairs that could digitally sign what they send back to
+identify the sender. With random distribution of work, the chances of
+malice are considerably less, and the key signature ensures that you
+know who you got anything dodgy from.
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000298.html">[Mageia-dev] Will this work for a build system?
+</A></li>
+ <LI>Next message: <A HREF="000289.html">[Mageia-dev] Will this work for a build system?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#281">[ date ]</a>
+ <a href="thread.html#281">[ thread ]</a>
+ <a href="subject.html#281">[ subject ]</a>
+ <a href="author.html#281">[ 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>