Re: Fwd: PPA Assistance and Bug/Patch Triage

[Julien Lavergne <julien lavergne gmail com>]

Hi,

On Wednesday 28 January 2009 14:40:13 John Stowers wrote:
> On Fri, Jan 23, 2009 at 12:38 PM, Julien Lavergne
> <julien lavergne gmail com
>
> > wrote:
> >
> > Thanks :)
> >
> > I just want to add that most of this work rely on the Debian and Ubuntu
> > packaging work. I'll try to follow them as close as possible and report
> > adjustment I made or will make (like the pysqlite2 depends :)).
>
> Thanks Julien.
>
> I have another few tweaks to the package (dependencies) on conduit-trunk,
> pretty please!
>
> * Can you remove both the Suggests: (we no longer use ffmpeg or mplayer, we
> use gstreamer instead)
Done.

> * Can you make us depend on python-gpod
Depends mean that you need this package to work. It seems this is only needed 
if you want to sync an Ipod, right ? python-gpod is set as Recommends, mean 
that python-gpod will be installed when you install conduit, but you can 
remove it without removing conduit itself. IMO, it should stay like this.

> * Can you add a dependency on python-gconf
python-gconf is already included in python-gnome2 package.

>
> I would like your advice on what to do about webkit. Updating to a newer
> PPA snapshot for webkit appears to fix all crashes on my machine for
> logging into facebook [1]. However, it seems to break other packages [2].
> What do you think should be done. Ideally I would like to just depend on
> the webkit-ppa, and then depend on a recent version that I know works, eg
> >= 1.0.1-4+r40220
>
I'm not an expert on Webkit, it depends how snapshots are stable enough. 
Regarding the development of Webkit (not often release), and if it bring 
improvements with no regression for conduit, it is not a bad idea.

> Is it possible to depend on another 3rd party ppa? is this nice thing to
> do? 
Yes, but users need to be aware of this, or you will have many reports about 
broken dependencies :) It's written on the top of the PPA page, but it 
couldn't be enough.

> What about breaking peoples Gwibber?
Well, IMO it's more a Gwibber and Webkit problem :) Gwibber or Webkit packages 
need to mark a conflict with each other regarding this bug, and/or fix it. At 
least, and if you really want to make people aware of this, I can add a 
conflict with Gwibber but it need to be removed when the bug is gone (not 
recommended, it's not an usual practice).

Regards,
Julien Lavergne