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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20packages%20branches%20and%20revision%20numbers%20when%0A%20submiting%20packages%09with%20mgarepo&In-Reply-To=%3C4D4370B4.90800%40iki.fi%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002372.html">
<LINK REL="Next" HREF="002374.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo</H1>
<B>Anssi Hannula</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20packages%20branches%20and%20revision%20numbers%20when%0A%20submiting%20packages%09with%20mgarepo&In-Reply-To=%3C4D4370B4.90800%40iki.fi%3E"
TITLE="[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo">anssi.hannula at iki.fi
</A><BR>
<I>Sat Jan 29 02:43:16 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002372.html">[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
</A></li>
<LI>Next message: <A HREF="002374.html">[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2373">[ date ]</a>
<a href="thread.html#2373">[ thread ]</a>
<a href="subject.html#2373">[ subject ]</a>
<a href="author.html#2373">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 29.01.2011 03:16, nicolas vigier wrote:
><i> Hello,
</I>><i>
</I>><i> In Mandriva using repsys it was possible to provide a svn revision number
</I>><i> when submitting a package. It is still possible to do it using mgarepo,
</I>><i> but with a separate repository for binary files, it is more difficult.
</I>><i> The current version of mgarepo tries to find the right revision to use
</I>><i> for the binrepo (revision from the same date as the revision on the
</I>><i> specs repository), but it is not always working as expected. I started
</I>><i> to add an option to be able to specify the binrepo revision to use when
</I>><i> submiting, but after thinking about it, it's probably not a good idea,
</I>><i> because it becomes too complicate.
</I>><i>
</I>><i> With repsys it's also possible when submiting packages to give an URL
</I>><i> instead of a package name. This allows creating new branches for a
</I>><i> package. However we also have a problem with this with binrepo, as we
</I>><i> need to find the right path for the binary repository. We could add an
</I>><i> option to give the URL for the binaries, but I don't think it's a good
</I>><i> idea.
</I>><i>
</I>><i> So I propose to do this instead :
</I>><i>
</I>><i> - We won't allow using revision numbers when submiting packages.
</I>><i> Instead we always use the latest revision available on svn. I don't
</I>><i> think submit with a revision number are used much (but maybe I'm wrong ?)
</I>><i> and a branch copied from a revision can be used instead, to do the
</I>><i> same. And not supporting revision numbers will make mgarepo code more
</I>><i> simple.
</I>><i>
</I>><i> - We won't allow submit with a URL, but only with a package name (and
</I>><i> the right URL will be generated by the script receiving the submit request
</I>><i> on pkgsubmit). To allow using branches, instead we add a --branch option
</I>><i> to provide the name of a branch. If no branch name is provided we use
</I>><i> the package from this path :
</I>><i> /packages/cauldron/[packagename]/current
</I>><i> If a branch name is provided we use the package from this path :
</I>><i> /packages/cauldron/[packagename]/branches/[branchname]
</I>><i> And the same path in the binrepo.
</I>><i> Some commands can be added in mgarepo to create, remove, checkout branches.
</I>><i>
</I>><i> With this, the path for branches will be more clear, and the same for
</I>><i> all packages (contrary to Mandriva where packages could have some branches
</I>><i> in /packages/branches, or in /packages/updates, /packages/updates_release
</I>><i> or /packages/cooker or anywhere on the repository).
</I>><i>
</I>><i>
</I>><i> Does anyone see any problem with this ? Or other ideas, or comments ?
</I>
AFAICS the above branch scheme doesn't work well with changelog
generation. As changelog is generated from [packagename]/releases, one
of two things seems bound to happen:
a) There is no [packagename]/releases under the branch, and the
changelog gets messed up (all commits since initial package import in a
single release entry), or
b) One tries to keep [packagename]/releases to preserve sane changelog
when branching, but this will fail as this SVN command is invalid, as
one can't copy a directory into itself:
svn cp /packages/cauldron/[packagename]
/packages/cauldron/[packagename]/branches/[branchname]
Or maybe I'm missing something?
--
Anssi Hannula
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002372.html">[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
</A></li>
<LI>Next message: <A HREF="002374.html">[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2373">[ date ]</a>
<a href="thread.html#2373">[ thread ]</a>
<a href="subject.html#2373">[ subject ]</a>
<a href="author.html#2373">[ 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>
|
