On 3 October 2010 09:58, Fabrice Facorat 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 contribution
No
On 4 October 2010 23:53, Robert Xu 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 these GUIs freeze
On 5 October 2010 00:09, Liam R E Quin 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 hashing), which
On 5 October 2010 04:43, Hoyt Duff wrote:
> On Mon, Oct 4, 2010 at 10:15 PM, Ahmad Samir 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
>>> environment variable.
>
2010/10/5 Thierry Vignaud :
> On 3 October 2010 09:58, Fabrice Facorat 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 a
Le mardi 05 octobre 2010 à 13:30 +0200, Fabrice Facorat a écrit :
> 2010/10/5 Thierry Vignaud :
> > On 3 October 2010 09:58, Fabrice Facorat wrote:
> >> sure. But do Mandriva still have enough man power to maintain so many
> >> tools ?
> >
> > That's a nop argument. Rewriting from scratch needs m
Juan Luis Baptiste wrote:
> On Mon, Oct 4, 2010 at 7:40 PM, Fernando Parra
> 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 backports are for,
Wolfgang Bornath wrote:
> 2010/10/2 Michael Scherer :
>>
>> 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 thi
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
deba
Quote: Fabrice Facorat wrote on Tue, 05 October 2010 13:30
> > That's a nop argument. Rewriting from scratch needs more manpower
> > whatever is the number of tools...
>
> sure, but if more people are able to contribute, this could counter
> balanced this fact .
Well, Fabrice you should know h
On 5 October 2010 15:28, Tux99 wrote:
>
>
> Personally I think the way Mandriva maintains both updates and backports
> for each release is a waste of resources.
>
How is it a waste?
A practical example is the college professor / school teacher (see
Fernando Parra post a few emails back); he does
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 they
have) to download them.
Other distros are now trying this model, only for
On Tue, 5 Oct 2010, Ahmad Samir wrote:
Actually yes, it's one of the - rather rare - cases where upstream,
OOo, offers readily installable binary rpms :)
(although you have to bear in mind that the openoffice version in the
Mandriva repos was the http://go-oo.org/ version, which has a saner
buil
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 guarantee that a new package won't
> introduce regressions (or
On 5 October 2010 15:54, Dale Huckeby wrote:
> On Tue, 5 Oct 2010, Ahmad Samir wrote:
>
>> Actually yes, it's one of the - rather rare - cases where upstream,
>> OOo, offers readily installable binary rpms :)
>> (although you have to bear in mind that the openoffice version in the
>> Mandriva repo
Maybe here could fit "my" idea of "core" repo.
https://www.mageia.org/pipermail/mageia-discuss/20101001/001761.html
In fact, what you need to define is what's the "core" system.
Then you could see "core system" will be updated every X month.
Example: you decide to update core system every 12 mont
Quote: Gustavo Giampaoli wrote on Tue, 05 October 2010 16:01
>
> In fact, what you need to define is what's the "core" system.
>
> Then you could see "core system" will be updated every X month.
> Example: you decide to update core system every 12 month.
>
> So, "core system 2011" will last 12
On 5 October 2010 15:56, Tux99 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 guarantee that a
Le mardi 05 octobre 2010 à 08:54 -0500, Dale Huckeby a écrit :
> On Tue, 5 Oct 2010, Ahmad Samir wrote:
>
> > Actually yes, it's one of the - rather rare - cases where upstream,
> > OOo, offers readily installable binary rpms :)
> > (although you have to bear in mind that the openoffice version in
On 5 October 2010 16:21, Olivier Méjean wrote:
> Le mardi 5 octobre 2010 15:47:20, Ahmad Samir a écrit :
>> On 5 October 2010 15:28, Tux99 wrote:
>> > Personally I think the way Mandriva maintains both updates and backports
>> > for each release is a waste of resources.
>>
>> How is it a waste?
>
On 5 October 2010 15:28, Tux99 wrote:
> 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.
No. No spac
On Tue, 5 Oct 2010, Thierry Vignaud wrote:
> On 5 October 2010 15:28, Tux99 wrote:
> > 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 ti
Quote: Ahmad Samir wrote on Tue, 05 October 2010 16:27
> And nothing breaks? no critical apps get broken in that model?
>
> Personally I haven't use PCLinuxOS before, so can't tell for sure; my
> guess would be yes, stuff break because new versions are prone to
> introduce regressions. Note that
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 packa
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 prop
On 5 October 2010 17:36, Tux99 wrote:
>
>
> Quote: Ahmad Samir wrote on Tue, 05 October 2010 16:27
>> And nothing breaks? no critical apps get broken in that model?
>>
>> Personally I haven't use PCLinuxOS before, so can't tell for sure; my
>> guess would be yes, stuff break because new versions a
Le 05/10/2010 17:58, Tux99 a écrit :
>
>
> 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 workl
On Tue, 5 Oct 2010, Daniel Le Berre 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.
> >
>
> I guess it would still be possible to choose in the update manager which
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 the description that me and
others have given here earlie
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.
2010/10/5 Giuseppe Ghibò :
> A 233 is probably possible to be emulated on a core i7 using qemu without
> any virtualization (kqemu, etc.), to look how it appear.
Still too fast. We would need to emulate slow PCI bus used for nearly
everything, slower memory, slow memory card :-)
On 5 October 2010 18:54, Tux99 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 the desc
On Tue, 05 Oct 2010 09:44:53 -0400
Marc Paré 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 they have
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 unders
On 5 October 2010 19:53, Tux 99 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 :). light/heavy makes no
>> sense here.
>
> I give up, i'm not sure if it's a communication probl
Hello to everyone on the list,
As some people said in another thread, Mandriva's current media schema already
gives the opportunity to :
- install newer versions of software if needed (from backports media),
- keep a stable system with only security fixes if needed (updates media, for
servers or
Le mardi 05 octobre 2010 à 20:17 +0200, Ahmad Samir a écrit :
> On 5 October 2010 19:53, Tux 99 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 :). light/heavy makes no
Le mardi 05 octobre 2010 à 22:01 +0100, Buchan Milne a écrit :
> Anyway, the rate-of-change in non-rolling distros which have high update rate
> (e.g. Fedora) is unacceptable, real rolling distros are a usability nightmare
> IMHO.
About this, the fedora board is proposing a update policy with l
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 wor
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 your server, and all your web
> site
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 --aut
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 Mandriva variants)
>
> But you can still use it while it i
On Tue, 05 Oct 2010 08:00:46 -0400
Sinner from the Prairy
wrote:
> Juan Luis Baptiste wrote:
>
> > On Mon, Oct 4, 2010 at 7:40 PM, Fernando Parra
> > wrote:
>
> >> A different approach could be a "light rolling distro", let me explain. A
> >> distro with a selected number of programs updated
On Tue, 5 Oct 2010 15:47:20 +0200
Ahmad Samir wrote:
> On 5 October 2010 15:28, Tux99
> wrote:
> >
> >
> > Personally I think the way Mandriva maintains both updates and backports
> > for each release is a waste of resources.
> >
>
> How is it a waste?
>
> A practical example is the college p
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 t
2010/10/6 Michael Scherer :
>
> I do. I even update them more often. And you would be surprised to see
> that it doesn't create as much problem as you can think, if the sysadmin
> is competent enough.
However many small companies can't pay a competent enough sysadmin.
It's why they often choose w
On 6 October 2010 05:02, Fernando Parra wrote:
> On Tue, 5 Oct 2010 15:47:20 +0200
> Ahmad Samir wrote:
>
>> On 5 October 2010 15:28, Tux99
>> wrote:
>> >
>> >
>> > Personally I think the way Mandriva maintains both updates and backports
>> > for each release is a waste of resources.
>> >
>>
>>
Op woensdag 06 oktober 2010 01:24:39 schreef Tux99:
> 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 M
48 matches
Mail list logo
