diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20110612')
22 files changed, 774 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20110612/1fc5ea8a/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110612/1fc5ea8a/attachment-0001.html new file mode 100644 index 000000000..3f66851d2 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/1fc5ea8a/attachment-0001.html @@ -0,0 +1,14 @@ +<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><font class="Apple-style-span" face="arial" style="font-size: 10pt; ">Hello,</font><div style="font-size: 10pt; font-family: arial; "><br></div><div style="font-size: 10pt; font-family: arial; ">I hope I am doing this right as I have never used this type of thing before, I will apologize before hand if not.</div><div style="font-size: 10pt; font-family: arial; "><br></div><div style="font-size: 10pt; font-family: arial; ">I wrote a proposal on the forums and I think it is very good and I would like it at the very least just heard and seen if it might work in the ideals of the project. I joined this list to get this out here. I am going to do copy/paste from my original post(s) to get this here.. Post 1:</div><div style="font-size: 10pt; font-family: arial; "><br></div><div style="font-size: 10pt; font-family: arial; "><meta http-equiv="content-type" + content="text/html; charset=utf-8"><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; ">Here is what I propose:<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Unstable- This is the place where it all starts! Packages come from upstream end up here and move forward if no show stopper bugs are found<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Rolling Unstable- Packages that leave Unstable come here to be tested for stability and made stable... + Bleeding edge rolling (Debian Unstable)<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Rolling Stable- Packages that are stable in Rolling Unstable for X amount of time come here.... Stable rolling (Arch)<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Point releases- These releases are taken from the stable rolling release and supported for X amount of time... Security updates only <br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">LTS release- These are rock solid stable (Debian stable) and snap shots from point release on whole number<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; + margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">So we would have unstable (easy to understand), unstable rolling for those who want cutting edge software, stable rolling for those who want to roll stable, point releases for those who like to install every now and then and LTS which after the way down the line should be VERY stable!</span></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; "><br></span></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, + Helvetica, Arial, sans-serif; line-height: 18px; ">Further info:</span></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; "><br></span></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; "><meta http-equiv="content-type" content="text/html; charset=utf-8">1 developer releases 1 package. Package maintainer pulls package into unstable (developers don't make a habit of making crappy packages, stability is judged by the whole system running in harmony). Maintainers job is to make sure it works before it leaves unstable. When the package gains stability in unstable (basically you are able to install the package and have a + usable system) the package moves to the next stage, rolling unstable. Rolling unstable is a test bed of bleeding edge software from the package maintainer for a X amount of time (we are still on this one package). Now, the next time this package moves it is from a scheduled pull, so this package after X amount of time now gets "pulled" into the next phase (rolling stable (as long as there are no show stopper bugs)). From here on out the "team" responsible pulls in packages from up stream (rolling unstable) and the package maintainer just repeats this process in working at the top of the ladder. Security updates and bug fixes can be "pushed" down by the maintainer.<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; + padding-bottom: 0px; padding-left: 0px; ">Where is this hard? Sounds like any other distribution to me... Debian maybe?<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Anyway...<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">2.0 will become an LTS. Not a packaging nightmare at all... A snapshot of rolling stable from a point in time that matures with bug fixes and security updates. Kernel only updates + within kernel branch (2.6.30-XX).<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">2.1 is a point release... Snapshot of rolling unstable (again easy on package maintainer). Supported for X amount of time. Becomes slightly mature as bug fixes and core updates make it so (from stuff already coming down from up stream).<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">So we have 1 package maintainer + working packages that are pushed into rolling unstable (think testing) and trickle on down the line with help from the community team of "distribution" maintainers.<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">One rolling set of packages ever changing like a fine oiled machine. The logic just sounds right to me and very efficient I think...<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">EDIT: If + you wanted to "shorten" the amount of "projects (I guess)" you could omit anything below rolling unstable.<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Rolling unstable for instance could roll into a full fledged release (Not a good idea IMHO)<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Rolling stable we could do without and we would be Debian all over (maybe more bleeding edge on the release)<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; + ">LTS does not have to be... But LTS would be a very good way to get us used on servers...<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Point releases are for those who don't like the rolling model... This is a "showcase" release to show everyone what we are without having to roll <br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Up to anyone really but this model is so versatile it really don't matter. You could omit about any point below the maintainer and have working mechanics.</span></div><div style="font-size: 10pt; font-family: arial; "><span + class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; ">________________________________________________________________________</span></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif" size="2"><span class="Apple-style-span" style="line-height: 18px;">Last post was in response to a disagreement with someone else. To help make my idea more fitting I was suggesting ways within my idea where things can change. Was under the impression the other part thought the idea would be hard on the package maintainer, I didn't and still don't see this problem. With everything being snapshots of the rolling model, maintaining should be very easy.</span></font></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, + Arial, sans-serif" size="2"><span class="Apple-style-span" style="line-height: 18px;"><br></span></font></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif" size="2"><span class="Apple-style-span" style="line-height: 18px;">We could become fully rolling with this model, rolling and stable (debian but with newer packages), rolling unstable with LTS releases, rolling with general releases... Really there are a lot of possibilities based on this model. </span></font></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif" size="2"><span class="Apple-style-span" style="line-height: 18px;"><br></span></font></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif" size="2"><span class="Apple-style-span" + style="line-height: 18px;">I like it...</span></font></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; "><br></span></div><div style="font-size: 10pt; "><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif"><span class="Apple-style-span" style="line-height: 18px;"><br></span></font></div></td></tr></table>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110612/1fc5ea8a/attachment.html b/zarb-ml/mageia-dev/attachments/20110612/1fc5ea8a/attachment.html new file mode 100644 index 000000000..3f66851d2 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/1fc5ea8a/attachment.html @@ -0,0 +1,14 @@ +<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><font class="Apple-style-span" face="arial" style="font-size: 10pt; ">Hello,</font><div style="font-size: 10pt; font-family: arial; "><br></div><div style="font-size: 10pt; font-family: arial; ">I hope I am doing this right as I have never used this type of thing before, I will apologize before hand if not.</div><div style="font-size: 10pt; font-family: arial; "><br></div><div style="font-size: 10pt; font-family: arial; ">I wrote a proposal on the forums and I think it is very good and I would like it at the very least just heard and seen if it might work in the ideals of the project. I joined this list to get this out here. I am going to do copy/paste from my original post(s) to get this here.. Post 1:</div><div style="font-size: 10pt; font-family: arial; "><br></div><div style="font-size: 10pt; font-family: arial; "><meta http-equiv="content-type" + content="text/html; charset=utf-8"><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; ">Here is what I propose:<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Unstable- This is the place where it all starts! Packages come from upstream end up here and move forward if no show stopper bugs are found<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Rolling Unstable- Packages that leave Unstable come here to be tested for stability and made stable... + Bleeding edge rolling (Debian Unstable)<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Rolling Stable- Packages that are stable in Rolling Unstable for X amount of time come here.... Stable rolling (Arch)<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Point releases- These releases are taken from the stable rolling release and supported for X amount of time... Security updates only <br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">LTS release- These are rock solid stable (Debian stable) and snap shots from point release on whole number<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; + margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">So we would have unstable (easy to understand), unstable rolling for those who want cutting edge software, stable rolling for those who want to roll stable, point releases for those who like to install every now and then and LTS which after the way down the line should be VERY stable!</span></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; "><br></span></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, + Helvetica, Arial, sans-serif; line-height: 18px; ">Further info:</span></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; "><br></span></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; "><meta http-equiv="content-type" content="text/html; charset=utf-8">1 developer releases 1 package. Package maintainer pulls package into unstable (developers don't make a habit of making crappy packages, stability is judged by the whole system running in harmony). Maintainers job is to make sure it works before it leaves unstable. When the package gains stability in unstable (basically you are able to install the package and have a + usable system) the package moves to the next stage, rolling unstable. Rolling unstable is a test bed of bleeding edge software from the package maintainer for a X amount of time (we are still on this one package). Now, the next time this package moves it is from a scheduled pull, so this package after X amount of time now gets "pulled" into the next phase (rolling stable (as long as there are no show stopper bugs)). From here on out the "team" responsible pulls in packages from up stream (rolling unstable) and the package maintainer just repeats this process in working at the top of the ladder. Security updates and bug fixes can be "pushed" down by the maintainer.<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; + padding-bottom: 0px; padding-left: 0px; ">Where is this hard? Sounds like any other distribution to me... Debian maybe?<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Anyway...<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">2.0 will become an LTS. Not a packaging nightmare at all... A snapshot of rolling stable from a point in time that matures with bug fixes and security updates. Kernel only updates + within kernel branch (2.6.30-XX).<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">2.1 is a point release... Snapshot of rolling unstable (again easy on package maintainer). Supported for X amount of time. Becomes slightly mature as bug fixes and core updates make it so (from stuff already coming down from up stream).<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">So we have 1 package maintainer + working packages that are pushed into rolling unstable (think testing) and trickle on down the line with help from the community team of "distribution" maintainers.<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">One rolling set of packages ever changing like a fine oiled machine. The logic just sounds right to me and very efficient I think...<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">EDIT: If + you wanted to "shorten" the amount of "projects (I guess)" you could omit anything below rolling unstable.<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Rolling unstable for instance could roll into a full fledged release (Not a good idea IMHO)<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Rolling stable we could do without and we would be Debian all over (maybe more bleeding edge on the release)<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; + ">LTS does not have to be... But LTS would be a very good way to get us used on servers...<br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Point releases are for those who don't like the rolling model... This is a "showcase" release to show everyone what we are without having to roll <br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><br style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; ">Up to anyone really but this model is so versatile it really don't matter. You could omit about any point below the maintainer and have working mechanics.</span></div><div style="font-size: 10pt; font-family: arial; "><span + class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; ">________________________________________________________________________</span></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif" size="2"><span class="Apple-style-span" style="line-height: 18px;">Last post was in response to a disagreement with someone else. To help make my idea more fitting I was suggesting ways within my idea where things can change. Was under the impression the other part thought the idea would be hard on the package maintainer, I didn't and still don't see this problem. With everything being snapshots of the rolling model, maintaining should be very easy.</span></font></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, + Arial, sans-serif" size="2"><span class="Apple-style-span" style="line-height: 18px;"><br></span></font></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif" size="2"><span class="Apple-style-span" style="line-height: 18px;">We could become fully rolling with this model, rolling and stable (debian but with newer packages), rolling unstable with LTS releases, rolling with general releases... Really there are a lot of possibilities based on this model. </span></font></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif" size="2"><span class="Apple-style-span" style="line-height: 18px;"><br></span></font></div><div><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif" size="2"><span class="Apple-style-span" + style="line-height: 18px;">I like it...</span></font></div><div style="font-size: 10pt; font-family: arial; "><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: 'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif; line-height: 18px; "><br></span></div><div style="font-size: 10pt; "><font class="Apple-style-span" color="#333333" face="'Lucida Grande', 'Trebuchet MS', Verdana, Helvetica, Arial, sans-serif"><span class="Apple-style-span" style="line-height: 18px;"><br></span></font></div></td></tr></table>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110612/470d84ba/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110612/470d84ba/attachment-0001.html new file mode 100644 index 000000000..08d543f62 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/470d84ba/attachment-0001.html @@ -0,0 +1 @@ +Hello,<br><br>will we get this as update for Mageia 1? <br clear="all"><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> diff --git a/zarb-ml/mageia-dev/attachments/20110612/470d84ba/attachment.html b/zarb-ml/mageia-dev/attachments/20110612/470d84ba/attachment.html new file mode 100644 index 000000000..08d543f62 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/470d84ba/attachment.html @@ -0,0 +1 @@ +Hello,<br><br>will we get this as update for Mageia 1? <br clear="all"><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> diff --git a/zarb-ml/mageia-dev/attachments/20110612/59929418/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110612/59929418/attachment-0001.html new file mode 100644 index 000000000..bf59c284e --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/59929418/attachment-0001.html @@ -0,0 +1,86 @@ +<div class="gmail_quote">On Sun, Jun 12, 2011 at 3:27 PM, Samuel Verschelde <span dir="ltr"><<a href="mailto:stormi@laposte.net">stormi@laposte.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +Hello to everyone,<br> +<br> +I'm sure there's someone among you who wants to help Mageia but hasn't found<br> +yet the good way to do it. Today is your lucky day, because there's a job<br> +that's available and can be really useful and interesting: coordinating the<br> +packagers mentoring program.<br> +<br> +You know that one key point of success for Mageia is in the ability to welcome<br> +new packagers. The better we will be at it, the better the distro will be. The<br> +packagers mentoring program has been created for that reason and several<br> +packagers have been or are being mentored. But we have some difficulty knowing<br> +who is being mentored by who and who hasn't found a mentor. And we need also<br> +to find more mentors and more apprentices.<br> +<br> +During a packagers weekly meeting, misc invited us to read the following<br> +article about mentoring programs in open-source projects:<br> +<a href="http://blogs.gnome.org/bolsh/2011/05/31/effective-mentoring-programs/" target="_blank">http://blogs.gnome.org/bolsh/2011/05/31/effective-mentoring-programs/</a><br> +<br> +I invite those who haven't read it yet, to read it. I'll quote one of the<br> +mentoring best practices that were given: "In bigger projects, keeping track<br> +of who is a mentor, and who is mentoring who, and inviting new mentors, and<br> +ensuring that no-one falls through the cracks when a mentor gets too busy, is<br> +a job of itself."<br> +<br> +I'm looking for someone who could fill that "job".<br> +<br> +Description of the job:<br> +<br> +- keep track of:<br> +-- who's being mentored by who, how well it's going<br> +-- who needs a mentor and hasn't found one yet (this is one of the most<br> +important parts: no volunteer must be forgotten, volunteers are too precious<br> +!)<br> +-- who can mentor more apprentices (and sometimes convince packagers to become<br> +mentors or accept one more apprentice)<br> +<br> +- be available for questions from apprentices or mentors, by mail, and if<br> +possible, to be present on the IRC channel #mageia-mentoring on freenode<br> +<br> +- help mentors with gathering "junior tasks" (bugzilla is a never empty<br> +reserve that can be used for that. Maybe ask the bug triage team to help<br> +identify such tasks. Maybe a "junior task" keyword in bugzilla would do the<br> +trick)<br> +-- small bugs to fix<br> +-- new small packages to import in the distribution<br> +-- backports<br> +<br> +- promote mentoring (empower users into contributers. Working with the<br> +marketing team would be great I think):<br> +-- make the mentoring program known (MLs, forums, web, etc.)<br> +-- look for new apprentices<br> +-- look for new mentors<br> +<br> +Some useful skills:<br> +- be autonomous (ie no need to check that you're doing the work)<br> +- good written english (communication is very important in this job)<br> +- knowledge about packaging is a plus but not mandatory (the key aspects can<br> +be taught to you)<br> +- being or having been a mentor, or having been mentored would be a plus, but<br> +not mandatory<br> +<br> +More information about the job:<br> +- does not require a big amount of work, but real committment to the task and<br> +regularity<br> +- remember that you have a coordination role, not an authoritative role. The<br> +difference in that is that you're not here to give orders but to facilitate the<br> +mentoring program.<br> +- you don't have to be alone to do this job if it's too much for one person:<br> +you can find other helpful people wanting to help you if needed and rely on the<br> +other teams (but finding them *is* part of your job ;) ).<br> +- this "job offer" concerns everything that revolves around the mentoring of<br> +new packagers, but if it's successful maybe other teams can follow the same<br> +approach (i18n, QA, etc... ).<br> +- depending on your level of confidence, experience and will, you could be<br> +helped in your work. Maybe someone from the council can supervise and help you<br> +at least at the beginning; or, if no one steps up, I can help you bootstrap<br> +and organize your new "job".<br> +<br> +So, who's in?<br> +<font color="#888888"><br> +Samuel Verschelde<br> +<br> +</font></blockquote></div><br>Hello Samuel,<br><br>the offer sounds nice. Maybe I can give it a try?<br><br>What do I already have in my mind?<br><br>- Creating a table on Mageia wiki where someone who wants to be mentored can put his name on, + the date he enters his name (so we can see how long he's waiting for a mentor)<br> +- A table with all available mentors and the actual apprentices<br>- On a regular base asking the mentors if they can mentor someone new or if his apprentice is ready for a full membership<br>- Regular meeting where everyone can vote for a full mentorship of an apprentice<br clear="all"> +<br>So what do you think?<br><br><br><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> diff --git a/zarb-ml/mageia-dev/attachments/20110612/59929418/attachment.html b/zarb-ml/mageia-dev/attachments/20110612/59929418/attachment.html new file mode 100644 index 000000000..bf59c284e --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/59929418/attachment.html @@ -0,0 +1,86 @@ +<div class="gmail_quote">On Sun, Jun 12, 2011 at 3:27 PM, Samuel Verschelde <span dir="ltr"><<a href="mailto:stormi@laposte.net">stormi@laposte.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +Hello to everyone,<br> +<br> +I'm sure there's someone among you who wants to help Mageia but hasn't found<br> +yet the good way to do it. Today is your lucky day, because there's a job<br> +that's available and can be really useful and interesting: coordinating the<br> +packagers mentoring program.<br> +<br> +You know that one key point of success for Mageia is in the ability to welcome<br> +new packagers. The better we will be at it, the better the distro will be. The<br> +packagers mentoring program has been created for that reason and several<br> +packagers have been or are being mentored. But we have some difficulty knowing<br> +who is being mentored by who and who hasn't found a mentor. And we need also<br> +to find more mentors and more apprentices.<br> +<br> +During a packagers weekly meeting, misc invited us to read the following<br> +article about mentoring programs in open-source projects:<br> +<a href="http://blogs.gnome.org/bolsh/2011/05/31/effective-mentoring-programs/" target="_blank">http://blogs.gnome.org/bolsh/2011/05/31/effective-mentoring-programs/</a><br> +<br> +I invite those who haven't read it yet, to read it. I'll quote one of the<br> +mentoring best practices that were given: "In bigger projects, keeping track<br> +of who is a mentor, and who is mentoring who, and inviting new mentors, and<br> +ensuring that no-one falls through the cracks when a mentor gets too busy, is<br> +a job of itself."<br> +<br> +I'm looking for someone who could fill that "job".<br> +<br> +Description of the job:<br> +<br> +- keep track of:<br> +-- who's being mentored by who, how well it's going<br> +-- who needs a mentor and hasn't found one yet (this is one of the most<br> +important parts: no volunteer must be forgotten, volunteers are too precious<br> +!)<br> +-- who can mentor more apprentices (and sometimes convince packagers to become<br> +mentors or accept one more apprentice)<br> +<br> +- be available for questions from apprentices or mentors, by mail, and if<br> +possible, to be present on the IRC channel #mageia-mentoring on freenode<br> +<br> +- help mentors with gathering "junior tasks" (bugzilla is a never empty<br> +reserve that can be used for that. Maybe ask the bug triage team to help<br> +identify such tasks. Maybe a "junior task" keyword in bugzilla would do the<br> +trick)<br> +-- small bugs to fix<br> +-- new small packages to import in the distribution<br> +-- backports<br> +<br> +- promote mentoring (empower users into contributers. Working with the<br> +marketing team would be great I think):<br> +-- make the mentoring program known (MLs, forums, web, etc.)<br> +-- look for new apprentices<br> +-- look for new mentors<br> +<br> +Some useful skills:<br> +- be autonomous (ie no need to check that you're doing the work)<br> +- good written english (communication is very important in this job)<br> +- knowledge about packaging is a plus but not mandatory (the key aspects can<br> +be taught to you)<br> +- being or having been a mentor, or having been mentored would be a plus, but<br> +not mandatory<br> +<br> +More information about the job:<br> +- does not require a big amount of work, but real committment to the task and<br> +regularity<br> +- remember that you have a coordination role, not an authoritative role. The<br> +difference in that is that you're not here to give orders but to facilitate the<br> +mentoring program.<br> +- you don't have to be alone to do this job if it's too much for one person:<br> +you can find other helpful people wanting to help you if needed and rely on the<br> +other teams (but finding them *is* part of your job ;) ).<br> +- this "job offer" concerns everything that revolves around the mentoring of<br> +new packagers, but if it's successful maybe other teams can follow the same<br> +approach (i18n, QA, etc... ).<br> +- depending on your level of confidence, experience and will, you could be<br> +helped in your work. Maybe someone from the council can supervise and help you<br> +at least at the beginning; or, if no one steps up, I can help you bootstrap<br> +and organize your new "job".<br> +<br> +So, who's in?<br> +<font color="#888888"><br> +Samuel Verschelde<br> +<br> +</font></blockquote></div><br>Hello Samuel,<br><br>the offer sounds nice. Maybe I can give it a try?<br><br>What do I already have in my mind?<br><br>- Creating a table on Mageia wiki where someone who wants to be mentored can put his name on, + the date he enters his name (so we can see how long he's waiting for a mentor)<br> +- A table with all available mentors and the actual apprentices<br>- On a regular base asking the mentors if they can mentor someone new or if his apprentice is ready for a full membership<br>- Regular meeting where everyone can vote for a full mentorship of an apprentice<br clear="all"> +<br>So what do you think?<br><br><br><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br> diff --git a/zarb-ml/mageia-dev/attachments/20110612/690b3be7/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110612/690b3be7/attachment-0001.asc new file mode 100644 index 000000000..fc8f10d9e --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/690b3be7/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk31CoMACgkQqEs9DA4DquBNcACfeyWjBHuEBguikK+8LiF0F3MT +N6sAoLewgAUUCvlKYhiHmqL6ZPhBnSiD +=oSL1 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110612/690b3be7/attachment.asc b/zarb-ml/mageia-dev/attachments/20110612/690b3be7/attachment.asc new file mode 100644 index 000000000..fc8f10d9e --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/690b3be7/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk31CoMACgkQqEs9DA4DquBNcACfeyWjBHuEBguikK+8LiF0F3MT +N6sAoLewgAUUCvlKYhiHmqL6ZPhBnSiD +=oSL1 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110612/6a5faa22/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110612/6a5faa22/attachment-0001.html new file mode 100644 index 000000000..844af9528 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/6a5faa22/attachment-0001.html @@ -0,0 +1,17 @@ +Hello,<div>I'm not offer my candidacy, I'm only a simple user.</div><div>But I offer my help as secrtary of the secratary of ...... the coordinator</div><div><br></div><div>As Mageia and I have the same birthday I'm following the upgroth since the beginning.</div> +<div>Also with a little help during qa for the final.</div><div><br></div><div>As I saw some requests for mentoring on the ml, I think it is important to show a quick response.</div><div>So mentoring team can do this, ask for the skill or say look to foo1, foo2 or foo3 on the bug-list</div> +<div>during we are looking for mentor.</div><div>(perhaps the packagers can classify the complexity of new-package-request and "simple" bugs)</div><div><br></div><div>Also very important ist the actuality of the wiki.</div> +<div>So we must have a look on the bug-list, ml and irc not to loose any request for mentoring.</div><div>On the other side we must have/build a very good communicatio to the packagers to avoid double work on packages</div> +<div>and to help for equal distribution of the mentoring work. </div><div><br></div><div>Although not filling the wanted skills (no packager, no being a mentor, not good english knowledge)</div><div>I'm ready to help.</div> +<div><br></div><div>I think some more eyes are always good :-)</div><div><br></div><div>So if I can help call me</div><div><br></div><div>Magnus</div><div><br></div><div>PS: In my job as it-auditor documentation, communication and learning new thinks are the normal things </div> +<div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div>  <br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +<div><div class="h5"><br> +> Some useful skills:<br> +> - be autonomous (ie no need to check that you're doing the work)<br> +> - good written english (communication is very important in this job)<br> +> - knowledge about packaging is a plus but not mandatory (the key aspects can<br> +> be taught to you)<br> +> - being or having been a mentor, or having been mentored would be a plus, but<br> +> not mandatoryI offer my candidacy. I was mentored by shikamaru and i'm a mandriva</div></div> +packager since 2009 and a mageia packager since the start.<br> +My english level is pretty good and i'm pretty sociable.<br><br></blockquote></div></div> diff --git a/zarb-ml/mageia-dev/attachments/20110612/6a5faa22/attachment.html b/zarb-ml/mageia-dev/attachments/20110612/6a5faa22/attachment.html new file mode 100644 index 000000000..844af9528 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/6a5faa22/attachment.html @@ -0,0 +1,17 @@ +Hello,<div>I'm not offer my candidacy, I'm only a simple user.</div><div>But I offer my help as secrtary of the secratary of ...... the coordinator</div><div><br></div><div>As Mageia and I have the same birthday I'm following the upgroth since the beginning.</div> +<div>Also with a little help during qa for the final.</div><div><br></div><div>As I saw some requests for mentoring on the ml, I think it is important to show a quick response.</div><div>So mentoring team can do this, ask for the skill or say look to foo1, foo2 or foo3 on the bug-list</div> +<div>during we are looking for mentor.</div><div>(perhaps the packagers can classify the complexity of new-package-request and "simple" bugs)</div><div><br></div><div>Also very important ist the actuality of the wiki.</div> +<div>So we must have a look on the bug-list, ml and irc not to loose any request for mentoring.</div><div>On the other side we must have/build a very good communicatio to the packagers to avoid double work on packages</div> +<div>and to help for equal distribution of the mentoring work. </div><div><br></div><div>Although not filling the wanted skills (no packager, no being a mentor, not good english knowledge)</div><div>I'm ready to help.</div> +<div><br></div><div>I think some more eyes are always good :-)</div><div><br></div><div>So if I can help call me</div><div><br></div><div>Magnus</div><div><br></div><div>PS: In my job as it-auditor documentation, communication and learning new thinks are the normal things </div> +<div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div>  <br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +<div><div class="h5"><br> +> Some useful skills:<br> +> - be autonomous (ie no need to check that you're doing the work)<br> +> - good written english (communication is very important in this job)<br> +> - knowledge about packaging is a plus but not mandatory (the key aspects can<br> +> be taught to you)<br> +> - being or having been a mentor, or having been mentored would be a plus, but<br> +> not mandatoryI offer my candidacy. I was mentored by shikamaru and i'm a mandriva</div></div> +packager since 2009 and a mageia packager since the start.<br> +My english level is pretty good and i'm pretty sociable.<br><br></blockquote></div></div> diff --git a/zarb-ml/mageia-dev/attachments/20110612/6d7f16e1/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110612/6d7f16e1/attachment-0001.asc new file mode 100644 index 000000000..8578c8535 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/6d7f16e1/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk31MegACgkQqEs9DA4DquAdxgCgpKtk2hppZM4f3NO2TEpGki6j +PoMAniefGoVzuSFjwHOWUdXz2CHyeWUo +=fJBs +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110612/6d7f16e1/attachment.asc b/zarb-ml/mageia-dev/attachments/20110612/6d7f16e1/attachment.asc new file mode 100644 index 000000000..8578c8535 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/6d7f16e1/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk31MegACgkQqEs9DA4DquAdxgCgpKtk2hppZM4f3NO2TEpGki6j +PoMAniefGoVzuSFjwHOWUdXz2CHyeWUo +=fJBs +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110612/99d16db2/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110612/99d16db2/attachment-0001.html new file mode 100644 index 000000000..e6072e0a1 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/99d16db2/attachment-0001.html @@ -0,0 +1,36 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> +<html><head><meta name="qrichtext" content="1" /><style type="text/css"> +p, li { white-space: pre-wrap; } +</style></head><body style=" font-family:'Sans Serif'; font-size:10pt; font-weight:400; font-style:normal;"> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Le dimanche 12 juin 2011 17:43:38, Daniel Kreuter a écrit :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Hello Samuel,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> the offer sounds nice. Maybe I can give it a try?</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I feared I would get no volunteer, so I sure won't say no ! I just want to wait a bit just in case there would be several volunteers, but I'm really glad you proposed your help :)</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> What do I already have in my mind?</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - Creating a table on Mageia wiki where someone who wants to be mentored</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> can put his name on, + the date he enters his name (so we can see how long</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> he's waiting for a mentor)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - A table with all available mentors and the actual apprentices</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Those already exist but need to be maintained because they're often out of date : http://mageia.org/wiki/doku.php?id=packages_mentoring</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">But this page must not be the only place where you should look for apprentices. IIRC the standard procedure is to create a mentoring request on bugzilla (or is it only to ask for an account ?), and we must not forget those who ask in the mailing lists.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - On a regular base asking the mentors if they can mentor someone new or if</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> his apprentice is ready for a full membership</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">This would be great yes.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - Regular meeting where everyone can vote for a full mentorship of an</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> apprentice</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I don't know if this is needed in your "job", because AFAIK each mentors decides alone when his apprentice is ready.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Best regards</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Samuel</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110612/99d16db2/attachment.html b/zarb-ml/mageia-dev/attachments/20110612/99d16db2/attachment.html new file mode 100644 index 000000000..e6072e0a1 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/99d16db2/attachment.html @@ -0,0 +1,36 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> +<html><head><meta name="qrichtext" content="1" /><style type="text/css"> +p, li { white-space: pre-wrap; } +</style></head><body style=" font-family:'Sans Serif'; font-size:10pt; font-weight:400; font-style:normal;"> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Le dimanche 12 juin 2011 17:43:38, Daniel Kreuter a écrit :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Hello Samuel,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> the offer sounds nice. Maybe I can give it a try?</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I feared I would get no volunteer, so I sure won't say no ! I just want to wait a bit just in case there would be several volunteers, but I'm really glad you proposed your help :)</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> What do I already have in my mind?</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - Creating a table on Mageia wiki where someone who wants to be mentored</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> can put his name on, + the date he enters his name (so we can see how long</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> he's waiting for a mentor)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - A table with all available mentors and the actual apprentices</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Those already exist but need to be maintained because they're often out of date : http://mageia.org/wiki/doku.php?id=packages_mentoring</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">But this page must not be the only place where you should look for apprentices. IIRC the standard procedure is to create a mentoring request on bugzilla (or is it only to ask for an account ?), and we must not forget those who ask in the mailing lists.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - On a regular base asking the mentors if they can mentor someone new or if</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> his apprentice is ready for a full membership</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">This would be great yes.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - Regular meeting where everyone can vote for a full mentorship of an</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> apprentice</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I don't know if this is needed in your "job", because AFAIK each mentors decides alone when his apprentice is ready.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Best regards</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Samuel</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110612/addf59a4/attachment-0001.ksh b/zarb-ml/mageia-dev/attachments/20110612/addf59a4/attachment-0001.ksh new file mode 100644 index 000000000..b47f1e3cb --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/addf59a4/attachment-0001.ksh @@ -0,0 +1,195 @@ +%define name get-skype +%define version 2.2.0.35 +%define release %mkrel 7 +%define instdir %{_datadir}/skype +%define langdir %{instdir}/lang +%define avatardir %{instdir}/avatars +%define sounddir %{instdir}/sounds +%define icondir %{instdir}/icons +%define md5 6e28002c0086fae5206e2d242c3edcfa +%define mytmp %{_localstatedir}/lib/%{name} + +Summary: Download and Install Skype. +Name: %{name} +Version: %{version} +Release: %{release} +License: Proprietary +Group: Networking/Instant messaging +URL: http://www.skype.com +Buildarch: noarch +Requires: wget +Requires: liblcms1 +Requires: libmng1 +Requires: libqtcore4 +Requires: libqtdbus4 +Requires: libqtnetwork4 +Requires: libqtgui4 +Requires: libqtsvg4 +Requires: libqtxml4 +Requires: libxscrnsaver1 +Requires: libxv1 +Requires: libv4l-wrappers + +# The following are lists of filenames (124 in total) placed +# in versioned text files to save clutter in the spec file. +Source0: avatars-%{version}.txt +Source1: sounds-%{version}.txt +Source2: lang-%{version}.txt + +%description + +This is an installer for Skype-%{version}. + +This package does not contain any files as the Skype license does not allow distribution. +By installing this package you will download and install Skype from skype.com. +You must accept the Skype EULA before using it. +Please be patient, this is a 23MB download and may take some time. +Uninstalling this package will uninstall Skype from your system. + +%pre + +mkdir %{mytmp} +[[ -d %{mytmp} ]] || exit 1 +cd %{mytmp} +wget -nc "http://download.skype.com/linux/skype-%{version}.tar.bz2" + +md5chk=$(md5sum skype-%{version}.tar.bz2 | cut -d' ' -f1) +if [[ %{md5} != $md5chk ]]; then +rm skype-%{version}.tar.bz2 +cd .. +rm -r %{mytmp} +echo "Error - download checksum failed" +exit 1 +fi + +%install + +rm -rf $RPM_BUILD_ROOT +install -d -m 0755 %buildroot%{_bindir} +install -d -m 0755 %buildroot%{_datadir}/applications +touch %buildroot%{_datadir}/applications/skype.desktop + +install -d -m 0755 %buildroot%{instdir} +touch %buildroot%{instdir}/{skype.desktop,skype,skype.conf,LICENSE,README} + +install -d -m 0755 %buildroot%{langdir} +while read line; do +touch %buildroot%{langdir}/skype_"$line" +done < %{SOURCE2} + +install -d -m 0755 %buildroot%{instdir}/icons +install -d -m 0755 %buildroot%{_iconsdir} +touch %buildroot%{_iconsdir}/skype.png +for i in 16 32 48; do +touch %buildroot%{_iconsdir}/SkypeBlue_${i}x${i}.png +touch %buildroot%{instdir}/icons/SkypeBlue_${i}x${i}.png +done + +install -d -m 0755 %buildroot%{avatardir} +while read line; do +touch %buildroot%{avatardir}/"$line" +done < %{SOURCE0} + +install -d -m 0755 %buildroot%{sounddir} +while read line; do +touch %buildroot%{sounddir}/"$line" +done < %{SOURCE1} + +echo "LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so %{instdir}/skype"\ + > %buildroot%{_bindir}/skype && chmod +x %buildroot%{_bindir}/skype + +%post + +tmpextdir=$(mktemp -d) +if ! [[ -d $tmpextdir ]]; then +echo "Failed to create temporary directory" +rm -r %{mytmp} +exit 1 +fi + +%define tmpdir ${tmpextdir}/skype-%{version} + +cd ${tmpextdir} +tar jxf %{mytmp}/skype-%{version}.tar.bz2 + +if ! [[ -d %{tmpdir} ]]; then +echo "Extracted file folder missing" +cd .. +rm -rf ${tmpextdir} +rm -r %{mytmp} +exit 1 +fi + + +mkdir -p %{instdir} + +cp -a %{tmpdir}/icons/* %{_iconsdir} +cp -a %{_iconsdir}/SkypeBlue_48x48.png %{_iconsdir}/skype.png +cp -a %{tmpdir}/skype.desktop %{_datadir}/applications/ +mv %{tmpdir}/skype %{instdir} +mv %{tmpdir}/skype.desktop %{instdir} +mv %{tmpdir}/skype.conf %{instdir} +mv %{tmpdir}/LICENSE %{instdir} +mv %{tmpdir}/README %{instdir} +mv %{tmpdir}/avatars %{instdir} +mv %{tmpdir}/lang %{langdir} +mv %{tmpdir}/sounds %{sounddir} +mv %{tmpdir}/icons %{icondir} +rm -r %{tmpdir} +cd .. +rm -r ${tmpextdir} +rm -r %{mytmp} + +%clean + +rm -rf $RPM_BUILD_ROOT + +%files + +%defattr(-,root,root) +%{_bindir}/skype + +# If any extra files are added in install then +# corresponding ghost files need to be added here +%ghost %{_iconsdir}/skype.png +%ghost %{_iconsdir}/SkypeBlue_*.png +%ghost %{_datadir}/applications/skype.desktop +%ghost %{instdir} + +%changelog + +* Sun Jun 12 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-7.mga1 +- Added tests for failed directory creation, exiting with cleanup. +- Added note in %post. +- Removed resource option on launch command line as we use default. + +* Sat Jun 11 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-6.mga1 +- Added md5sum check on download and cleanup on fail. +- Downloads to /var/lib/get-skype - removed after install. +- Creates unique /tmp/tmp.xxxx dir for extraction of tar. +- Added versioning to .txt files. +- Added removal of all tmp directories after install. +- Corrected URL: + +* Thu Jun 9 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-5.mga1 +- Bumped release to test update - no changes + +* Thu Jun 9 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-4.mga1 +- Moved installation to /usr/share instead of /opt +- Changed group and license +- Changed temporary dir +- Changed to wget for d/l + +* Mon Jun 6 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-2.mga1 +- Moved download to %pre to stop install if d/l fails + +* Sun Jun 5 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-1.mga1 +- Changed get-skype version to follow Skype version. +- Changed URL to directly download only correct version. +- A copy of the downloaded file is retained in /tmp/skype-%{version} to +- speed re-installation (unless you clean /tmp) + +* Sat Jun 4 2011 Barry Jackson <zen25000@zen.co.uk> 0.2.mga1 +- Now all files are registered in rpm database. +- lang, avatar and sound filenames supplied in source files. + diff --git a/zarb-ml/mageia-dev/attachments/20110612/addf59a4/attachment.ksh b/zarb-ml/mageia-dev/attachments/20110612/addf59a4/attachment.ksh new file mode 100644 index 000000000..b47f1e3cb --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/addf59a4/attachment.ksh @@ -0,0 +1,195 @@ +%define name get-skype +%define version 2.2.0.35 +%define release %mkrel 7 +%define instdir %{_datadir}/skype +%define langdir %{instdir}/lang +%define avatardir %{instdir}/avatars +%define sounddir %{instdir}/sounds +%define icondir %{instdir}/icons +%define md5 6e28002c0086fae5206e2d242c3edcfa +%define mytmp %{_localstatedir}/lib/%{name} + +Summary: Download and Install Skype. +Name: %{name} +Version: %{version} +Release: %{release} +License: Proprietary +Group: Networking/Instant messaging +URL: http://www.skype.com +Buildarch: noarch +Requires: wget +Requires: liblcms1 +Requires: libmng1 +Requires: libqtcore4 +Requires: libqtdbus4 +Requires: libqtnetwork4 +Requires: libqtgui4 +Requires: libqtsvg4 +Requires: libqtxml4 +Requires: libxscrnsaver1 +Requires: libxv1 +Requires: libv4l-wrappers + +# The following are lists of filenames (124 in total) placed +# in versioned text files to save clutter in the spec file. +Source0: avatars-%{version}.txt +Source1: sounds-%{version}.txt +Source2: lang-%{version}.txt + +%description + +This is an installer for Skype-%{version}. + +This package does not contain any files as the Skype license does not allow distribution. +By installing this package you will download and install Skype from skype.com. +You must accept the Skype EULA before using it. +Please be patient, this is a 23MB download and may take some time. +Uninstalling this package will uninstall Skype from your system. + +%pre + +mkdir %{mytmp} +[[ -d %{mytmp} ]] || exit 1 +cd %{mytmp} +wget -nc "http://download.skype.com/linux/skype-%{version}.tar.bz2" + +md5chk=$(md5sum skype-%{version}.tar.bz2 | cut -d' ' -f1) +if [[ %{md5} != $md5chk ]]; then +rm skype-%{version}.tar.bz2 +cd .. +rm -r %{mytmp} +echo "Error - download checksum failed" +exit 1 +fi + +%install + +rm -rf $RPM_BUILD_ROOT +install -d -m 0755 %buildroot%{_bindir} +install -d -m 0755 %buildroot%{_datadir}/applications +touch %buildroot%{_datadir}/applications/skype.desktop + +install -d -m 0755 %buildroot%{instdir} +touch %buildroot%{instdir}/{skype.desktop,skype,skype.conf,LICENSE,README} + +install -d -m 0755 %buildroot%{langdir} +while read line; do +touch %buildroot%{langdir}/skype_"$line" +done < %{SOURCE2} + +install -d -m 0755 %buildroot%{instdir}/icons +install -d -m 0755 %buildroot%{_iconsdir} +touch %buildroot%{_iconsdir}/skype.png +for i in 16 32 48; do +touch %buildroot%{_iconsdir}/SkypeBlue_${i}x${i}.png +touch %buildroot%{instdir}/icons/SkypeBlue_${i}x${i}.png +done + +install -d -m 0755 %buildroot%{avatardir} +while read line; do +touch %buildroot%{avatardir}/"$line" +done < %{SOURCE0} + +install -d -m 0755 %buildroot%{sounddir} +while read line; do +touch %buildroot%{sounddir}/"$line" +done < %{SOURCE1} + +echo "LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so %{instdir}/skype"\ + > %buildroot%{_bindir}/skype && chmod +x %buildroot%{_bindir}/skype + +%post + +tmpextdir=$(mktemp -d) +if ! [[ -d $tmpextdir ]]; then +echo "Failed to create temporary directory" +rm -r %{mytmp} +exit 1 +fi + +%define tmpdir ${tmpextdir}/skype-%{version} + +cd ${tmpextdir} +tar jxf %{mytmp}/skype-%{version}.tar.bz2 + +if ! [[ -d %{tmpdir} ]]; then +echo "Extracted file folder missing" +cd .. +rm -rf ${tmpextdir} +rm -r %{mytmp} +exit 1 +fi + + +mkdir -p %{instdir} + +cp -a %{tmpdir}/icons/* %{_iconsdir} +cp -a %{_iconsdir}/SkypeBlue_48x48.png %{_iconsdir}/skype.png +cp -a %{tmpdir}/skype.desktop %{_datadir}/applications/ +mv %{tmpdir}/skype %{instdir} +mv %{tmpdir}/skype.desktop %{instdir} +mv %{tmpdir}/skype.conf %{instdir} +mv %{tmpdir}/LICENSE %{instdir} +mv %{tmpdir}/README %{instdir} +mv %{tmpdir}/avatars %{instdir} +mv %{tmpdir}/lang %{langdir} +mv %{tmpdir}/sounds %{sounddir} +mv %{tmpdir}/icons %{icondir} +rm -r %{tmpdir} +cd .. +rm -r ${tmpextdir} +rm -r %{mytmp} + +%clean + +rm -rf $RPM_BUILD_ROOT + +%files + +%defattr(-,root,root) +%{_bindir}/skype + +# If any extra files are added in install then +# corresponding ghost files need to be added here +%ghost %{_iconsdir}/skype.png +%ghost %{_iconsdir}/SkypeBlue_*.png +%ghost %{_datadir}/applications/skype.desktop +%ghost %{instdir} + +%changelog + +* Sun Jun 12 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-7.mga1 +- Added tests for failed directory creation, exiting with cleanup. +- Added note in %post. +- Removed resource option on launch command line as we use default. + +* Sat Jun 11 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-6.mga1 +- Added md5sum check on download and cleanup on fail. +- Downloads to /var/lib/get-skype - removed after install. +- Creates unique /tmp/tmp.xxxx dir for extraction of tar. +- Added versioning to .txt files. +- Added removal of all tmp directories after install. +- Corrected URL: + +* Thu Jun 9 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-5.mga1 +- Bumped release to test update - no changes + +* Thu Jun 9 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-4.mga1 +- Moved installation to /usr/share instead of /opt +- Changed group and license +- Changed temporary dir +- Changed to wget for d/l + +* Mon Jun 6 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-2.mga1 +- Moved download to %pre to stop install if d/l fails + +* Sun Jun 5 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-1.mga1 +- Changed get-skype version to follow Skype version. +- Changed URL to directly download only correct version. +- A copy of the downloaded file is retained in /tmp/skype-%{version} to +- speed re-installation (unless you clean /tmp) + +* Sat Jun 4 2011 Barry Jackson <zen25000@zen.co.uk> 0.2.mga1 +- Now all files are registered in rpm database. +- lang, avatar and sound filenames supplied in source files. + diff --git a/zarb-ml/mageia-dev/attachments/20110612/c9a07f06/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110612/c9a07f06/attachment-0001.asc new file mode 100644 index 000000000..9f7ea9f1b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/c9a07f06/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk31BwwACgkQqEs9DA4DquA17ACdGVlmv3IQUrUuwp3nPRbpRxq2 +9wcAoKIHurz6ofVdvKbH1HxE/0ZLxcez +=EbAp +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110612/c9a07f06/attachment.asc b/zarb-ml/mageia-dev/attachments/20110612/c9a07f06/attachment.asc new file mode 100644 index 000000000..9f7ea9f1b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/c9a07f06/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk31BwwACgkQqEs9DA4DquA17ACdGVlmv3IQUrUuwp3nPRbpRxq2 +9wcAoKIHurz6ofVdvKbH1HxE/0ZLxcez +=EbAp +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110612/d793c819/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110612/d793c819/attachment-0001.asc new file mode 100644 index 000000000..23ae1808e --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/d793c819/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk30sE4ACgkQqEs9DA4DquBPeACbB7m6/Zi13JI0mykalXt/xZlZ +ehsAmwaFp/PrhRLFgc7RmH+Ay2k2A159 +=k5gb +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110612/d793c819/attachment.asc b/zarb-ml/mageia-dev/attachments/20110612/d793c819/attachment.asc new file mode 100644 index 000000000..23ae1808e --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/d793c819/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk30sE4ACgkQqEs9DA4DquBPeACbB7m6/Zi13JI0mykalXt/xZlZ +ehsAmwaFp/PrhRLFgc7RmH+Ay2k2A159 +=k5gb +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110612/dbbb4aa2/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110612/dbbb4aa2/attachment-0001.html new file mode 100644 index 000000000..a216c7375 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/dbbb4aa2/attachment-0001.html @@ -0,0 +1,10 @@ +<br><br><div class="gmail_quote">2011/6/12 Angelo Naselli <span dir="ltr"><<a href="mailto:anaselli@linux.it">anaselli@linux.it</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +In data domenica 12 giugno 2011 01:37:53, Barry Jackson ha scritto:<br> +> > - Dot in Summary.<br> +><br> +> ?? I don't see one.<br> +Summary: Â Â Â Â Download and Install Skype. <------<br> +<br> +Cheers,<br> +--<br> +<font color="#888888"> Â Â Â Â Angelo<br></font></blockquote><div><br></div><div>finally back on dl-stuff ? :)Â </div></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20110612/dbbb4aa2/attachment.html b/zarb-ml/mageia-dev/attachments/20110612/dbbb4aa2/attachment.html new file mode 100644 index 000000000..a216c7375 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110612/dbbb4aa2/attachment.html @@ -0,0 +1,10 @@ +<br><br><div class="gmail_quote">2011/6/12 Angelo Naselli <span dir="ltr"><<a href="mailto:anaselli@linux.it">anaselli@linux.it</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +In data domenica 12 giugno 2011 01:37:53, Barry Jackson ha scritto:<br> +> > - Dot in Summary.<br> +><br> +> ?? I don't see one.<br> +Summary: Â Â Â Â Download and Install Skype. <------<br> +<br> +Cheers,<br> +--<br> +<font color="#888888"> Â Â Â Â Angelo<br></font></blockquote><div><br></div><div>finally back on dl-stuff ? :)Â </div></div><br> |