After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 302202 - [Patch] RFE: module support in gnome_vfs_get_volume_free_space
[Patch] RFE: module support in gnome_vfs_get_volume_free_space
Status: RESOLVED FIXED
Product: gnome-vfs
Classification: Deprecated
Component: Other
cvs (head)
Other All
: Normal enhancement
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-27 18:01 UTC by Alexander Brausewetter
Modified: 2005-05-02 13:45 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
Proposed patch (25.04 KB, patch)
2005-04-28 01:02 UTC, Alexander Brausewetter
committed Details | Review

Description Alexander Brausewetter 2005-04-27 18:01:50 UTC
gnome_vfs_get_volume_free_space should provide module support.

There should be a new method func GnomeVFSMethodGetVolumeFreeSpaceFunc which
handles this.
Comment 1 Alexander Brausewetter 2005-04-28 01:02:24 UTC
Created attachment 45766 [details] [review]
Proposed patch
Comment 2 Allison Karlitskaya (desrt) 2005-04-29 07:41:05 UTC
I wonder if maybe this should just be added to the vfs file information
structure and fetched via the current vfs stat call?

In any case, if this gets merged, please make a comment about it in bug #148297
since your patch will invalidate the patch there.
Comment 3 Alexander Brausewetter 2005-04-29 12:48:07 UTC
Having it implemented by adding a new MethodFunc has the advantage that it
doesn't break the GNOME-VFS API.
Comment 4 Allison Karlitskaya (desrt) 2005-04-29 16:40:34 UTC
If it's added as a new field to the structure that nobody knows about then
you're keeping API compatibility just as much as adding a new function call.

also: The GnomeVFSFileInfo structure contains extra space at the end (void
*reserved1-*reserved5) so that the field can be added without breaking ABI
compatibility.

I'm not sure that I actually like my idea -- I'm just presenting it as an
alternative.
Comment 5 Alexander Brausewetter 2005-04-30 17:16:31 UTC
Hmm.. One thing is that the free volume space isn't really file info but more
volume info so it would probably be good to seperate it. However,
gnome_vfs_get_volume_free_space already takes a file URL to make out the volume.

If we add it as a field to GnomeVFSFileInfo and deprecate
gnome_vfs_get_volume_free_space but don't remove it for now but use it as a
wrapper for get_file_info, it would not break API nor ABI. Probably good.
Comment 6 Alexander Larsson 2005-05-02 13:45:31 UTC
I prefer it as a separate call. GnomeVFSFileInfo is really information about the
file, and volume info is not, even if it takes a uri argument.