diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2010-November/000190.html')
-rw-r--r-- | zarb-ml/mageia-sysadm/2010-November/000190.html | 113 |
1 files changed, 113 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2010-November/000190.html b/zarb-ml/mageia-sysadm/2010-November/000190.html new file mode 100644 index 000000000..2583c4173 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-November/000190.html @@ -0,0 +1,113 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Packages SVN + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Packages%20SVN&In-Reply-To=%3C20101104145735.GC21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000188.html"> + <LINK REL="Next" HREF="000168.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Packages SVN</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Packages%20SVN&In-Reply-To=%3C20101104145735.GC21938%40mars-attacks.org%3E" + TITLE="[Mageia-sysadm] Packages SVN">boklm at mars-attacks.org + </A><BR> + <I>Thu Nov 4 15:57:35 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000188.html">[Mageia-sysadm] Packages SVN +</A></li> + <LI>Next message: <A HREF="000168.html">[Mageia-sysadm] Packages SVN +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#190">[ date ]</a> + <a href="thread.html#190">[ thread ]</a> + <a href="subject.html#190">[ subject ]</a> + <a href="author.html#190">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, 04 Nov 2010, Luca Berra wrote: + +><i> On Wed, Nov 03, 2010 at 11:12:53PM +0100, Olivier Blin wrote: +</I>>><i> nicolas vigier <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">boklm at mars-attacks.org</A>> writes: +</I>>><i> +</I>>>><i> We can also remove history on cauldron binary branch, although it will +</I>>>><i> require to stop new commits for a few minutes/hours, doing something like +</I>>>><i> this : +</I>>>><i> <A HREF="http://robmayhew.com/delete-parts-of-subversion-history/">http://robmayhew.com/delete-parts-of-subversion-history/</A> +</I>>><i> +</I>>><i> Right, we could do in such a way. +</I>>><i> Each N distro branch could contain binary history from N-1 to N. +</I>>><i> +</I>>><i> For example when we release 2011.1, we would have binary history in the +</I>>><i> 2011.1 distro branch from 2011.0 to 2011.1, and start cauldron from a +</I>>><i> one-revision copy. +</I> +I'm not sure we need to keep history from N-1 to N (which is previous +cooker versions), maybe we can erase it. And only have history from +N (release date) to N + updates. + +>><i> Though, there is a disadvantage that could get problematic, when we do +</I>>><i> backports, we would have to copy the binaries to all target distros, and +</I>>><i> it would not be a cheap SVN copy anymore. +</I>>><i> This could get pretty big with games and OOo... +</I> +Yes. + +><i> I wonder why use svn at all in order to store blobs +</I>><i> IMHO it does not give any advantage +</I> +The advantage is that it is easier to implement, and already implemented +now in a repsys branch on git. But it is still possible to replace the +SVN binary repositories with something else later. + +><i> source tarballs in packages are usually compressed, so no delta is +</I>><i> possible, besides that sources are usually removed and the new one is +</I>><i> added, so it wont be even tried. +</I>><i> removing something from SVN is a PITA +</I> +Removing something from SVN is not very difficult, if removing all +history before a commit (and not only some of the files). + +><i> creating a branch for each distro will waste enormous amounts of space, +</I>><i> and will create the issue pointed above by blino. +</I>><i> +</I>><i> why not just use flat files to store flat files? +</I>><i> iirc redhat is doing this to store files +</I>><i> +</I>><i> if i were to design this i would index flat files by sha +</I>><i> and modify repsys/mdvsys in order to commit a file containing the sha in +</I>><i> <A HREF="svn://specrepo/package/SOURCES/foo-0.0.1.tar.xz">svn://specrepo/package/SOURCES/foo-0.0.1.tar.xz</A> instead of the real blob +</I>><i> and checkout the real file from <A HREF="file://binrepo/hashed_dir/sha">file://binrepo/hashed_dir/sha</A> instead of +</I>><i> the dummy. +</I> +It can be a good idea, but it requires some work to implement it. I +think it's something that can be done later. + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000188.html">[Mageia-sysadm] Packages SVN +</A></li> + <LI>Next message: <A HREF="000168.html">[Mageia-sysadm] Packages SVN +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#190">[ date ]</a> + <a href="thread.html#190">[ thread ]</a> + <a href="subject.html#190">[ subject ]</a> + <a href="author.html#190">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |