Summary: | Add information about nautilus vs gnome-volume-manager automounting in 2.22 upgrade guide | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mart Raudsepp <leio> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | pacho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 214260 |
Description
Mart Raudsepp
2008-06-15 20:24:36 UTC
Maybe other option could be rename "automount" USE flag to "nautilus" because: 1. Most common users will tend to enable any "automount" related stuff, even when using nautilus 2. Expected build for using with nautilus is with --disable-automount for preventing conflicts. From gnome-volume-manager Changelog: * src/manager.c: Conditionally disable all of the auto-mounting code which Nautilus is now supposed to handle starting with GNOME 2.22, as far as I understand... Also, distributions like fedora builds gnome-volume-manager disabling automount because most of its users will use gnome+nautilus 3. With a "nautilus" USE flag, people (like me) that uses gnome+nautilus will tend to enable it globally (for enabling nautilus support for file-roller, seahorse, gnome-mount...). This would also build gnome-volume-manager without automount support (better for usage with nautilus) Other people who use pcman or thunar (for example), will tend to disable "nautilus" USE flag globally, getting gnome-volume-manager merged with automount support (expected behavior for these users) Thanks a lot for opening this bug also :-) Upgrade guide updated in CVS. @Pacho, from the looks of it, g-v-m is on its way out anyway. Let's keep things simple for now, we can always revisit later. Besides, it's only a useflag :) Thanks (In reply to comment #2) > Upgrade guide updated in CVS. > > @Pacho, from the looks of it, g-v-m is on its way out anyway. Let's keep things > simple for now, we can always revisit later. Besides, it's only a useflag :) > > Thanks > OK, thanks for explanation |