From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- .../20111116/d050d796/attachment-0001.html | 45 ++++++++ .../attachments/20111116/d050d796/attachment.html | 45 ++++++++ .../20111116/ebfb4023/attachment-0001.html | 123 +++++++++++++++++++++ .../attachments/20111116/ebfb4023/attachment.html | 123 +++++++++++++++++++++ 4 files changed, 336 insertions(+) create mode 100644 zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment.html create mode 100644 zarb-ml/mageia-dev/attachments/20111116/ebfb4023/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20111116/ebfb4023/attachment.html (limited to 'zarb-ml/mageia-dev/attachments/20111116') 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 @@ + + + + + + + On 16/11/2011 10:44, Guillaume Rousse wrote: +
Le + 16/11/2011 00:11, jcc a écrit : +
+
Hi, +
+
+ I do not quite understand why with BuildRequires and Requires, + it is +
+ sometimes necessary to place a pkgconfig(any_lib) instead of + simply +
+ any_libin the spec file. +
+
+ 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. +
+
+
+
+

+
+
+
I thank you for these explanations.
+
+ Sincerely, J.-C.
+
+
+ + 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 @@ + + + + + + + On 16/11/2011 10:44, Guillaume Rousse wrote: +
Le + 16/11/2011 00:11, jcc a écrit : +
+
Hi, +
+
+ I do not quite understand why with BuildRequires and Requires, + it is +
+ sometimes necessary to place a pkgconfig(any_lib) instead of + simply +
+ any_libin the spec file. +
+
+ 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. +
+
+
+
+

+
+
+
I thank you for these explanations.
+
+ Sincerely, J.-C.
+
+
+ + 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 @@ + + + + + + +
On 14.11.2011 14:53, Buchan + Milne wrote: +
+
+
+
+
   ( and + given the discussion +
+
+ on ml, it should be soon ) +
+
+ When I ask the developers, they don't know if qemu will + include the +
+ patch at all and when (now or after one year) and they + suggested to do +
+ the openSUSE way (today the most recommended and full featured + Linux +
+ distro for GNS3). +
+
+ [...] +
+
+
OK. So if + gns3 can't be fixed for the stable - than should be removed +
+ from the repos (for ISOs is to late). +
+
+ If we don't provide qemu patch, then gns3 should be removed + from +
+ Cauldron as well. +
+
+ I believe removing GNS3 is better than keeping it broken and.. + irritate +
+ people (I don't count the opinion of our quality). Later some + 3rd party +
+ repos can provide GNS3 and its dependencies. +
+
+ You seem to imply that the only use of GNS3 is with this qemu + patch. +
+
+ It's possible to simulate and play without qemu. + (btw newer alpha release version supports in the same way + VirtualBox)
+
+ 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. +
+
+ 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. +
+
+ 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. +
+
But I used + GNS3 with just dynamips, and this issue of GNS3 not being usable + at +
+ all due to missing dynamips can really be solved quite quickly + just by +
+ shipping dynamips to updates. +
+
+ Yes. +
+
But, it looks + like someone blindly imported gns3 and dynagen from Mandriva +
+ without even understanding the use of these tools: +
+
+ $ rpm -q --suggests dynagen +
+ dynamips>= 0.2.8 +
+ xterm +
+
+ (dynamips isn't explicitly required to be installed on the host + with gns3 or +
+ dynagen, as the hypervisor can be run on a different host than + dynagen/GNS3). +
+
+
+ In theory yes. +
+
Regards, +
+ Buchan +
+
+
+
+ + 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 @@ + + + + + + +
On 14.11.2011 14:53, Buchan + Milne wrote: +
+
+
+
+
   ( and + given the discussion +
+
+ on ml, it should be soon ) +
+
+ When I ask the developers, they don't know if qemu will + include the +
+ patch at all and when (now or after one year) and they + suggested to do +
+ the openSUSE way (today the most recommended and full featured + Linux +
+ distro for GNS3). +
+
+ [...] +
+
+
OK. So if + gns3 can't be fixed for the stable - than should be removed +
+ from the repos (for ISOs is to late). +
+
+ If we don't provide qemu patch, then gns3 should be removed + from +
+ Cauldron as well. +
+
+ I believe removing GNS3 is better than keeping it broken and.. + irritate +
+ people (I don't count the opinion of our quality). Later some + 3rd party +
+ repos can provide GNS3 and its dependencies. +
+
+ You seem to imply that the only use of GNS3 is with this qemu + patch. +
+
+ It's possible to simulate and play without qemu. + (btw newer alpha release version supports in the same way + VirtualBox)
+
+ 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. +
+
+ 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. +
+
+ 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. +
+
But I used + GNS3 with just dynamips, and this issue of GNS3 not being usable + at +
+ all due to missing dynamips can really be solved quite quickly + just by +
+ shipping dynamips to updates. +
+
+ Yes. +
+
But, it looks + like someone blindly imported gns3 and dynagen from Mandriva +
+ without even understanding the use of these tools: +
+
+ $ rpm -q --suggests dynagen +
+ dynamips>= 0.2.8 +
+ xterm +
+
+ (dynamips isn't explicitly required to be installed on the host + with gns3 or +
+ dynagen, as the hypervisor can be run on a different host than + dynagen/GNS3). +
+
+
+ In theory yes. +
+
Regards, +
+ Buchan +
+
+
+
+ + -- cgit v1.2.1