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
|
<!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%0A%09when%09submiting%20packages%20with%20mgarepo&In-Reply-To=%3C20110129143043.GB21938%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="002373.html">
<LINK REL="Next" HREF="002375.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo</H1>
<B>nicolas vigier</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20packages%20branches%20and%20revision%20numbers%0A%09when%09submiting%20packages%20with%20mgarepo&In-Reply-To=%3C20110129143043.GB21938%40mars-attacks.org%3E"
TITLE="[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo">boklm at mars-attacks.org
</A><BR>
<I>Sat Jan 29 15:30:43 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002373.html">[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
</A></li>
<LI>Next message: <A HREF="002375.html">[Mageia-dev] Accident
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2374">[ date ]</a>
<a href="thread.html#2374">[ thread ]</a>
<a href="subject.html#2374">[ subject ]</a>
<a href="author.html#2374">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Sat, 29 Jan 2011, Anssi Hannula wrote:
><i>
</I>><i> AFAICS the above branch scheme doesn't work well with changelog
</I>><i> generation. As changelog is generated from [packagename]/releases, one
</I>><i> of two things seems bound to happen:
</I>><i>
</I>><i> a) There is no [packagename]/releases under the branch, and the
</I>><i> changelog gets messed up (all commits since initial package import in a
</I>><i> single release entry), or
</I>><i>
</I>><i> b) One tries to keep [packagename]/releases to preserve sane changelog
</I>><i> when branching, but this will fail as this SVN command is invalid, as
</I>><i> one can't copy a directory into itself:
</I>><i> svn cp /packages/cauldron/[packagename]
</I>><i> /packages/cauldron/[packagename]/branches/[branchname]
</I>
Good question. I have looked at how it is working now :
- it first looks at all svn logs from [packagename]/releases, and
extract infos from "%repsys markrelease" logs, which contains
infos about packages version, release, and relrevision.
- it use commit logs from [packagename]/current and groups them by
package releases using the infos from markrelease.
So I think we can do this :
- We don't copy releases directory in branches, only SPECS and SOURCES
directories, we share the releases directory for current and branches.
- In "%repsys markrelease" commits, we include the branch name
- When generating logs for a branch package we only use markrelease
infos from that branch, and from current from before the first
markrelease for the branch
- When generating logs for current package, we ignore markrelease from
other branches
Does it look ok ?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002373.html">[Mageia-dev] packages branches and revision numbers when submiting packages with mgarepo
</A></li>
<LI>Next message: <A HREF="002375.html">[Mageia-dev] Accident
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2374">[ date ]</a>
<a href="thread.html#2374">[ thread ]</a>
<a href="subject.html#2374">[ subject ]</a>
<a href="author.html#2374">[ 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>
|
