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 --- zarb-ml/mageia-dev/20110323/003544.html | 79 +++++++++++++++++++++++++++++++++ 1 file changed, 79 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110323/003544.html (limited to 'zarb-ml/mageia-dev/20110323/003544.html') diff --git a/zarb-ml/mageia-dev/20110323/003544.html b/zarb-ml/mageia-dev/20110323/003544.html new file mode 100644 index 000000000..e79a52b57 --- /dev/null +++ b/zarb-ml/mageia-dev/20110323/003544.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor) + + + + + + + + + +

[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)

+ Tux99 + tux99-mga at uridium.org +
+ Wed Mar 23 22:29:09 CET 2011 +

+
+ +
+
+Quote: Balcaen John wrote on Wed, 23 March 2011 22:05
+
+> But as i said before (like others), you should first try to build it
+> locally, 
+> check it's working, intergrate nicely for menu,kdm  then we'll start
+> thinking 
+> about providing an alternative repository.
+
+It goes without saying that I would first build everything locally and test
+it, I always do that with every package I work on.
+
+But like I said, I think a separate/third party repo is a very bad idea,
+the whole point of Mageia was that (unlike with Mandriva) finally all
+contributors could join their efforts rather than having separate third
+party repos all over the place.
+
+If now this is no longer the case then I don't really see the point in
+participating in Mageia as packager.
+
+-- 
+Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1