Re: Code freeze break request

[Alexander Larsson <alexl redhat com>]

On Fri, 2008-03-07 at 12:21 -0500, David Zeuthen wrote:
> On Fri, 2008-03-07 at 12:33 +0100, Alexander Larsson wrote:
> > 2 - Don't automount gphoto:// volumes. This is problematic,
> >     as when they are mounted other apps can't access the device.
> >     Longterm they should ideally use gio to access the files so
> >     that everyone can share the connection and apps don't need
> >     gphoto specific code. However, atm the automount is causing
> >     problem by locking out apps using libgphoto directly.
> 
> I'm fundamentally against bending over for broken apps. At the very
> least please make a note in the release notes / NEWS / whatever that
> states that this thing is only something for 2.22 and it's going to
> change for 2.24. Also want to note that, by then, apps then either need
> to start using gio or do something else like making sure they can access
> the USB device. 

You have a kinda strange notion of "broken apps" I must say. Apparently
it includes everything that doesn't immediately drop everything and
change their code to work with our new system rather than the way it has
been working since forever.

Did you actually talk to any of the affected application developers
about this, or do you just expect them to read our mailing lists and
figure this out?

The fact is that our code broke working applications, and there is
currently zero applications ported to the new model. Its a huge
disservice to users to ship with it enabled.