Now it's http://mageia.org/press/faq/ it should be http://mageia.org/en/faq/
Also Press reviews http://mageia.org/press/ link is missing on some pages.
For example http://mageia.org/en/.
I know it's temporary but I think it's still important.
Thanks to all contributors and especially to
On 3 October 2010 09:58, Fabrice Facorat fabrice.faco...@gmail.com wrote:
Specifying what exactly is wrong is an essential issue here:
- Just perl is hard to understand isn't a problem for users, users
don't code it.
but for dev and potential contributor this increase the antry barrier
for
On 4 October 2010 23:53, Robert Xu rob...@gmail.com wrote:
Please do not quote so many useless quotes
would it be possible to move drakxtools slowly away from perl gtk?
Or at least make perl gtk better (and provide a perlQt implementation?)
Because as far as I'm concerned, if any of
On 5 October 2010 00:09, Liam R E Quin l...@holoweb.net wrote:
But rpmdrake ported to Qt would probably freeze up in the same places.
It needs more asynchronous operations. At one point I thought about
using dbxml (a small, fast interface to XML documents, with a btree
index and dynamic
On 5 October 2010 04:43, Hoyt Duff hoytd...@gmail.com wrote:
On Mon, Oct 4, 2010 at 10:15 PM, Ahmad Samir ahmadsamir3...@gmail.com wrote:
If upstream can't accomplish this in their apps, how do you expect
downstream to do it?
Easy. Both upstream and downstream should obey the $BROWSER
Juan Luis Baptiste wrote:
On Mon, Oct 4, 2010 at 7:40 PM, Fernando Parra
gato2...@yahoo.com.mx wrote:
A different approach could be a light rolling distro, let me explain. A
distro with a selected number of programs updated regular as their new
versions are available.
That's what
Wolfgang Bornath wrote:
2010/10/2 Michael Scherer m...@zarb.org:
So I say no to this idea. Asking useless questions just add burden to
the user. People that have a preferred browser know how to install it,
those that don't do not care enough.
Reasonable. Can also be applied to other such
Personally I think the way Mandriva maintains both updates and backports
for each release is a waste of resources.
I do agree that Mageia should be a semi-rolling distro.
By semi rolling distro I mean the following:
Release a distro every 8-12 months (the exact cyle is not the point I'm
On 5 October 2010 15:56, Tux99 tux99-...@uridium.org wrote:
Quote: Ahmad Samir wrote on Tue, 05 October 2010 15:47
Again a rolling distro is something that's not clearly defined. And to
be honest, a rolling distro isn't suitable for new or inexperienced
users. Simply because you can't
Le mardi 05 octobre 2010 à 15:28 +0200, Tux99 a écrit :
This would reduce the space requirements on the mirrors and it would mean
that Mageia is a rolling distro for most apps, making it more attractive
compared to ubuntu/Fedora/opensuse and at the same time reduce the workload
for packagers.
Quote: Michael Scherer wrote on Tue, 05 October 2010 17:53
Instead of focusing on features in cooker and focus on bug fixing once
the release is near, I will just have to focus on bug fixing every
time.
So to me, that's a increase of workload.
I think you misunderstood the concept
R James wrote:
[...]
I did make a few post-installation tweaks:
1. Remove msec.
2. Disable PulseAudio.
3. Delete /etc/X11/xinit.d/70net_applet
(net_applet is a pig and not needed for static wired connection)
Google Chromium is finally a browser that can handle gmail on
low-resource systems.
On 5 October 2010 18:54, Tux99 tux99-...@uridium.org wrote:
Quote: Ahmad Samir wrote on Tue, 05 October 2010 17:41
A rolling distro isn't a defined term, as Michael explained, now you
add light to the equation and it becomes even more undefined.
You shouldn't look at the name but rather at
On Tue, 05 Oct 2010 09:44:53 -0400
Marc Paré m...@marcpare.com wrote:
However, changing to a light rolling distro would force other
users, who don't necessarily want these updates (or, don't want
to pay for all the bandwidth for these updates, because they
are happy with the version
On Tue, 5 Oct 2010, Ahmad Samir wrote:
I looked at the description that Michael gave. And I think I know what
a rolling distro is having Cooker and all :). light/heavy makes no
sense here.
I give up, i'm not sure if it's a communication problem or if you are
simply pretending not to
Le mardi 05 octobre 2010 à 20:17 +0200, Ahmad Samir a écrit :
On 5 October 2010 19:53, Tux 99 tux99-...@uridium.org wrote:
On Tue, 5 Oct 2010, Ahmad Samir wrote:
I looked at the description that Michael gave. And I think I know what
a rolling distro is having Cooker and all :).
On Tue, 05 Oct 2010, Tux99 wrote:
Quote: Michael Scherer wrote on Tue, 05 October 2010 17:53
Instead of focusing on features in cooker and focus on bug fixing once
the release is near, I will just have to focus on bug fixing every
time.
So to me, that's a increase of workload.
On Wed, 06 Oct 2010, Tux99 wrote:
On Wed, 6 Oct 2010, nicolas vigier wrote:
I think you misunderstood the concept proposed, we are not talking about
replacing cooker/cauldron, just merging updates and backports for the
released version.
And then you run urpmi --auto-select on
Le mercredi 06 octobre 2010 à 01:24 +0200, Tux99 a écrit :
On Wed, 6 Oct 2010, nicolas vigier wrote:
1) I'd never use Mandriva on a server, because of the short support
period, a server OS requires at least 4-5 years support lifecycles
(I'm not talking about MES here, just the normal
19 matches
Mail list logo
