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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] changing binrepos
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20changing%20binrepos&In-Reply-To=%3C4E1DC7A7.5060504%40eesti.ee%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003717.html">
<LINK REL="Next" HREF="003719.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] changing binrepos</H1>
<B>Sander Lepik</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20changing%20binrepos&In-Reply-To=%3C4E1DC7A7.5060504%40eesti.ee%3E"
TITLE="[Mageia-sysadm] changing binrepos">sander.lepik at eesti.ee
</A><BR>
<I>Wed Jul 13 18:28:23 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003717.html">[Mageia-sysadm] changing binrepos
</A></li>
<LI>Next message: <A HREF="003719.html">[Mageia-sysadm] changing binrepos
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3718">[ date ]</a>
<a href="thread.html#3718">[ thread ]</a>
<a href="subject.html#3718">[ subject ]</a>
<a href="author.html#3718">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>13.07.2011 19:09, nicolas vigier kirjutas:
><i> Hello,
</I>><i>
</I>><i> I think current binrepos is not really perfect :
</I>><i>
</I>><i> - Using separate repository for each release require having multiple
</I>><i> copies of some files
</I>><i> - removing old binary files from history is easier than before, but
</I>><i> still not very simple
</I>><i> - Using the same directory structure as packages (with current and
</I>><i> releases directories) in binrepos is not very usefull I think
</I>><i>
</I>><i> So I think we could replace binrepos svn with something like this :
</I>><i>
</I>><i> - on valstar, a script to upload a file, accessed by ssh using "mgarepo
</I>><i> upload". The script saves all files in the same directory, using
</I>><i> sha1sum for the filename. And the directory is accessible by http.
</I>><i> The script could also take an URL as an argument, so that the file is
</I>><i> downloaded from this URL instead of being uploaded by the packager (for
</I>><i> people with slow connection). The script can also send an email on a
</I>><i> mailing list when a new file is uploaded.
</I>><i> - the uploaded file becomes accessible at this URL :
</I>><i> <A HREF="http://binrepos.mageia.org/files/[sha1sum">http://binrepos.mageia.org/files/[sha1sum</A>]
</I>><i> - the same sha1.lst file as we have now is used to list binary files in
</I>><i> the SOURCES directory
</I>><i> - when doing "mgarepo co" or "mgarepo getsrpm", mgarepo download all
</I>><i> files listed in sha1.lst from <A HREF="http://binrepos.mageia.org/files/...">http://binrepos.mageia.org/files/...</A>
</I>><i> - when a file is no longer used, it is only removed from sha1.lst, not
</I>><i> removed from the server
</I>><i> - If we want to save space, we can have a script to generate the list of
</I>><i> all used files from all packages, and remove files not in this list
</I>><i>
</I>><i> What do you think about this change ?
</I>Sounds like a good idea.
--
Sander
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003717.html">[Mageia-sysadm] changing binrepos
</A></li>
<LI>Next message: <A HREF="003719.html">[Mageia-sysadm] changing binrepos
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3718">[ date ]</a>
<a href="thread.html#3718">[ thread ]</a>
<a href="subject.html#3718">[ subject ]</a>
<a href="author.html#3718">[ 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>
|
