diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/attachments/20110613 | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20110613')
40 files changed, 1012 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20110613/1149e3a9/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/1149e3a9/attachment-0001.html new file mode 100644 index 000000000..826a9c62f --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/1149e3a9/attachment-0001.html @@ -0,0 +1,17 @@ +<!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:'DejaVu Sans [unknown]'; font-size:9pt; 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;">Barry Jackson <zen25000@zen.co.uk> schrieb am 13.06.2011</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 13/06/11 09:17, Angelo Naselli wrote:</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;">> > IIRC rpmlint should tell you as a warning.</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;">> Thanks Angelo,</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 never used rpmlint before, so I installed it.</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;">> It did not warn about the dot, but it did pick up a few spaces/tabs</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;">> etc. There is a warning about Group: Networking/Instant messaging</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;">> being non-standard, however this is used by the pidgin package.</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;">Have you also installed rpmlint-mageia-policy?</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;">Otherwise rpmlint will give you quite some warnings about Mageia specific things.</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;">Oliver</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/1149e3a9/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/1149e3a9/attachment.html new file mode 100644 index 000000000..826a9c62f --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/1149e3a9/attachment.html @@ -0,0 +1,17 @@ +<!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:'DejaVu Sans [unknown]'; font-size:9pt; 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;">Barry Jackson <zen25000@zen.co.uk> schrieb am 13.06.2011</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 13/06/11 09:17, Angelo Naselli wrote:</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;">> > IIRC rpmlint should tell you as a warning.</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;">> Thanks Angelo,</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 never used rpmlint before, so I installed it.</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;">> It did not warn about the dot, but it did pick up a few spaces/tabs</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;">> etc. There is a warning about Group: Networking/Instant messaging</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;">> being non-standard, however this is used by the pidgin package.</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;">Have you also installed rpmlint-mageia-policy?</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;">Otherwise rpmlint will give you quite some warnings about Mageia specific things.</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;">Oliver</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment-0001.ksh b/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment-0001.ksh new file mode 100644 index 000000000..6a315f788 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment-0001.ksh @@ -0,0 +1,63 @@ +#!/bin/bash +# +# Save this file as skype-txt-gen in your home folder +# $ chmod +x skype-txt-gen +# Extract the new skype tarball into your home folder which should create a folder e.g. ~/skype-2.2.0.35 +# Run this script and copy the three output txt files to the SOURCES folder in your rpm build tree. +# +######################################################### + +if [[ ${#1} = 0 ]]; then +echo "Usage: $ ./skype-txt-gen <version>" +echo "example: $ ./skype-txt-gen 2.2.0.35" +exit 1 +fi +version=$1 +if ! [[ -d skype-$version ]]; then +echo "Directory skype-$version is missing" +exit 1 +fi +dirname="skype-sources-$version" +rm -rf "$dirname" +mkdir "$dirname" +cd skype-"$version" + +getavatars() +{ +rm -f ../"$dirname"/avatars-"$version".txt +cd avatars +for item in * +do +echo $item >> ../../"$dirname"/avatars-"$version".txt +done +cd .. +} + +getsounds() +{ +rm -f ../"$dirname/"sounds-"$version".txt +cd sounds +for item in * +do +echo $item >> ../../"$dirname"/sounds-"$version".txt +done +cd .. +} + +getlang() +{ +rm -f ../"$dirname"/lang-"$version".txt +cd lang +for item in * +do +echo $item >> ../../"$dirname"/lang-"$version".txt +done +cd .. +sed -i 's/skype_//g' ../"$dirname"/lang-"$version".txt +} + +getavatars +getsounds +getlang + +echo "The text files have been created in ~/$dirname"
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment-0002.ksh b/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment-0002.ksh new file mode 100644 index 000000000..4cf4c9ee8 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment-0002.ksh @@ -0,0 +1,201 @@ +%define name get-skype +%define version 2.2.0.35 +%define release %mkrel 9 +%define instdir %{_datadir}/skype +%define langdir %{instdir}/lang +%define avatardir %{instdir}/avatars +%define sounddir %{instdir}/sounds +%define icondir %{instdir}/icons +%define md5 6e28002c0086fae5206e2d242c3edcfa +%define tmp_download_dir %{_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 %{tmp_download_dir} +[[ -d %{tmp_download_dir} ]] || exit 1 +cd %{tmp_download_dir} || exit 1 +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 %{tmp_download_dir} +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 + +tmp_extract_dir=$(mktemp -d) +if ! [[ -d $tmp_extract_dir ]]; then +echo "Failed to create temporary directory" +rm -r %{tmp_download_dir} +exit 1 +fi + +%define tmp_skype_dir ${tmp_extract_dir}/skype-%{version} + +cd ${tmp_extract_dir} +tar jxf %{tmp_download_dir}/skype-%{version}.tar.bz2 + +if ! [[ -d %{tmp_skype_dir} ]]; then +echo "Extracted file folder missing" +cd .. +rm -rf ${tmp_extract_dir} +rm -r %{tmp_download_dir} +exit 1 +fi + +# If any extra files are installed here then +# corresponding ghost files need to be added in files + +mkdir -p %{instdir} + +cp -a %{tmp_skype_dir}/icons/* %{_iconsdir} +cp -a %{_iconsdir}/SkypeBlue_48x48.png %{_iconsdir}/skype.png +cp -a %{tmp_skype_dir}/skype.desktop %{_datadir}/applications/ +mv %{tmp_skype_dir}/skype %{instdir} +mv %{tmp_skype_dir}/skype.desktop %{instdir} +mv %{tmp_skype_dir}/skype.conf %{instdir} +mv %{tmp_skype_dir}/LICENSE %{instdir} +mv %{tmp_skype_dir}/README %{instdir} +mv %{tmp_skype_dir}/avatars %{instdir} +mv %{tmp_skype_dir}/lang %{langdir} +mv %{tmp_skype_dir}/sounds %{sounddir} +mv %{tmp_skype_dir}/icons %{icondir} +rm -r %{tmp_skype_dir} +cd .. +rm -r ${tmp_extract_dir} +rm -r %{tmp_download_dir} + +%clean + +rm -rf $RPM_BUILD_ROOT + +%files + +%defattr(-,root,root) +%{_bindir}/skype +%ghost %{_iconsdir}/skype.png +%ghost %{_iconsdir}/SkypeBlue_*.png +%ghost %{_datadir}/applications/skype.desktop +%ghost %{instdir} + +%changelog + +* Mon Jun 13 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-8.mga1 +- Added || exit 1 in pre +- Changed tmp file var names to be more descriptive. + + +* Sun Jun 12 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-8.mga1 +- Removed full stop from summary. + +* 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/20110613/2c715ab6/attachment-0003.ksh b/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment-0003.ksh new file mode 100644 index 000000000..6a315f788 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment-0003.ksh @@ -0,0 +1,63 @@ +#!/bin/bash +# +# Save this file as skype-txt-gen in your home folder +# $ chmod +x skype-txt-gen +# Extract the new skype tarball into your home folder which should create a folder e.g. ~/skype-2.2.0.35 +# Run this script and copy the three output txt files to the SOURCES folder in your rpm build tree. +# +######################################################### + +if [[ ${#1} = 0 ]]; then +echo "Usage: $ ./skype-txt-gen <version>" +echo "example: $ ./skype-txt-gen 2.2.0.35" +exit 1 +fi +version=$1 +if ! [[ -d skype-$version ]]; then +echo "Directory skype-$version is missing" +exit 1 +fi +dirname="skype-sources-$version" +rm -rf "$dirname" +mkdir "$dirname" +cd skype-"$version" + +getavatars() +{ +rm -f ../"$dirname"/avatars-"$version".txt +cd avatars +for item in * +do +echo $item >> ../../"$dirname"/avatars-"$version".txt +done +cd .. +} + +getsounds() +{ +rm -f ../"$dirname/"sounds-"$version".txt +cd sounds +for item in * +do +echo $item >> ../../"$dirname"/sounds-"$version".txt +done +cd .. +} + +getlang() +{ +rm -f ../"$dirname"/lang-"$version".txt +cd lang +for item in * +do +echo $item >> ../../"$dirname"/lang-"$version".txt +done +cd .. +sed -i 's/skype_//g' ../"$dirname"/lang-"$version".txt +} + +getavatars +getsounds +getlang + +echo "The text files have been created in ~/$dirname"
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment.ksh b/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment.ksh new file mode 100644 index 000000000..4cf4c9ee8 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/2c715ab6/attachment.ksh @@ -0,0 +1,201 @@ +%define name get-skype +%define version 2.2.0.35 +%define release %mkrel 9 +%define instdir %{_datadir}/skype +%define langdir %{instdir}/lang +%define avatardir %{instdir}/avatars +%define sounddir %{instdir}/sounds +%define icondir %{instdir}/icons +%define md5 6e28002c0086fae5206e2d242c3edcfa +%define tmp_download_dir %{_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 %{tmp_download_dir} +[[ -d %{tmp_download_dir} ]] || exit 1 +cd %{tmp_download_dir} || exit 1 +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 %{tmp_download_dir} +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 + +tmp_extract_dir=$(mktemp -d) +if ! [[ -d $tmp_extract_dir ]]; then +echo "Failed to create temporary directory" +rm -r %{tmp_download_dir} +exit 1 +fi + +%define tmp_skype_dir ${tmp_extract_dir}/skype-%{version} + +cd ${tmp_extract_dir} +tar jxf %{tmp_download_dir}/skype-%{version}.tar.bz2 + +if ! [[ -d %{tmp_skype_dir} ]]; then +echo "Extracted file folder missing" +cd .. +rm -rf ${tmp_extract_dir} +rm -r %{tmp_download_dir} +exit 1 +fi + +# If any extra files are installed here then +# corresponding ghost files need to be added in files + +mkdir -p %{instdir} + +cp -a %{tmp_skype_dir}/icons/* %{_iconsdir} +cp -a %{_iconsdir}/SkypeBlue_48x48.png %{_iconsdir}/skype.png +cp -a %{tmp_skype_dir}/skype.desktop %{_datadir}/applications/ +mv %{tmp_skype_dir}/skype %{instdir} +mv %{tmp_skype_dir}/skype.desktop %{instdir} +mv %{tmp_skype_dir}/skype.conf %{instdir} +mv %{tmp_skype_dir}/LICENSE %{instdir} +mv %{tmp_skype_dir}/README %{instdir} +mv %{tmp_skype_dir}/avatars %{instdir} +mv %{tmp_skype_dir}/lang %{langdir} +mv %{tmp_skype_dir}/sounds %{sounddir} +mv %{tmp_skype_dir}/icons %{icondir} +rm -r %{tmp_skype_dir} +cd .. +rm -r ${tmp_extract_dir} +rm -r %{tmp_download_dir} + +%clean + +rm -rf $RPM_BUILD_ROOT + +%files + +%defattr(-,root,root) +%{_bindir}/skype +%ghost %{_iconsdir}/skype.png +%ghost %{_iconsdir}/SkypeBlue_*.png +%ghost %{_datadir}/applications/skype.desktop +%ghost %{instdir} + +%changelog + +* Mon Jun 13 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-8.mga1 +- Added || exit 1 in pre +- Changed tmp file var names to be more descriptive. + + +* Sun Jun 12 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-8.mga1 +- Removed full stop from summary. + +* 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/20110613/30ac67d2/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/30ac67d2/attachment-0001.html new file mode 100644 index 000000000..1ba6b26a0 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/30ac67d2/attachment-0001.html @@ -0,0 +1,39 @@ +<br><br><div class="gmail_quote">2011/6/13 Thomas Backlund <span dir="ltr"><<a href="mailto:tmb@mageia.org">tmb@mageia.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +Wolfgang Bornath skrev 13.6.2011 15:20:<br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +About the cycles:<div class="im"><br> +<br> +The 9-months seem to be a compromise - but I start to ask why we need<br> +such a fixed statement (which it would be, once published). We need a<br> +schedule for each cycle, that's true. Without a schedule we would<br> +never finish anything. But how about taking 9 months only as a "nice<br> +to meet" target, leaving us the option to set a roadmap after setting<br> +the specs of the next release - we could then go for a 8 or 10 months<br> +roadmap, depending on the specs.<br> +<br> +</div></blockquote> +<br> +This is somewhat like what I had in my mind to write too, but you beat me to it :)<br> +<br> +It could allow us to adapt a little for upstream releases.<br> +But should we then decide that the limit is +/- 1 month ?<br> +<br> +Obviously there will still be people complaining that "you waited 10 months... if you had extended with ~2 more weeks... "this" or "that"<br> +package would have been available too... and so on....<br> +<br> +<br> +And something not to forget (this is more related to the specs):<br> +<br> +If an estimated upstream release of kde/gnome/... seem to fit our<br> +schedule it _must_ be in Cauldron before version freeze so we<br> +actually get some test/qa on it and not try to force it in by<br> +"hey it's released ~x days before final mageia release so it<br> + must be added" attitude that tends to pop up at every freeze.<br> +<br> +--<br><font color="#888888"> +Thomas<br> +<br> +<br> +<br> +</font></blockquote></div>Let the 9 months as maximum, as a general target.<div><br></div><div>Make the specs and then the roadmap with a fixed release date and a fixed enough time for freeze and testing.</div><div><br></div> +<div>If an upstream release brings conflits, that's live.</div><div>Main focus should be a stable release for simple users not a pot of the latest apps</div><div><br></div><div>Magnus</div><div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20110613/30ac67d2/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/30ac67d2/attachment.html new file mode 100644 index 000000000..1ba6b26a0 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/30ac67d2/attachment.html @@ -0,0 +1,39 @@ +<br><br><div class="gmail_quote">2011/6/13 Thomas Backlund <span dir="ltr"><<a href="mailto:tmb@mageia.org">tmb@mageia.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +Wolfgang Bornath skrev 13.6.2011 15:20:<br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +About the cycles:<div class="im"><br> +<br> +The 9-months seem to be a compromise - but I start to ask why we need<br> +such a fixed statement (which it would be, once published). We need a<br> +schedule for each cycle, that's true. Without a schedule we would<br> +never finish anything. But how about taking 9 months only as a "nice<br> +to meet" target, leaving us the option to set a roadmap after setting<br> +the specs of the next release - we could then go for a 8 or 10 months<br> +roadmap, depending on the specs.<br> +<br> +</div></blockquote> +<br> +This is somewhat like what I had in my mind to write too, but you beat me to it :)<br> +<br> +It could allow us to adapt a little for upstream releases.<br> +But should we then decide that the limit is +/- 1 month ?<br> +<br> +Obviously there will still be people complaining that "you waited 10 months... if you had extended with ~2 more weeks... "this" or "that"<br> +package would have been available too... and so on....<br> +<br> +<br> +And something not to forget (this is more related to the specs):<br> +<br> +If an estimated upstream release of kde/gnome/... seem to fit our<br> +schedule it _must_ be in Cauldron before version freeze so we<br> +actually get some test/qa on it and not try to force it in by<br> +"hey it's released ~x days before final mageia release so it<br> + must be added" attitude that tends to pop up at every freeze.<br> +<br> +--<br><font color="#888888"> +Thomas<br> +<br> +<br> +<br> +</font></blockquote></div>Let the 9 months as maximum, as a general target.<div><br></div><div>Make the specs and then the roadmap with a fixed release date and a fixed enough time for freeze and testing.</div><div><br></div> +<div>If an upstream release brings conflits, that's live.</div><div>Main focus should be a stable release for simple users not a pot of the latest apps</div><div><br></div><div>Magnus</div><div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20110613/3e6ddee7/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110613/3e6ddee7/attachment-0001.asc new file mode 100644 index 000000000..8d4f1f53b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/3e6ddee7/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32AHYACgkQqEs9DA4DquBNwQCfbrQYH/IWPxSj2rBtnu7IsgJA +KPEAoLu4DvTI2VRab/RSqBX0tYOq5IwO +=v8xE +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/3e6ddee7/attachment.asc b/zarb-ml/mageia-dev/attachments/20110613/3e6ddee7/attachment.asc new file mode 100644 index 000000000..8d4f1f53b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/3e6ddee7/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32AHYACgkQqEs9DA4DquBNwQCfbrQYH/IWPxSj2rBtnu7IsgJA +KPEAoLu4DvTI2VRab/RSqBX0tYOq5IwO +=v8xE +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/4f2f9de9/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/4f2f9de9/attachment-0001.html new file mode 100644 index 000000000..0add9d432 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/4f2f9de9/attachment-0001.html @@ -0,0 +1,44 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> + <head> + <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> + </head> + <body text="#000000" bgcolor="#ffffff"> + From <strong><a +href="https://forums.mageia.org/en/memberlist.php?mode=viewprofile&u=359">pmithrandir</a></strong> + on the forum<br> + <br> + On my side, I think mageia should do a "mix" of others idea.<br> + <br> + I would say : <br> + - A release every year.<br> + - During this year, a way to update some popular stuff (firefox, + chrome, libreoffice...)<br> + - During this year also a way to add some new package if needed or + if there is some instant success for a new software.<br> + <br> + Every 3 years, the release is LTS and that mean it would be maintain + for 4 years.<br> + <br> + So at the same time, mageia would be in 3 mode : <br> + - The LTS<br> + - The common release<br> + - The cauldron.<br> + <br> + With that kind of stuff, you should have no more than one release + for public at a time, and just one LTS.<br> + If you update main software(we could define a list of no more than + 20 software) people who are crasy about new function, or developper + who need tham to develop new stuff would be happy.<br> + <br> + BTW : I think mailing list are totally outdated and that mageia + should have a special section in this forum for these discussion, or + maybe another forum.<br> + It's totally impossible for people who want to participate sometimes + to follow you emails everydays. It's much faster to read some topic + on a forum than dozens emails. And your final user should be able to + know what happen easily. It would be a big + in front of others + distributions.<br> + <br> + </body> +</html> diff --git a/zarb-ml/mageia-dev/attachments/20110613/4f2f9de9/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/4f2f9de9/attachment.html new file mode 100644 index 000000000..0add9d432 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/4f2f9de9/attachment.html @@ -0,0 +1,44 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> + <head> + <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> + </head> + <body text="#000000" bgcolor="#ffffff"> + From <strong><a +href="https://forums.mageia.org/en/memberlist.php?mode=viewprofile&u=359">pmithrandir</a></strong> + on the forum<br> + <br> + On my side, I think mageia should do a "mix" of others idea.<br> + <br> + I would say : <br> + - A release every year.<br> + - During this year, a way to update some popular stuff (firefox, + chrome, libreoffice...)<br> + - During this year also a way to add some new package if needed or + if there is some instant success for a new software.<br> + <br> + Every 3 years, the release is LTS and that mean it would be maintain + for 4 years.<br> + <br> + So at the same time, mageia would be in 3 mode : <br> + - The LTS<br> + - The common release<br> + - The cauldron.<br> + <br> + With that kind of stuff, you should have no more than one release + for public at a time, and just one LTS.<br> + If you update main software(we could define a list of no more than + 20 software) people who are crasy about new function, or developper + who need tham to develop new stuff would be happy.<br> + <br> + BTW : I think mailing list are totally outdated and that mageia + should have a special section in this forum for these discussion, or + maybe another forum.<br> + It's totally impossible for people who want to participate sometimes + to follow you emails everydays. It's much faster to read some topic + on a forum than dozens emails. And your final user should be able to + know what happen easily. It would be a big + in front of others + distributions.<br> + <br> + </body> +</html> diff --git a/zarb-ml/mageia-dev/attachments/20110613/533d939b/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/533d939b/attachment-0001.html new file mode 100644 index 000000000..130b319dd --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/533d939b/attachment-0001.html @@ -0,0 +1,27 @@ +<br><br><div class="gmail_quote">2011/6/13 Lee Forest <span dir="ltr"><<a href="mailto:lee8oi@gmail.com">lee8oi@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +<p>I like the idea of releasing when ready. Its done when the team thinks its ready and not because its being demanded by end users. In Linux Mint this does alot of good because of having to clean up after ubuntu so much. The releases are much more stable and polished. The way clement lefabre likes it. And everyone who uses it is usually satisfied with the end product. <br> +</p></blockquote><div>Well this is theway it seems we are going to, some people proposing 9 months release depending on release dates of main softwares. Anyway whatever the choice, it's obvious that we will not release final one if this is not stable enough.</div> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p> + +As for being in the news more, we dont have to put out a release just to be able blog about whats going on in the mageia community and remind everyone why mageia is special. But this must be the case because theres rarely any new news posted in mageia blog unless a release is coming out. Thats getting about as lame as these messages in this mailing list telling people they sent their message to the mailing list wrong.<br> + + +What is this distro really about? One upping mandriva and following the same mechanical routines they did to piss you guys off, or building a real community distribution of gnu/linux that cares more about keeping in touch with the community than they do about the way someone new sent a mailing list message. Theres more to a linux community then mailing lists.<br> + + +At first I was excited about using mageia, and being a part of the community. Now im dissappointed because I see how you treat people that are not on the team. Basically like their opinions<br></p></blockquote><div>Not at all. everyone can subscribe mailing- lists. The point is Mageia is a young project and we cannot afford for now at least to spread efforts on forums and mailing-lists and blogs... People still sleep during the night. It may not be perfect but it's a start. Our points is just to try to get all opinions in a same place, that's all.</div> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p> +(that you ask for) dont matter, and you are only concerned with the proper submission of mailing lists messages. Get someone on the blogs and start talking to the rest of the community the way they deserve. I agree with the gentleman leaving the mailing list. This isn't worth sticking around for. Time to remember why you started mageia in the first place.</p> +</blockquote><div>Of course we are opened to any of your proposals and ideas and contributions to improve all this :)</div><div><br></div><div>Cheers</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +<div><div></div><div class="h5"> + +<div class="gmail_quote">On Jun 13, 2011 12:51 PM, "Ron" <<a href="mailto:corbintechboy@yahoo.com" target="_blank">corbintechboy@yahoo.com</a>> wrote:<br type="attribution">> I will say my part and I'm gone...<br> + +> I don't understand why everyone is acting like a rolling release is going to put so much strain on the project. What is so hard about developing in one place and allowing the updates to trickle down is so hard?<br> + +> It almost seems to me that you want to ask the opinion of people, but don't want to hear.<br>> And what is this posting here? I don't even know how to use this thing and yet I had to signup to get my voice heard because this is the way you want to do things? I don't understand where the whole community fits into this here right now, I think I actually say a lot when I say that many people want a rolling release.... It just seems the developers will have the way here... Why ask in the first place? Really?<br> + +> I am leaving the list and sorry about the HTML in my emails, must be a yahoo thing because I did not use HTML... Again I don't know how to use this thing and should not have been forced to.<br>> I would also say that I, for 1 will not be staying if you are going to do a release cycle only... I have loads of options if I just want snapshots of what's going on in the Linux world.... Arch gives me so much more and I had hopes of switching to this with a release model that made sense... But it seems we won't and we will just become yet another XXX release cycle distribution with no clear anything that sets us apart from X.<br> + +> On you, I'm gone and thanks for hearing me and sorry if my postings were done wrong....<br></div> +</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anne<br><a href="http://www.mageia.org" target="_blank">http://www.mageia.org</a><br> diff --git a/zarb-ml/mageia-dev/attachments/20110613/533d939b/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/533d939b/attachment.html new file mode 100644 index 000000000..130b319dd --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/533d939b/attachment.html @@ -0,0 +1,27 @@ +<br><br><div class="gmail_quote">2011/6/13 Lee Forest <span dir="ltr"><<a href="mailto:lee8oi@gmail.com">lee8oi@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +<p>I like the idea of releasing when ready. Its done when the team thinks its ready and not because its being demanded by end users. In Linux Mint this does alot of good because of having to clean up after ubuntu so much. The releases are much more stable and polished. The way clement lefabre likes it. And everyone who uses it is usually satisfied with the end product. <br> +</p></blockquote><div>Well this is theway it seems we are going to, some people proposing 9 months release depending on release dates of main softwares. Anyway whatever the choice, it's obvious that we will not release final one if this is not stable enough.</div> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p> + +As for being in the news more, we dont have to put out a release just to be able blog about whats going on in the mageia community and remind everyone why mageia is special. But this must be the case because theres rarely any new news posted in mageia blog unless a release is coming out. Thats getting about as lame as these messages in this mailing list telling people they sent their message to the mailing list wrong.<br> + + +What is this distro really about? One upping mandriva and following the same mechanical routines they did to piss you guys off, or building a real community distribution of gnu/linux that cares more about keeping in touch with the community than they do about the way someone new sent a mailing list message. Theres more to a linux community then mailing lists.<br> + + +At first I was excited about using mageia, and being a part of the community. Now im dissappointed because I see how you treat people that are not on the team. Basically like their opinions<br></p></blockquote><div>Not at all. everyone can subscribe mailing- lists. The point is Mageia is a young project and we cannot afford for now at least to spread efforts on forums and mailing-lists and blogs... People still sleep during the night. It may not be perfect but it's a start. Our points is just to try to get all opinions in a same place, that's all.</div> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p> +(that you ask for) dont matter, and you are only concerned with the proper submission of mailing lists messages. Get someone on the blogs and start talking to the rest of the community the way they deserve. I agree with the gentleman leaving the mailing list. This isn't worth sticking around for. Time to remember why you started mageia in the first place.</p> +</blockquote><div>Of course we are opened to any of your proposals and ideas and contributions to improve all this :)</div><div><br></div><div>Cheers</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +<div><div></div><div class="h5"> + +<div class="gmail_quote">On Jun 13, 2011 12:51 PM, "Ron" <<a href="mailto:corbintechboy@yahoo.com" target="_blank">corbintechboy@yahoo.com</a>> wrote:<br type="attribution">> I will say my part and I'm gone...<br> + +> I don't understand why everyone is acting like a rolling release is going to put so much strain on the project. What is so hard about developing in one place and allowing the updates to trickle down is so hard?<br> + +> It almost seems to me that you want to ask the opinion of people, but don't want to hear.<br>> And what is this posting here? I don't even know how to use this thing and yet I had to signup to get my voice heard because this is the way you want to do things? I don't understand where the whole community fits into this here right now, I think I actually say a lot when I say that many people want a rolling release.... It just seems the developers will have the way here... Why ask in the first place? Really?<br> + +> I am leaving the list and sorry about the HTML in my emails, must be a yahoo thing because I did not use HTML... Again I don't know how to use this thing and should not have been forced to.<br>> I would also say that I, for 1 will not be staying if you are going to do a release cycle only... I have loads of options if I just want snapshots of what's going on in the Linux world.... Arch gives me so much more and I had hopes of switching to this with a release model that made sense... But it seems we won't and we will just become yet another XXX release cycle distribution with no clear anything that sets us apart from X.<br> + +> On you, I'm gone and thanks for hearing me and sorry if my postings were done wrong....<br></div> +</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anne<br><a href="http://www.mageia.org" target="_blank">http://www.mageia.org</a><br> diff --git a/zarb-ml/mageia-dev/attachments/20110613/5adac570/attachment-0001.bin b/zarb-ml/mageia-dev/attachments/20110613/5adac570/attachment-0001.bin Binary files differnew file mode 100644 index 000000000..5e6677792 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/5adac570/attachment-0001.bin diff --git a/zarb-ml/mageia-dev/attachments/20110613/5adac570/attachment.bin b/zarb-ml/mageia-dev/attachments/20110613/5adac570/attachment.bin Binary files differnew file mode 100644 index 000000000..5e6677792 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/5adac570/attachment.bin diff --git a/zarb-ml/mageia-dev/attachments/20110613/687bf147/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110613/687bf147/attachment-0001.asc new file mode 100644 index 000000000..20bc57c46 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/687bf147/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32C2QACgkQqEs9DA4DquCcCQCfYohvAiy6cJOrYsNp28umuQgi +vkIAnRkju3+d+HEQxnewUP9mo1QaGwCL +=tReE +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/687bf147/attachment.asc b/zarb-ml/mageia-dev/attachments/20110613/687bf147/attachment.asc new file mode 100644 index 000000000..20bc57c46 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/687bf147/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32C2QACgkQqEs9DA4DquCcCQCfYohvAiy6cJOrYsNp28umuQgi +vkIAnRkju3+d+HEQxnewUP9mo1QaGwCL +=tReE +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/7068a595/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110613/7068a595/attachment-0001.asc new file mode 100644 index 000000000..bd11fe6a8 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/7068a595/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32ONwACgkQqEs9DA4DquBNDwCfc/yKdiuz+2tYMPwppUOE6rLU +awcAn3g7rnTMbWSKryP8Ao6Cj//EmMh6 +=fWeT +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/7068a595/attachment.asc b/zarb-ml/mageia-dev/attachments/20110613/7068a595/attachment.asc new file mode 100644 index 000000000..bd11fe6a8 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/7068a595/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32ONwACgkQqEs9DA4DquBNDwCfc/yKdiuz+2tYMPwppUOE6rLU +awcAn3g7rnTMbWSKryP8Ao6Cj//EmMh6 +=fWeT +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/8c643b61/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/8c643b61/attachment-0001.html new file mode 100644 index 000000000..7c8ecf006 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/8c643b61/attachment-0001.html @@ -0,0 +1,8 @@ +<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">From a long time mandriva (and now mageia) user POV, for myself I was quite<br> +fine with 6 month release cycle, but at work I'd rather not update too<br> +frequently and same goes for the rest of the family who generally don't care<br> +much for newer versions. And I know that for some people, a big upgrade<br> +every 6 month is a lot of work (and skipping a release is more risky).<br></blockquote><div>I agree and think this the the sight of most of the "normal" users.</div><div><br></div><div>Proposal #2 is the right time to discuss, to do greater changes and to test. </div> +<div>Especially testing-time should be a focus to get a standing as very stable distri.</div><div><br></div><div>Other hand, we should not hang too close to the nine month.</div><div>The release date could be a good "human readable" date:</div> +<div><br></div><div>Mageia 2 = Spring time (2012-03-20)</div><div>Mageia 3 = Nicolas (2012-12-06)</div><div>Mageia 4 = Revolution (2013-07-14) or Birthday (2013-09-18)</div><div><br></div><div>or someting like this</div><div> +<br></div><div>Proposal #3 is too long, for the patience of the users and developers</div><div><br></div><div>Magnus</div></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20110613/8c643b61/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/8c643b61/attachment.html new file mode 100644 index 000000000..7c8ecf006 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/8c643b61/attachment.html @@ -0,0 +1,8 @@ +<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">From a long time mandriva (and now mageia) user POV, for myself I was quite<br> +fine with 6 month release cycle, but at work I'd rather not update too<br> +frequently and same goes for the rest of the family who generally don't care<br> +much for newer versions. And I know that for some people, a big upgrade<br> +every 6 month is a lot of work (and skipping a release is more risky).<br></blockquote><div>I agree and think this the the sight of most of the "normal" users.</div><div><br></div><div>Proposal #2 is the right time to discuss, to do greater changes and to test. </div> +<div>Especially testing-time should be a focus to get a standing as very stable distri.</div><div><br></div><div>Other hand, we should not hang too close to the nine month.</div><div>The release date could be a good "human readable" date:</div> +<div><br></div><div>Mageia 2 = Spring time (2012-03-20)</div><div>Mageia 3 = Nicolas (2012-12-06)</div><div>Mageia 4 = Revolution (2013-07-14) or Birthday (2013-09-18)</div><div><br></div><div>or someting like this</div><div> +<br></div><div>Proposal #3 is too long, for the patience of the users and developers</div><div><br></div><div>Magnus</div></div><br> diff --git a/zarb-ml/mageia-dev/attachments/20110613/9badc44d/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/9badc44d/attachment-0001.html new file mode 100644 index 000000000..424e22588 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/9badc44d/attachment-0001.html @@ -0,0 +1,14 @@ +<p>I like the idea of releasing when ready. Its done when the team thinks its ready and not because its being demanded by end users. In Linux Mint this does alot of good because of having to clean up after ubuntu so much. The releases are much more stable and polished. The way clement lefabre likes it. And everyone who uses it is usually satisfied with the end product. <br> + +As for being in the news more, we dont have to put out a release just to be able blog about whats going on in the mageia community and remind everyone why mageia is special. But this must be the case because theres rarely any new news posted in mageia blog unless a release is coming out. Thats getting about as lame as these messages in this mailing list telling people they sent their message to the mailing list wrong.<br> + +What is this distro really about? One upping mandriva and following the same mechanical routines they did to piss you guys off, or building a real community distribution of gnu/linux that cares more about keeping in touch with the community than they do about the way someone new sent a mailing list message. Theres more to a linux community then mailing lists.<br> + +At first I was excited about using mageia, and being a part of the community. Now im dissappointed because I see how you treat people that are not on the team. Basically like their opinions<br> +(that you ask for) dont matter, and you are only concerned with the proper submission of mailing lists messages. Get someone on the blogs and start talking to the rest of the community the way they deserve. I agree with the gentleman leaving the mailing list. This isn't worth sticking around for. Time to remember why you started mageia in the first place.</p> + +<div class="gmail_quote">On Jun 13, 2011 12:51 PM, "Ron" <<a href="mailto:corbintechboy@yahoo.com">corbintechboy@yahoo.com</a>> wrote:<br type="attribution">> I will say my part and I'm gone...<br> +> I don't understand why everyone is acting like a rolling release is going to put so much strain on the project. What is so hard about developing in one place and allowing the updates to trickle down is so hard?<br> +> It almost seems to me that you want to ask the opinion of people, but don't want to hear.<br>> And what is this posting here? I don't even know how to use this thing and yet I had to signup to get my voice heard because this is the way you want to do things? I don't understand where the whole community fits into this here right now, I think I actually say a lot when I say that many people want a rolling release.... It just seems the developers will have the way here... Why ask in the first place? Really?<br> +> I am leaving the list and sorry about the HTML in my emails, must be a yahoo thing because I did not use HTML... Again I don't know how to use this thing and should not have been forced to.<br>> I would also say that I, for 1 will not be staying if you are going to do a release cycle only... I have loads of options if I just want snapshots of what's going on in the Linux world.... Arch gives me so much more and I had hopes of switching to this with a release model that made sense... But it seems we won't and we will just become yet another XXX release cycle distribution with no clear anything that sets us apart from X.<br> +> On you, I'm gone and thanks for hearing me and sorry if my postings were done wrong....<br></div> diff --git a/zarb-ml/mageia-dev/attachments/20110613/9badc44d/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/9badc44d/attachment.html new file mode 100644 index 000000000..424e22588 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/9badc44d/attachment.html @@ -0,0 +1,14 @@ +<p>I like the idea of releasing when ready. Its done when the team thinks its ready and not because its being demanded by end users. In Linux Mint this does alot of good because of having to clean up after ubuntu so much. The releases are much more stable and polished. The way clement lefabre likes it. And everyone who uses it is usually satisfied with the end product. <br> + +As for being in the news more, we dont have to put out a release just to be able blog about whats going on in the mageia community and remind everyone why mageia is special. But this must be the case because theres rarely any new news posted in mageia blog unless a release is coming out. Thats getting about as lame as these messages in this mailing list telling people they sent their message to the mailing list wrong.<br> + +What is this distro really about? One upping mandriva and following the same mechanical routines they did to piss you guys off, or building a real community distribution of gnu/linux that cares more about keeping in touch with the community than they do about the way someone new sent a mailing list message. Theres more to a linux community then mailing lists.<br> + +At first I was excited about using mageia, and being a part of the community. Now im dissappointed because I see how you treat people that are not on the team. Basically like their opinions<br> +(that you ask for) dont matter, and you are only concerned with the proper submission of mailing lists messages. Get someone on the blogs and start talking to the rest of the community the way they deserve. I agree with the gentleman leaving the mailing list. This isn't worth sticking around for. Time to remember why you started mageia in the first place.</p> + +<div class="gmail_quote">On Jun 13, 2011 12:51 PM, "Ron" <<a href="mailto:corbintechboy@yahoo.com">corbintechboy@yahoo.com</a>> wrote:<br type="attribution">> I will say my part and I'm gone...<br> +> I don't understand why everyone is acting like a rolling release is going to put so much strain on the project. What is so hard about developing in one place and allowing the updates to trickle down is so hard?<br> +> It almost seems to me that you want to ask the opinion of people, but don't want to hear.<br>> And what is this posting here? I don't even know how to use this thing and yet I had to signup to get my voice heard because this is the way you want to do things? I don't understand where the whole community fits into this here right now, I think I actually say a lot when I say that many people want a rolling release.... It just seems the developers will have the way here... Why ask in the first place? Really?<br> +> I am leaving the list and sorry about the HTML in my emails, must be a yahoo thing because I did not use HTML... Again I don't know how to use this thing and should not have been forced to.<br>> I would also say that I, for 1 will not be staying if you are going to do a release cycle only... I have loads of options if I just want snapshots of what's going on in the Linux world.... Arch gives me so much more and I had hopes of switching to this with a release model that made sense... But it seems we won't and we will just become yet another XXX release cycle distribution with no clear anything that sets us apart from X.<br> +> On you, I'm gone and thanks for hearing me and sorry if my postings were done wrong....<br></div> diff --git a/zarb-ml/mageia-dev/attachments/20110613/a251d51e/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/a251d51e/attachment-0001.html new file mode 100644 index 000000000..e79662b68 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/a251d51e/attachment-0001.html @@ -0,0 +1,2 @@ +<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">I will say my part and I'm gone...<div><br></div><div>I don't understand why everyone is acting like a rolling release is going to put so much strain on the project. What is so hard about developing in one place and allowing the updates to trickle down is so hard?</div><div><br></div><div>It almost seems to me that you want to ask the opinion of people, but don't want to hear.</div><div><br></div><div>And what is this posting here? I don't even know how to use this thing and yet I had to signup to get my voice heard because this is the way you want to do things? I don't understand where the whole community fits into this here right now, I think I actually say a lot when I say that many people want a rolling release.... It just seems the developers will have the way here... Why ask in the first place? Really?</div><div><br></div><div>I am leaving the list and + sorry about the HTML in my emails, must be a yahoo thing because I did not use HTML... Again I don't know how to use this thing and should not have been forced to.</div><div><br></div><div>I would also say that I, for 1 will not be staying if you are going to do a release cycle only... I have loads of options if I just want snapshots of what's going on in the Linux world.... Arch gives me so much more and I had hopes of switching to this with a release model that made sense... But it seems we won't and we will just become yet another XXX release cycle distribution with no clear anything that sets us apart from X.</div><div><br></div><div>On you, I'm gone and thanks for hearing me and sorry if my postings were done wrong....</div></td></tr></table>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/a251d51e/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/a251d51e/attachment.html new file mode 100644 index 000000000..e79662b68 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/a251d51e/attachment.html @@ -0,0 +1,2 @@ +<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">I will say my part and I'm gone...<div><br></div><div>I don't understand why everyone is acting like a rolling release is going to put so much strain on the project. What is so hard about developing in one place and allowing the updates to trickle down is so hard?</div><div><br></div><div>It almost seems to me that you want to ask the opinion of people, but don't want to hear.</div><div><br></div><div>And what is this posting here? I don't even know how to use this thing and yet I had to signup to get my voice heard because this is the way you want to do things? I don't understand where the whole community fits into this here right now, I think I actually say a lot when I say that many people want a rolling release.... It just seems the developers will have the way here... Why ask in the first place? Really?</div><div><br></div><div>I am leaving the list and + sorry about the HTML in my emails, must be a yahoo thing because I did not use HTML... Again I don't know how to use this thing and should not have been forced to.</div><div><br></div><div>I would also say that I, for 1 will not be staying if you are going to do a release cycle only... I have loads of options if I just want snapshots of what's going on in the Linux world.... Arch gives me so much more and I had hopes of switching to this with a release model that made sense... But it seems we won't and we will just become yet another XXX release cycle distribution with no clear anything that sets us apart from X.</div><div><br></div><div>On you, I'm gone and thanks for hearing me and sorry if my postings were done wrong....</div></td></tr></table>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/b1599667/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/b1599667/attachment-0001.html new file mode 100644 index 000000000..9253f8540 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/b1599667/attachment-0001.html @@ -0,0 +1,14 @@ +<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><meta http-equiv="content-type" content="text/html; charset=utf-8"><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; ">>There is a limited set of options, and as you can see, none of your >idea was not already explored by someone else.</span><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; "><br></span></div><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; ">It has all been done before, in that sense let's just close up shop and call it a day???</span></div><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; + "><br></span></div><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; "><meta http-equiv="content-type" content="text/html; charset=utf-8">>If everything move all days, you cannot :<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>- translate software ( as the string will change every day )<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>- create documentation ( for the same reason )<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>- communicate ( as everything ca be broken at any time )<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>- ensure stability ( as each change can bring unstability )<br style="line-height: 1.2em; + outline-style: none; outline-width: initial; outline-color: initial; "><br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>And for user, some do not want to redo training every week for >their<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>users, because libreoffice got updated, because ff 4 just arrived >and<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>75% of extensions do not work, etc. <br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">><br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>In fact, the whole release model is basically what is used all >over the<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; + ">>place, from lower level like kernel to higher level like kde. So >you can<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>get lots of feedback on it.</span></div><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; "><br></span></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">You are correct on the release model being used everywhere, that fit's development and really there is no other way to do it as it takes time. But really, up stream does have to take time but package maintainers can pull things in pretty fast and make things work.</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: + 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">I don't understand what's being said here? Are we a community of users or are we just teachers teaching a class? Help with changes is what forums and people are for. </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">You worried about not being able to keep up with documentation? I suggest you take a look at the Arch wiki, best Linux wiki there is and things change fast... Again, community...</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: + 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>So basically, you suggest that since everybody is already doing >it, this is useless. So the logical conclusion is we should drop >the distribution ?</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">No that is not what I'm saying! </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span + class="Apple-style-span" style="font-size: 14px; line-height: 16px;">What I am saying is that you have 100+/- distributions all going by a release model and only a handful making rolling releases. There is only one defacto maker of a rolling release and that is Arch, why does this have to be? (Yes I know there are others but Arch is the leader of the pack)</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>We have the same thing, this is the strength of free software. We<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>basically all work together.</span></font></div><div><font + class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">It truly is redundant to do what everyone else is doing just because....</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>like cauldron ? or debian unstable, fedora rawhide, opensuse >factory,</span></font><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; ">mandriva cooker ?</span></div><div><font class="Apple-style-span" + face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Sure, there has to be an unstable branch whether rolling or not...</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>like debian testing ( and CUT ) ? suse tumbleweed ? arch linux</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" + face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Nope, gotta call you on this... Debian testing rolls with the purpose of becoming a release... Therefore things can grow outdated rather quickly. </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Suse tumblweed IS NOT going to be a true rolling release! It is going to "tumble up" to the next release hence the name.</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: + 16px;">This cannot be compared to Arch either as Arch has a set of rules as well and rolls into stable...</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>Very stable for a distribution mean "that do not change". That's<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>incompatible with the idea of rolling per definition. And inorder >to have stable software, you have to freeze them and fix bugs. So >to have that on the whole distribution, you need to freeze the >whole distribution for a time, and then ask for test, fix bugs >and then release. Which is + exactly what we currently do since >years.</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Sorry, your wrong! I have been using Arch for years and have yet to meet a show stopper bug, it is very stable. </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Stability simply means tested! It does not have to be like Debian testing that grows stale with time, you can remain very very close to bleeding edge and still remain + stable...</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>So basically, you just reinvented the concept of release, and the >way Mandriva, Debian, Fedora work since years. </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">And I must have peed in your cheerios... I am all for giving people what they want, I also don't think you have to follow the status quo to do so... We + don't have to be "just another distribution doing the same things the others are doing"... Sorry, but this is what I see....</span></font></div></td></tr></table>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/b1599667/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/b1599667/attachment.html new file mode 100644 index 000000000..9253f8540 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/b1599667/attachment.html @@ -0,0 +1,14 @@ +<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><meta http-equiv="content-type" content="text/html; charset=utf-8"><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; ">>There is a limited set of options, and as you can see, none of your >idea was not already explored by someone else.</span><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; "><br></span></div><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; ">It has all been done before, in that sense let's just close up shop and call it a day???</span></div><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; + "><br></span></div><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; "><meta http-equiv="content-type" content="text/html; charset=utf-8">>If everything move all days, you cannot :<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>- translate software ( as the string will change every day )<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>- create documentation ( for the same reason )<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>- communicate ( as everything ca be broken at any time )<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>- ensure stability ( as each change can bring unstability )<br style="line-height: 1.2em; + outline-style: none; outline-width: initial; outline-color: initial; "><br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>And for user, some do not want to redo training every week for >their<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>users, because libreoffice got updated, because ff 4 just arrived >and<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>75% of extensions do not work, etc. <br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">><br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>In fact, the whole release model is basically what is used all >over the<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; + ">>place, from lower level like kernel to higher level like kde. So >you can<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>get lots of feedback on it.</span></div><div style="font-family: arial; font-size: 10pt; "><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; "><br></span></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">You are correct on the release model being used everywhere, that fit's development and really there is no other way to do it as it takes time. But really, up stream does have to take time but package maintainers can pull things in pretty fast and make things work.</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: + 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">I don't understand what's being said here? Are we a community of users or are we just teachers teaching a class? Help with changes is what forums and people are for. </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">You worried about not being able to keep up with documentation? I suggest you take a look at the Arch wiki, best Linux wiki there is and things change fast... Again, community...</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: + 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>So basically, you suggest that since everybody is already doing >it, this is useless. So the logical conclusion is we should drop >the distribution ?</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">No that is not what I'm saying! </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span + class="Apple-style-span" style="font-size: 14px; line-height: 16px;">What I am saying is that you have 100+/- distributions all going by a release model and only a handful making rolling releases. There is only one defacto maker of a rolling release and that is Arch, why does this have to be? (Yes I know there are others but Arch is the leader of the pack)</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>We have the same thing, this is the strength of free software. We<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>basically all work together.</span></font></div><div><font + class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">It truly is redundant to do what everyone else is doing just because....</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>like cauldron ? or debian unstable, fedora rawhide, opensuse >factory,</span></font><span class="Apple-style-span" style="font-family: monospace; font-size: 14px; line-height: 16px; ">mandriva cooker ?</span></div><div><font class="Apple-style-span" + face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Sure, there has to be an unstable branch whether rolling or not...</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>like debian testing ( and CUT ) ? suse tumbleweed ? arch linux</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" + face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Nope, gotta call you on this... Debian testing rolls with the purpose of becoming a release... Therefore things can grow outdated rather quickly. </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Suse tumblweed IS NOT going to be a true rolling release! It is going to "tumble up" to the next release hence the name.</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: + 16px;">This cannot be compared to Arch either as Arch has a set of rules as well and rolls into stable...</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>Very stable for a distribution mean "that do not change". That's<br style="line-height: 1.2em; outline-style: none; outline-width: initial; outline-color: initial; ">>incompatible with the idea of rolling per definition. And inorder >to have stable software, you have to freeze them and fix bugs. So >to have that on the whole distribution, you need to freeze the >whole distribution for a time, and then ask for test, fix bugs >and then release. Which is + exactly what we currently do since >years.</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Sorry, your wrong! I have been using Arch for years and have yet to meet a show stopper bug, it is very stable. </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">Stability simply means tested! It does not have to be like Debian testing that grows stale with time, you can remain very very close to bleeding edge and still remain + stable...</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><meta http-equiv="content-type" content="text/html; charset=utf-8">>So basically, you just reinvented the concept of release, and the >way Mandriva, Debian, Fedora work since years. </span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;"><br></span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-size: 14px; line-height: 16px;">And I must have peed in your cheerios... I am all for giving people what they want, I also don't think you have to follow the status quo to do so... We + don't have to be "just another distribution doing the same things the others are doing"... Sorry, but this is what I see....</span></font></div></td></tr></table>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/def4bfb8/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/def4bfb8/attachment-0001.html new file mode 100644 index 000000000..5f5cbc428 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/def4bfb8/attachment-0001.html @@ -0,0 +1,26 @@ +<!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:'DejaVu Sans [unknown]'; font-size:9pt; 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;">Michael Scherer <misc@zarb.org> schrieb am 12.06.2011</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;">> Proposal 1:</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;">> 6 months release cycle -> 12 months life cycle</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;">> ( Fedora, Ubuntu, Mandriva < 2010.1 && Mandriva != 2006.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;">> </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;">> Proposal 2:</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;">> 9 months release cycle -> 18 months life cycle</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;">> ( ~ opensuse and the one we used for Mageia 1 )</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;">> Proposal 3:</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;">> 12 months release cycle -> 24 months life cycle</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;">> ( Mandriva > 2010.1 )</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;">That's kind of a hard decison. I don't know if a 6 month cycle would not put too much stress on the dev/packager community. But 12 months are a bit much for the hordes of impatient users usually residing in the forums.</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;">So I would - for now - prefer option 2, 9 months seeming a reasonable time span.</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;">Especially since we would always be able to change that cycle to something more fitting.</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;">As to the "rolling" and the "lts" discussion. I think it's something for the future. We first have to see, how much manpower we really have, to maintain the distro.</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 woul then kind of like the idea of a special rolling repo like debian testing or suse tumbleweed.</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;">Oliver</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/def4bfb8/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/def4bfb8/attachment.html new file mode 100644 index 000000000..5f5cbc428 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/def4bfb8/attachment.html @@ -0,0 +1,26 @@ +<!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:'DejaVu Sans [unknown]'; font-size:9pt; 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;">Michael Scherer <misc@zarb.org> schrieb am 12.06.2011</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;">> Proposal 1:</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;">> 6 months release cycle -> 12 months life cycle</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;">> ( Fedora, Ubuntu, Mandriva < 2010.1 && Mandriva != 2006.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;">> </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;">> Proposal 2:</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;">> 9 months release cycle -> 18 months life cycle</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;">> ( ~ opensuse and the one we used for Mageia 1 )</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;">> Proposal 3:</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;">> 12 months release cycle -> 24 months life cycle</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;">> ( Mandriva > 2010.1 )</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;">That's kind of a hard decison. I don't know if a 6 month cycle would not put too much stress on the dev/packager community. But 12 months are a bit much for the hordes of impatient users usually residing in the forums.</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;">So I would - for now - prefer option 2, 9 months seeming a reasonable time span.</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;">Especially since we would always be able to change that cycle to something more fitting.</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;">As to the "rolling" and the "lts" discussion. I think it's something for the future. We first have to see, how much manpower we really have, to maintain the distro.</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 woul then kind of like the idea of a special rolling repo like debian testing or suse tumbleweed.</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;">Oliver</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/e6448a8c/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/e6448a8c/attachment-0001.html new file mode 100644 index 000000000..efc907a93 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/e6448a8c/attachment-0001.html @@ -0,0 +1,3 @@ +<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><font class="Apple-style-span" face="arial" size="2">I made another post in a different thread about the way I feel the release cycle should go. After more thinking I do think that I really have the right idea and here is why...</font><div style="font-family: arial; font-size: 10pt; "><br></div><div><font class="Apple-style-span" face="arial" size="2">Going the route of release cycles really does not make this distribution fit into anything. You going to try and appeal to new people? Ubuntu has that </font><font class="Apple-style-span" face="arial" size="2">covered and you will never steal that role. Hoping to become a geek type distro? There are many that have that covered. </font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">The best thing you can do as a + team is try to come up with something that makes you stand apart from the crowd. I never understood the release cycle model anyhow, whats the goal of that? To show off the latest tech in the open source world? Really? With Slackware and Fedora and Suse and hosts of other flavors of GNU/Linux all doing the same thing?</font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">What do we have that others don't? We have something new that can be great if planned right. There are 100's of distros releasing in cycles, let's get out of that and truly showcase the best of open source through:</font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">Unstable branch - absolute latest software here...</font></div><div><font class="Apple-style-span" face="arial" size="2">Rolling unstable - + Still risky but not on the lines of unstable</font></div><div><font class="Apple-style-span" face="arial" size="2">Rolling stable - everyday use and very stable </font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">You could throw in "snapshots" and support those for X amount of time as I have posted in the other place if you wanted (based on rolling unstable). You could also have LTS releases based on Rolling stable.... It's up to you.</font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">I don't believe we need yet another "burn new disk every X months for????" distribution. </font></div><div></div></td></tr></table>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/e6448a8c/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/e6448a8c/attachment.html new file mode 100644 index 000000000..efc907a93 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/e6448a8c/attachment.html @@ -0,0 +1,3 @@ +<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><font class="Apple-style-span" face="arial" size="2">I made another post in a different thread about the way I feel the release cycle should go. After more thinking I do think that I really have the right idea and here is why...</font><div style="font-family: arial; font-size: 10pt; "><br></div><div><font class="Apple-style-span" face="arial" size="2">Going the route of release cycles really does not make this distribution fit into anything. You going to try and appeal to new people? Ubuntu has that </font><font class="Apple-style-span" face="arial" size="2">covered and you will never steal that role. Hoping to become a geek type distro? There are many that have that covered. </font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">The best thing you can do as a + team is try to come up with something that makes you stand apart from the crowd. I never understood the release cycle model anyhow, whats the goal of that? To show off the latest tech in the open source world? Really? With Slackware and Fedora and Suse and hosts of other flavors of GNU/Linux all doing the same thing?</font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">What do we have that others don't? We have something new that can be great if planned right. There are 100's of distros releasing in cycles, let's get out of that and truly showcase the best of open source through:</font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">Unstable branch - absolute latest software here...</font></div><div><font class="Apple-style-span" face="arial" size="2">Rolling unstable - + Still risky but not on the lines of unstable</font></div><div><font class="Apple-style-span" face="arial" size="2">Rolling stable - everyday use and very stable </font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">You could throw in "snapshots" and support those for X amount of time as I have posted in the other place if you wanted (based on rolling unstable). You could also have LTS releases based on Rolling stable.... It's up to you.</font></div><div><font class="Apple-style-span" face="arial" size="2"><br></font></div><div><font class="Apple-style-span" face="arial" size="2">I don't believe we need yet another "burn new disk every X months for????" distribution. </font></div><div></div></td></tr></table>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110613/f23c0327/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110613/f23c0327/attachment-0001.html new file mode 100644 index 000000000..b295e5388 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/f23c0327/attachment-0001.html @@ -0,0 +1,6 @@ +<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> +</div></div>Â As I said with different<br> +words, not using a volunteer's help would be a crime !<br> +<font color="#888888"><br> +Samuel<br> +</font></blockquote></div><br><div>:-))</div><div>I ready to start</div><div><br></div><div>Magnus</div> diff --git a/zarb-ml/mageia-dev/attachments/20110613/f23c0327/attachment.html b/zarb-ml/mageia-dev/attachments/20110613/f23c0327/attachment.html new file mode 100644 index 000000000..b295e5388 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/f23c0327/attachment.html @@ -0,0 +1,6 @@ +<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> +</div></div>Â As I said with different<br> +words, not using a volunteer's help would be a crime !<br> +<font color="#888888"><br> +Samuel<br> +</font></blockquote></div><br><div>:-))</div><div>I ready to start</div><div><br></div><div>Magnus</div> diff --git a/zarb-ml/mageia-dev/attachments/20110613/f7a3e7a1/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110613/f7a3e7a1/attachment-0001.asc new file mode 100644 index 000000000..b8f35eaad --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/f7a3e7a1/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32D2gACgkQqEs9DA4DquCmcgCZAeQva7ID+dwIkknzx+ydGchn +tm0AoIQR+Kx3h0wBElcUlkC/ljtuDWIa +=bXp7 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/f7a3e7a1/attachment.asc b/zarb-ml/mageia-dev/attachments/20110613/f7a3e7a1/attachment.asc new file mode 100644 index 000000000..b8f35eaad --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/f7a3e7a1/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32D2gACgkQqEs9DA4DquCmcgCZAeQva7ID+dwIkknzx+ydGchn +tm0AoIQR+Kx3h0wBElcUlkC/ljtuDWIa +=bXp7 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/f7d7bb63/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110613/f7d7bb63/attachment-0001.asc new file mode 100644 index 000000000..6dab76c10 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/f7d7bb63/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32LpIACgkQqEs9DA4DquAlTQCfWItTIK6hEJN1dVAysQCkD4I3 +p7oAniE7AQumZaTnxIapZiNlWfIQXFmi +=yi8s +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/f7d7bb63/attachment.asc b/zarb-ml/mageia-dev/attachments/20110613/f7d7bb63/attachment.asc new file mode 100644 index 000000000..6dab76c10 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/f7d7bb63/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk32LpIACgkQqEs9DA4DquAlTQCfWItTIK6hEJN1dVAysQCkD4I3 +p7oAniE7AQumZaTnxIapZiNlWfIQXFmi +=yi8s +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/f90a3a85/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20110613/f90a3a85/attachment-0001.asc new file mode 100644 index 000000000..d76cd4e42 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/f90a3a85/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk31x60ACgkQqEs9DA4DquBeyQCghWm7sW2vvPd6VphcEYuC45So +gJoAn0qXtRtZ3GjuimN8bQjg/VTLaBTL +=rEbd +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20110613/f90a3a85/attachment.asc b/zarb-ml/mageia-dev/attachments/20110613/f90a3a85/attachment.asc new file mode 100644 index 000000000..d76cd4e42 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110613/f90a3a85/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.10 (GNU/Linux) + +iEYEABECAAYFAk31x60ACgkQqEs9DA4DquBeyQCghWm7sW2vvPd6VphcEYuC45So +gJoAn0qXtRtZ3GjuimN8bQjg/VTLaBTL +=rEbd +-----END PGP SIGNATURE----- |