1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Distributed packaging for a community distro
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Distributed%20packaging%20for%20a%20community%20distro&In-Reply-To=%3C201009191410.57950.p_christ%40hol.gr%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000768.html">
<LINK REL="Next" HREF="000777.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Distributed packaging for a community distro</H1>
<B>P. Christeas</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Distributed%20packaging%20for%20a%20community%20distro&In-Reply-To=%3C201009191410.57950.p_christ%40hol.gr%3E"
TITLE="[Mageia-dev] Distributed packaging for a community distro">p_christ at hol.gr
</A><BR>
<I>Sun Sep 19 13:10:57 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000768.html">[Mageia-dev] Distributed packaging for a community distro
</A></li>
<LI>Next message: <A HREF="000777.html">[Mageia-dev] Distributed packaging for a community distro
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#770">[ date ]</a>
<a href="thread.html#770">[ thread ]</a>
<a href="subject.html#770">[ subject ]</a>
<a href="author.html#770">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Sunday 19 September 2010, Colin Guthrie wrote:
> I've not read the above fedora links yet (I definitely will), but the
><i> two immediate problems I have are:
</I>><i>
</I>><i> * Binary churn: If we add the tarballs, there can be a lot of binary
</I>><i> churn. Cloning a git repo means we get the full history locally which
</I>><i> means all copies of the tarball over the x years period. SVN is better
</I>><i> suited to binary churn, only keeping the most recent version in your
</I>><i> checkout. This is likely discussed above.
</I>The idea is that we don't submit the source tar inside our own "packaging"
repo, but the opposite: that we submit our "mageia.spec" file into the upstream
project's git repo. So, no binary churns. The same way as some projects
already have a "debian/" folder or sample RedHat .specs .
If we need to patch the upstream (or the upstream is not interested to include
our spec), we will just keep a git branch of our "flavour", which follows
upstream.
><i>
</I>><i> * Tagging: When a release is done, the packages need to be tagged. This
</I>><i> is more awkward with individual repos rather than one central one, but I
</I>><i> suspect it's a relatively easy process to script.
</I>
That's where we use the master repo with submodules . The master will do the
tag-keeping.
><i> (I do hope these are mentioned in the above links)
</I>><i>
</I>><i> Anyway, as a general rule, I'm very much behind using git for packages :)
</I>><i>
</I>
Another issue, already thought of is what if upstream doesn't use git: there
are many usable converters, now, from SVN, CVS, Bzr[1], Hg etc. So, we can
incrementaly import those projects.
[1] already patched the bzr-fastexport 's bugs.
--
Say NO to spam and viruses. Stop using Microsoft Windows!
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000768.html">[Mageia-dev] Distributed packaging for a community distro
</A></li>
<LI>Next message: <A HREF="000777.html">[Mageia-dev] Distributed packaging for a community distro
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#770">[ date ]</a>
<a href="thread.html#770">[ thread ]</a>
<a href="subject.html#770">[ subject ]</a>
<a href="author.html#770">[ 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>
|
