library import/monitoring should follow symbolic links
Submitted by Adam Dingle
Assigned to Jim Nelson
Link to original bug (#716673)
Description
---- Reported by adam@yorba.org 2010-07-20 17:44:00 -0700 ----
Original Redmine bug id: 2307
Original URL: http://redmine.yorba.org/issues/2307
Searchable id: yorba-bug-2307
Original author: Adam Dingle
Original description:
library import/monitoring should follow symbolic links
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:40:00 -0700 ----
History
Comment 1
Updated by Adam Dingle about 3 years ago
- Status changed from Open to 5
- Resolution set to duplicate
- % Done set to 100
This is now part of#2478.
Comment 2
Updated by Jim Nelson about 3 years ago
- Status changed from 5 to 4
-
Resolution deleted (
<strike>
_duplicate_</strike>
) - % Done changed from 100 to 0
Re-opening because the patch for #2478 (closed) was large and hairy enough that I didn't want to deal with symbolic links.
Comment 3
Updated by Adam Dingle about 3 years ago
- Subject changed from library monitoring should follow symbolic links to library import/monitoring should follow symbolic links
Comment 4
Updated by Adam Dingle about 3 years ago
-
Priority deleted (
<strike>
_High_</strike>
)
Comment 5
Updated by Adam Dingle almost 3 years ago
-
Priority deleted (
<strike>
__</strike>
)
It appears that auto-importing is following symbolic links. I created a symbolic link from my Pictures directory to ~/Desktop/test. When I started Shotwell with an empty library, it discovered a photo in that directory.
Not sure whether this is intentional. Upping to release for discussion.
Comment 6
Updated by Adam Dingle almost 3 years ago
We discussed. Symbolic link support is actually almost complete – we now only need to handle the case in which a symbolic link appears in the library directory on the fly. We now plan to implement this for 0.8.
Comment 7
Updated by Adam Dingle almost 3 years ago
- Status changed from 4 to Review
- Assignee changed from Anonymous to Jim Nelson
Comment 8
Updated by Jim Nelson almost 3 years ago
- Status changed from Review to 5
- Resolution set to fixed
- % Done changed from 0 to 100
r2484
Comment 9
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:46 UTC ---
This bug was previously known as bug 2307 at http://redmine.yorba.org/show_bug.cgi?id=2307
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED FIXED