summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20120420/007068.html
blob: af284d3387daf1a1221c81f358048dc8fb94739d (plain)
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
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-discuss] A proposal of some kind to get point of views &amp; comments
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20A%20proposal%20of%20some%20kind%20to%20get%20point%20of%20views%0A%20%26%20comments&In-Reply-To=%3C4F91CB62.60906%40gmx.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="007065.html">
   <LINK REL="Next"  HREF="007063.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-discuss] A proposal of some kind to get point of views &amp; comments</H1>
    <B>Sebastian sebsebseb</B> 
    <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20A%20proposal%20of%20some%20kind%20to%20get%20point%20of%20views%0A%20%26%20comments&In-Reply-To=%3C4F91CB62.60906%40gmx.com%3E"
       TITLE="[Mageia-discuss] A proposal of some kind to get point of views &amp; comments">sebsebseb_mageia at gmx.com
       </A><BR>
    <I>Fri Apr 20 22:47:30 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="007065.html">[Mageia-discuss] A proposal of some kind to get point of views &amp;	comments
</A></li>
        <LI>Next message: <A HREF="007063.html">[Mageia-discuss] Configuring external monitor display
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#7068">[ date ]</a>
              <a href="thread.html#7068">[ thread ]</a>
              <a href="subject.html#7068">[ subject ]</a>
              <a href="author.html#7068">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On 20/04/12 19:27, Kristoffer Grundstr&#246;m wrote:
&gt;<i> Hi!
</I>&gt;<i>
</I>&gt;<i> Now &amp; then I tend to loose my mind &amp; install Ubuntu on one of my 
</I>&gt;<i> computers &amp; the last time I did it I heard about PPA's. I added a PPA 
</I>&gt;<i> &amp; noticed how fun it was to test the code that it offers.
</I>&gt;<i>
</I>&gt;<i> This is the explanation of what PPA is &amp; does according to the 
</I>&gt;<i> Ubuntu-page:
</I>&gt;<i>
</I>&gt;<i> *&quot;Personal Package Archives (PPA) allow you to upload Ubuntu source 
</I>&gt;<i> packages to be built and published as an apt repository by Launchpad.&quot;*
</I>&gt;<i>
</I>&gt;<i> My idea would be something similar.
</I>&gt;<i>
</I>&gt;<i> It starts with the user that gets annoyed how some Mageia-packages 
</I>&gt;<i> that are meant to be stable that they aren't.
</I>&gt;<i> Instead of having to do the job themselves they can just add a special 
</I>&gt;<i> media called user-contrib that contains packages built from git-source 
</I>&gt;<i> to be tested in Cauldron &amp; then released as Backport-version when 
</I>&gt;<i> confirmed stable enough to see if the issue they had on the officially 
</I>&gt;<i> stable package is gone.
</I>&gt;<i>
</I>&gt;<i> I know that it would take many people to build thoose, but I'm willing 
</I>&gt;<i> to download git-code &amp; compile &amp; build for Mageia.
</I>&gt;<i>
</I>&gt;<i> I've already managed to compile &amp; build the latest official version of 
</I>&gt;<i> Transmission without using the official Mageia patches &amp; I've got NO 
</I>&gt;<i> problem at all using the package.
</I>&gt;<i>
</I>&gt;<i> Test theese packages &amp; say what you think:
</I>&gt;<i>
</I>&gt;<i> <A HREF="http://199.91.153.84/c75b5l1s469g/yljxa1e92l5mmix/transmission-debug-2.51%2B-1.x86_64.rpm">http://199.91.153.84/c75b5l1s469g/yljxa1e92l5mmix/transmission-debug-2.51%2B-1.x86_64.rpm</A>
</I>&gt;<i>
</I>&gt;<i> <A HREF="http://199.91.152.243/2wm8pbg3k5eg/9th0m5xxslth99a/transmission-2.51%2B-1.x86_64.rpm">http://199.91.152.243/2wm8pbg3k5eg/9th0m5xxslth99a/transmission-2.51%2B-1.x86_64.rpm</A>
</I>&gt;<i>
</I>&gt;<i> /Kristoffer
</I>
Hi

I have thought about it before how it could be useful after Mageia 2 has 
been released for there to be PPA's or something like it for Mageia.

With Ubuntu PPA's are really just repo's that can be added by users so 
that they can get later versions of software that aren't in the Ubuntu 
repo's. With PPA's it's meant to be known as well that they may be 
buggy, because usually they have just been made by developers/packagers 
or something like that I think, and not gone through a proper Quality 
Assurance process. Really they are meant to be aimed at more experienced 
users, but it seems that more recently since 2008 or something like 
that, that quite a lot of less experienced Ubuntu users may also have at 
least one PPA installed. Also to many installed PPA's can cause issues 
with the Ubuntu install.

I have been thinking before about the current Mageia release cycle and 
when it comes to Gnome. Since the 9 months release cycle for example, it 
seems that sometimes a new major version of Gnome will have to be 
skipped, as in not offered by Mageia as an update for any supported 
stable final release at the time.  I am not a developer, but I assume 
those versions of Gnome can be put into Cauldron and then backported to 
the current stable release as well, or put into something like a PPA for 
users to install into final Mageia releases. As for Cauldron it should 
keep on having the latest versions of Gnome, usually development versions.

In general most Desktop Linux users want the latest final versions of 
the software that they use it seems, and I think that it would be good 
if there was a easy way to offer this for most or all packages. This is 
where something like Ubuntu's PPA's would come in.

I think if Mageia has something like PPA's, they shouldn't need to 
require QA from the QA team and it should be known users and potential 
users that they may be buggy/unstable.  Where as backports of course 
will have gone through the Mageia QA team process.

As for the PPA's themselves or the something like it, would need a 
website for it like they have for Ubuntu 
<A HREF="https://launchpad.net/ubuntu/+ppas">https://launchpad.net/ubuntu/+ppas</A> and they should only be offered on 
the site from people who have gone through the Mageia packaging process 
and become trusted packagers I think.

<A HREF="http://www.makeuseof.com/tag/ubuntu-ppa-technology-explained/">http://www.makeuseof.com/tag/ubuntu-ppa-technology-explained/</A>

<A HREF="https://help.launchpad.net/Packaging/PPA">https://help.launchpad.net/Packaging/PPA</A>

 From Sebastian sebsebseb


-------------- next part --------------
An HTML attachment was scrubbed...
URL: &lt;/pipermail/mageia-discuss/attachments/20120420/4eeecfb3/attachment-0001.html&gt;
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="007065.html">[Mageia-discuss] A proposal of some kind to get point of views &amp;	comments
</A></li>
	<LI>Next message: <A HREF="007063.html">[Mageia-discuss] Configuring external monitor display
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#7068">[ date ]</a>
              <a href="thread.html#7068">[ thread ]</a>
              <a href="subject.html#7068">[ subject ]</a>
              <a href="author.html#7068">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>