On Fri 2003-03-14 at 21:48:20 -0500, [EMAIL PROTECTED] wrote: > On Friday 14 March 2003 08:35 pm, Pierre Fortin wrote: > > > > > Does Mdk even try just *starting* the applications included in a > > release?
I am not sure they should. There are a lot of testers out there. And
if none of them bothered to try the app *and* report problems, I would
consider it reasonable to remove that app, because apparently nobody
cares enough about it.
> > I'm still quite miffed at 9.0 for a number of reasons; however, last
> > night, I asked another list member if ohphone just *started* in 9.1rc2...
> >
> > NOPE! "pwlib problem"
> >
> Did anybody test it on the current cooker? IIRC, rc2 was almost 3 weeks ago
> now.
Well, I just installed it from current cooker (ohphone-1.3.5-1mdk) and
could start it without problem. Did not include much testing, because
I did not care to read the manual, but I can make it searching for
something it calls "gatekeeper". :-)
Yes, there were some fixes only after RC2:
$ rpm -q --changelog ohphone
* Tue Mar 11 2003 Florin <[EMAIL PROTECTED]>
- 1.3.5
- update requires
- remove already intergrated c++fixes patch
- update the lib64 patch
* Sun Dec 01 2002 Gwenole Beauchesne <[EMAIL PROTECTED]> 1.2.11-2mdk
- Patch2: Make it lib64 aware
I also searched the the bug database. Not a single entry for ohphone.
Maybe there was a report directly on the cooker mailing list.
Anyhow, regarding the the late update, I would say: blame yourself.
(I do not mean anyone particular with yourself here.)
Anyone can easily get a working ohphone by testing *and* reporting
problems early. This process works. Really.
Bye,
Benjamin.
pgp00000.pgp
Description: PGP signature
