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/20111116 | |
| 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/20111116')
4 files changed, 336 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment-0001.html new file mode 100644 index 000000000..a81c6d704 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment-0001.html @@ -0,0 +1,45 @@ +<!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"> + On 16/11/2011 10:44, Guillaume Rousse wrote: + <blockquote cite="mid:4EC38611.1040608@gmail.com" type="cite">Le + 16/11/2011 00:11, jcc a écrit : + <br> + <blockquote type="cite">Hi, + <br> + <br> + I do not quite understand why with BuildRequires and Requires, + it is + <br> + sometimes necessary to place a pkgconfig(any_lib) instead of + simply + <br> + any_libin the spec file. + <br> + </blockquote> + If you have a dependency for any_lib, you'll only get the runtime + part of the lib. If you need to build something with the lib, + you'll need the buildtime part of the lib, which is generally + isolated in the -devel package. Hence the need for a build + dependency of either any_lib-devel (always present), or + pkgconfig(any_lib), which is a virtual package automatically + generated by rpm if a pkgconfig file is present. + <br> + <br> + </blockquote> + <br> + <div style="width: 100%;"><br> + </div> + <div id="gt-res-content" class="almost_half_cell"> + <div dir="ltr" style=""><span id="result_box" class="short_text" + lang="en"><span class="hps">I thank you for</span> <span + class="hps">these explanations.</span><br> + <br> + <span class="hps">Sincerely, J.-C.<br> + </span></span></div> + </div> + </body> +</html> diff --git a/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment.html b/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment.html new file mode 100644 index 000000000..a81c6d704 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment.html @@ -0,0 +1,45 @@ +<!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"> + On 16/11/2011 10:44, Guillaume Rousse wrote: + <blockquote cite="mid:4EC38611.1040608@gmail.com" type="cite">Le + 16/11/2011 00:11, jcc a écrit : + <br> + <blockquote type="cite">Hi, + <br> + <br> + I do not quite understand why with BuildRequires and Requires, + it is + <br> + sometimes necessary to place a pkgconfig(any_lib) instead of + simply + <br> + any_libin the spec file. + <br> + </blockquote> + If you have a dependency for any_lib, you'll only get the runtime + part of the lib. If you need to build something with the lib, + you'll need the buildtime part of the lib, which is generally + isolated in the -devel package. Hence the need for a build + dependency of either any_lib-devel (always present), or + pkgconfig(any_lib), which is a virtual package automatically + generated by rpm if a pkgconfig file is present. + <br> + <br> + </blockquote> + <br> + <div style="width: 100%;"><br> + </div> + <div id="gt-res-content" class="almost_half_cell"> + <div dir="ltr" style=""><span id="result_box" class="short_text" + lang="en"><span class="hps">I thank you for</span> <span + class="hps">these explanations.</span><br> + <br> + <span class="hps">Sincerely, J.-C.<br> + </span></span></div> + </div> + </body> +</html> diff --git a/zarb-ml/mageia-dev/attachments/20111116/ebfb4023/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20111116/ebfb4023/attachment-0001.html new file mode 100644 index 000000000..a3d1e6b74 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111116/ebfb4023/attachment-0001.html @@ -0,0 +1,123 @@ +<!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"> + <div class="moz-text-flowed" style="font-family: -moz-fixed; + font-size: 12px;" lang="x-unicode">On 14.11.2011 14:53, Buchan + Milne wrote: + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);"> + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);"> + <blockquote type="cite" style="color: rgb(0, 0, 0);"> ( and + given the discussion + <br> + <br> + on ml, it should be soon ) + <br> + </blockquote> + When I ask the developers, they don't know if qemu will + include the + <br> + patch at all and when (now or after one year) and they + suggested to do + <br> + the openSUSE way (today the most recommended and full featured + Linux + <br> + distro for GNS3). + <br> + </blockquote> + [...] + <br> + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);">OK. So if + gns3 can't be fixed for the stable - than should be removed + <br> + from the repos (for ISOs is to late). + <br> + <br> + If we don't provide qemu patch, then gns3 should be removed + from + <br> + Cauldron as well. + <br> + <br> + I believe removing GNS3 is better than keeping it broken and.. + irritate + <br> + people (I don't count the opinion of our quality). Later some + 3rd party + <br> + repos can provide GNS3 and its dependencies. + <br> + </blockquote> + You seem to imply that the only use of GNS3 is with this qemu + patch. + <br> + </blockquote> + It's possible to simulate and play without qemu. + (btw newer alpha release version supports in the same way + VirtualBox)<br> + <br> + It should be "Suggested" by GNS3, but then what is the idea of + suggesting qemu that isn't working at all? I simply don't know why + to distribute a program that provides support in GUI for something + that's not working. + <br> + <br> + People can try to waste their time and configure qemuwrapper with + our qemu... it's just a matter of time for a bugrequest on our + bugzilla. + <br> + <br> + In my opinion if we provide an application with so exposed + (visible) support for working with qemu and we don't provide qemu + itself then our quality of packages get lower. + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);">But I used + GNS3 with just dynamips, and this issue of GNS3 not being usable + at + <br> + all due to missing dynamips can really be solved quite quickly + just by + <br> + shipping dynamips to updates. + <br> + </blockquote> + Yes. + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);">But, it looks + like someone blindly imported gns3 and dynagen from Mandriva + <br> + without even understanding the use of these tools: + <br> + <br> + $ rpm -q --suggests dynagen + <br> + dynamips>= 0.2.8 + <br> + xterm + <br> + <br> + (dynamips isn't explicitly required to be installed on the host + with gns3 or + <br> + dynagen, as the hypervisor can be run on a different host than + dynagen/GNS3). + <br> + <br> + </blockquote> + In theory yes. + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);">Regards, + <br> + Buchan + <br> + </blockquote> + <br> + </div> + </body> +</html> diff --git a/zarb-ml/mageia-dev/attachments/20111116/ebfb4023/attachment.html b/zarb-ml/mageia-dev/attachments/20111116/ebfb4023/attachment.html new file mode 100644 index 000000000..a3d1e6b74 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111116/ebfb4023/attachment.html @@ -0,0 +1,123 @@ +<!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"> + <div class="moz-text-flowed" style="font-family: -moz-fixed; + font-size: 12px;" lang="x-unicode">On 14.11.2011 14:53, Buchan + Milne wrote: + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);"> + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);"> + <blockquote type="cite" style="color: rgb(0, 0, 0);"> ( and + given the discussion + <br> + <br> + on ml, it should be soon ) + <br> + </blockquote> + When I ask the developers, they don't know if qemu will + include the + <br> + patch at all and when (now or after one year) and they + suggested to do + <br> + the openSUSE way (today the most recommended and full featured + Linux + <br> + distro for GNS3). + <br> + </blockquote> + [...] + <br> + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);">OK. So if + gns3 can't be fixed for the stable - than should be removed + <br> + from the repos (for ISOs is to late). + <br> + <br> + If we don't provide qemu patch, then gns3 should be removed + from + <br> + Cauldron as well. + <br> + <br> + I believe removing GNS3 is better than keeping it broken and.. + irritate + <br> + people (I don't count the opinion of our quality). Later some + 3rd party + <br> + repos can provide GNS3 and its dependencies. + <br> + </blockquote> + You seem to imply that the only use of GNS3 is with this qemu + patch. + <br> + </blockquote> + It's possible to simulate and play without qemu. + (btw newer alpha release version supports in the same way + VirtualBox)<br> + <br> + It should be "Suggested" by GNS3, but then what is the idea of + suggesting qemu that isn't working at all? I simply don't know why + to distribute a program that provides support in GUI for something + that's not working. + <br> + <br> + People can try to waste their time and configure qemuwrapper with + our qemu... it's just a matter of time for a bugrequest on our + bugzilla. + <br> + <br> + In my opinion if we provide an application with so exposed + (visible) support for working with qemu and we don't provide qemu + itself then our quality of packages get lower. + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);">But I used + GNS3 with just dynamips, and this issue of GNS3 not being usable + at + <br> + all due to missing dynamips can really be solved quite quickly + just by + <br> + shipping dynamips to updates. + <br> + </blockquote> + Yes. + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);">But, it looks + like someone blindly imported gns3 and dynagen from Mandriva + <br> + without even understanding the use of these tools: + <br> + <br> + $ rpm -q --suggests dynagen + <br> + dynamips>= 0.2.8 + <br> + xterm + <br> + <br> + (dynamips isn't explicitly required to be installed on the host + with gns3 or + <br> + dynagen, as the hypervisor can be run on a different host than + dynagen/GNS3). + <br> + <br> + </blockquote> + In theory yes. + <br> + <blockquote type="cite" style="color: rgb(0, 0, 0);">Regards, + <br> + Buchan + <br> + </blockquote> + <br> + </div> + </body> +</html> |