Would be great if bzr could use gnome-vfs for URLs

Bug #48971 reported by Nicholas Allen on 2006-06-08
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Wishlist
Mattias Eriksson

Bug Description

When on a Unix system it would be great if bzr could use gnome-vfs for URLs. This way you get the benefit of many more protocols (eg smb) and password caching in a safe manner.

I'm not so sure. It would have to be a soft dependency or people would whinge about requiring Gnome libs to install bzr.

Personally I use Gnome, but lots of people use KDE, and in my experience the KDE VFS technology (kioslaves) is actually better than gnome-vfs. So should we use it instead?

This could get messy fast :)

Changed in bzr:
importance: Untriaged → Wishlist
status: Unconfirmed → Confirmed

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Ellerman wrote:
> I'm not so sure. It would have to be a soft dependency or people would
> whinge about requiring Gnome libs to install bzr.
>
> Personally I use Gnome, but lots of people use KDE, and in my experience
> the KDE VFS technology (kioslaves) is actually better than gnome-vfs. So
> should we use it instead?

I think this stuff would be a great candidate for a plugin.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEiAQd0F+nu1YWqI0RAnqmAJ9On7wxH/ALe+HvPiriISkZI+nOSgCghBqd
7hJdPAjEjf+fqwZbo5W20PQ=
=s4lG
-----END PGP SIGNATURE-----

Nicholas Allen (nick-allen) wrote :

I would definately like it as a soft dependancy like paramiko is. It could be provided as a plugin and the KDE VFS could be provided in the same way. The gnome api would be much easier to use I would think as it closely resembes the APIs used on local files. The KDE API requires that you save remote files into a temporary file and does not support streaming (at least in my humble understanding which is mostly likely wrong!). But I don't want to way up the pros and cons of either. A gnome API would be preferable to me as there is already work integrating bzr with Nautilus and that uses the gnome API. Then you could use it in Nautilus on any remote share.

In the preferences one could specify a priority for handling URLs if there are multiple handlers (eg paramiko, gnome-vfs, KDE vfs etc). It would ask each in turn and the first to understand the URL would be used. If they were written as plugins then the user could either install the KDE or gnome one as they prefer.

Yeah, that sounds pretty good. Now we just need someone to write it ;)

Nicholas Allen (nick-allen) wrote :

I was thinking that this would make sense as a general purpose python library that is not specific to bzr. The library would offer an abstraction over the various URL handlers and offer a common API and the ability for the user to configure their preferred preference for backends.
I don't mind looking into it. I don't have a lot of spare time and so don't know how long it would take me. I'll publish a branch if I get anything working though...

John A Meinel (jameinel) wrote :

We already have an abstraction at the Transport layer.
My recommendation would be to write a GnomeTransport (or possibly VFSTransport), which would then register all names starting with either gnome+ or vfs+

Then you could access branches as:

vfs+sftp://host/foo/bar
vfs+smb://host/share

Or whatever the gnome notation is. All you need is a custom prefix (foo+ works well), and then register your custom Transport as a handler for those paths.
Then bazaar will happily use your transport for any of those urls.

On Tue, 2006-07-25 at 15:44 +0000, John A Meinel wrote:
> We already have an abstraction at the Transport layer.
> My recommendation would be to write a GnomeTransport (or possibly VFSTransport), which would then register all names starting with either gnome+ or vfs+

You would only register it onces as 'gnomevfs+' or whatever. Then when
you are given the url, strip off gnomevfs+ to get the real URL, and try
it via gnome vfs.

Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Collins wrote:
> On Tue, 2006-07-25 at 15:44 +0000, John A Meinel wrote:
>> We already have an abstraction at the Transport layer.
>> My recommendation would be to write a GnomeTransport (or possibly VFSTransport), which would then register all names starting with either gnome+ or vfs+
>
> You would only register it onces as 'gnomevfs+' or whatever. Then when
> you are given the url, strip off gnomevfs+ to get the real URL, and try
> it via gnome vfs.
>
> Rob

That is actually what I meant. But you said it more clearly.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFExrH7JdeBCYSNAAMRAqzbAJ4jTXvNI/94DbRWrMcaCbRrJVlO0QCfRBua
gWi1wWs+lvcABWHNEWPEQvY=
=gqwK
-----END PGP SIGNATURE-----

Dan Watkins (daniel-thewatkins) wrote :

At Jelmer's request.

Changed in bzr:
assignee: nobody → jelmer

  status triaged
  importance wishlist
  tags gnome-vfs

Initial work on this is available from:

http://people.samba.org/bzr/jelmer/bzr-gnomevfs/

Cheers,

Jelmer

--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

Changed in bzr:
status: Confirmed → Triaged

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Watkins wrote:
| At Jelmer's request.
|
| ** Changed in: bzr
| Assignee: (unassigned) => Jelmer Vernooij (jelmer)
|
Would it make sense to use the new GVFS API that is being developed
instead of the old gnome-vfs API? It should be availble in Hardy Heron
and would deprecate the old gnome-vfs API...

http://mail.gnome.org/archives/gtk-devel-list/2007-February/msg00062.html

Cheers,

Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHzbbK1+i51gqqEGkRAluuAJ9jz94ysw1kPKDO4Aaeg9ft0gPlAgCgqoLd
5ylsmybDqn2zqYoavtePlog=
=G+2q
-----END PGP SIGNATURE-----

Wouter Bolsterlee (uws) wrote :

Gnome VFS is officially deprecated. The new GVFS/GIO system has replaced it.

On Wed, 2008-08-20 at 16:10 +0000, Wouter Bolsterlee (uws) wrote:
> Gnome VFS is officially deprecated. The new GVFS/GIO system has replaced
> it.

So is that 'be nice if we supported gvfs/gio' now? or should we close
the bug?

-Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Wouter Bolsterlee (uws) wrote :

The feature request an sich still stands. Just replace "gnome-vfs" with "gio/gvfs" in the summary. Note that a "gio+" prefix sounds like the sanest url prefix (gio is not necessarily hooking into gvfs, e.g. it does not for local file systems).

Oh, GIO bindings in PyGObject will most likely ship with Gnome 2.24.

Martin Pool (mbp) on 2010-03-19
Changed in bzr:
status: Triaged → Confirmed
Jelmer Vernooij (jelmer) on 2010-09-09
Changed in bzr:
assignee: Jelmer Vernooij (jelmer) → Mattias Eriksson (snaggen)
status: Confirmed → Fix Released
milestone: none → 2.2.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers