Fwd: PPA Assistance and Bug/Patch Triage

["John Stowers" <john stowers gmail com>]

Oops forward to list

---------- Forwarded message ----------
From: John Stowers <john stowers gmail com>
Date: Wed, Jan 21, 2009 at 12:40 PM
Subject: Re: PPA Assistance and Bug/Patch Triage
To: Julien Lavergne <julien lavergne gmail com>

On Wed, Jan 21, 2009 at 12:22 PM, Julien Lavergne <julien lavergne gmail com> wrote:

Thanks. This is what I have in mind :

Hi Julien

Thanks for your enthusiastic reaction. Comments follow
 

- We can use one repository for stable release and svn snapshots, using
2 different names for the packages (conduit for stable, and
conduit-trunk for snapshots). Users will have only one line to add in
their sources.list and can switch when they want from the stable to the
unstable packages. Of course, installing the unstable will remove the
stable package.

Sounds good.
 

- I'll publish a bzr branch which is a branch of the bzr mirror of GNOME
SVN. It'll contain the debian/ directory needed to build the package. I
think it easier to work on a separate branch for not introducing
"distribution-specific" stuff in an upstream development tree (also,
Debian and Ubuntu guys should not be happy to find a debian directory in
the release tarball :)) I also need this bzr branch for my script.

Sounds good.
 

- Since Conduit depends on GIO and Webkit python bindings, it could be
difficult to safely and quickly made packages for version under Intrepid
(8.10). If more support is really needed, it can be planned later.

As you might know, Conduit supports both webkit/gtkmozembed for the web browser, and gio/gnomevfs for the file implementation. The latest stable 0.3.15 release defaults to gtkmozembed and gnomevfs, however I recommend webkit and gio. To change the conduit defaults for these features, you change the appropriate constants in conduit/__init__.py. You will see this is what the patch in the debian/ubuntu package does (I hope). If depending on webkit, then you can also install conduit.real to /usr/bin/conduit (the old wrapper script was necessary for firefox to not crash)

So, I am happy to just support intrepid by updating the 0.3.14 package to work against the 0.3.15 release.

Releases from trunk, i.e. conduit-svn snapshots need no such patching, as the default file and browser implementation has been changed to GIO and webkit.

With this in mind, I agree that supporting >= intrepid is the correct decision.

Thanks for your work,

Regards

John

Regards,
Julien Lavergne

On Wed, 2009-01-21 at 09:49 +1300, John Stowers wrote:
>
>
> On Wed, Jan 21, 2009 at 7:22 AM, Julien Lavergne
> <julien lavergne gmail com> wrote:
>         Hi,
>
>         I can work on the PPA side, I done the same thing for Awn and
>         I think it
>         won't too difficult to set. I can confirm that a repository
>         with
>         packages up to the last svn/bzr revision is very useful for
>         the
>         development/testing :)
>
>         Tell me if with you are agree so I can start to look at it.
>
> Agree++
>
> We would all be super grateful if you could do this.
>
> Regards
>
> John
>
>
>
>
>         Regards,
>         Julien Lavergne
>
>
>         On Tue, 2009-01-20 at 17:17 +1300, John Stowers wrote:
>         > Hi Guys,
>         >
>         > I have been back working on Conduit over the last few days,
>         reviewing
>         > patches, hacking, etc. I have been a little disappointed
>         that Ubuntu
>         > did not pick up our stable releases. It feels like we will
>         always be
>         > out of date on that platform.
>         >
>         > To solve this problem I want to get some PPA packages for
>         Ubuntu
>         > built. I am unfamiliar with debian packaging, so I would
>         like to see
>         > if someone would be able to do this for me. Basically, I
>         would really
>         > really like it if
>         > 1)     We had a conduit stable repository, that always has
>         the latest
>         > Conduit release, installable for hardy, intrepid, jaunty
>         > 2)     We also have a conduit development repository that
>         tracks SVN
>         > HEAD. What would be super cool was if there was also a
>         script in
>         > conduit/scripts/build_svn_package.sh that executed the
>         necessary magic
>         > commands to build a package, and uploaded it to the conduit
>         > development repository. It would also make sense to have a
>         > conduit/scripts/build_stable_package.sh script too.
>         >
>         > If anyone could help with these tasks, I would be much
>         appreciated.
>         >
>         > Finally, if anyone has a favorite bug or patch in bugzilla,
>         please
>         > tell me about it so I do not forget.
>         >
>         > John
>
>
>         > _______________________________________________
>         > Conduit-list mailing list
>         > Conduit-list gnome org
>         > http://mail.gnome.org/mailman/listinfo/conduit-list
>
>
>