[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [abc] not compiling in [xyz]
From:       Manuel Amador <rudd-o () amautacorp ! com>
Date:       2004-09-16 22:58:53
Message-ID: 1095375532.5475.9.camel () master ! amauta
[Download RAW message or body]

Maybe the right thing to do in order to catch these situations early is
to setup some kind of tinderbox like mozilla did.

El lun, 13-09-2004 a las 17:14, J. Preiss escribió:
> In principle, I'd agree. Great!
> In reality I could not compile kdebase for about 3 days, ad I'm still not sure 
> to be able to compile it...
> Anyway, shit happens. Its not the question why I can't compile it. Its not the 
> question how long it takes you to get this error out. You'll get it, we'll 
> get it, somehow, maybe tonight or maybe tomorrow. 
> But lets assume we are working on ...mmh.. kdemultimedia (dont know)... and we 
> are getting the latest kdelibs (example) which does not compile 
> (example!!!!). What you're doing next? - Nothing, probably. 
> 
> To declare a package to be "not compilable" would mean: hey, we have a 
> problem, dont check it out now, we are working on it. If you already have it 
> - sorry. In best case: we got the error in 2 minutes, you can get it now, try 
> it again. In worst case: oh, sorry, he/she's on holiday. This could be a 
> fix...
> 
> The best case of this multimedia programmer would be : I am trying to get the 
> latest version... oh, 10 tried to get the latest version, but they all run 
> into trouble...
> Do you know what I mean? - Just an idea.
> 
> 
> Am Montag, 13. September 2004 23:04 schrieb David Faure:
> > On Monday 13 September 2004 22:51, J. Preiss wrote:
> > > Hi all,
> > >
> > > currently writing on my qbuildkde... and read those messages about
> > > "cannot compile ...". I have those problems, too (of course), so I am
> > > wondering if it would be possible to declare a package to be "not
> > > compilable" or something like that. Could that be implemented somehow?
> >
> > No, because we prefer to fix things rather than mark them as broken.
> > That's the right approach, isn't it?
> > Seriously, things don't remain broken for long, when they are broken, so I
> > don't see your point.
>  
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]