---- Reported by jim@yorba.org 2010-10-27 13:28:00 -0700 ----

Original Redmine bug id: 2738
Original URL: http://redmine.yorba.org/issues/2738
Searchable id: yorba-bug-2738
Original author: Jim Nelson
Original description:

Shotwell today cannot build or run on FreeBSD because gudev (i.e. udev) is a
Linuxism. To support FreeBSD out-of-the-box, camera support needs to be
disabled (#2737) or we need to allow some build-time mechanism to swap in
FreeBSD's device notification system.



---- Additional Comments From shotwell-maint@gnome.bugs 2011-04-13 11:27:00 -0700 ----

### History

####

#1

Updated by Landry Breuil over 2 years ago

Adding my voice here.. atm, OpenBSD's device notification system only allows
for shell execution when a device is inserted/removed, which won't be easy to
integrate in shotwell as-is.

I have some dreams to have a udev-compatible userland api someday, but it
won't be easy.

####

#2

Updated by Jim Nelson over 2 years ago

It may be still be possible with few changes to Shotwell. Today Shotwell can
be launched with a command-line URI pointing to a mounted camera device. This
could be altered to also allow an atm specifier that tells Shotwell to re-scan
for cameras. This would work even if Shotwell was already running via
libunique.

Could you post a link to more information about atm for future implementors?

####

#3

Updated by Landry Breuil over 2 years ago

Oh, by 'atm' i meant “at the moment†:)

OpenBSD uses hotplugd, cf [http://www.openbsd.org/cgi-
bin/man.cgi?query=hotplugd&sektion=8](http://www.openbsd.org/cgi-
bin/man.cgi?query=hotplugd&sektion=8)

It executes a shell script upon device insertion/removal, where you have to
write your own glue to detect if the device is a camera, a usb key, etc, and
then you mount the device as a regular disk device.

I think that's we want to tell shotwell to scan the mountpoint dir instead of
a disk device (ie shotwell --scan /mnt/camera)

For cameras not seen as regular disk devices (ie the ones using PTP protocol),
one could use gphoto2 -P to fetch images to a temporary dir, and tell shotwell
to scan that dir ? Or does shotwell plan to integrate gphoto2 support ?

As of now with shotwell 0.9.1 (with gudev disabled), i don't have a command-
line option to give an URI pointing to a mounted device..

####

#4

Updated by Jim Nelson over 2 years ago

That's funny. I thought atm was FreeBSD's version of udev. When I searched for
it I kept finding pages on how to use Asynchronous Transfer Mode hardware with
BSD. That didn't seem right, of course.

Shotwell has integrated gphoto2 support today. The only thing we use udev for
are notifications that a device has been attached or removed from the system.
Shotwell then initiates a camera scan via gphoto2. That's why I feel my
proposal above will work -- all Shotwell needs is a notification of some kind
to scan for new cameras and gphoto2 will do the rest.

This ticket is also related: #2498



--- Bug imported by chaz@yorba.org 2013-11-25 21:47 UTC  ---

This bug was previously known as _bug_ 2738 at http://redmine.yorba.org/show_bug.cgi?id=2738

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 set on an open status.
   Dropping resolution