I have successfully emerged dev-python/imaging 1.1.5 on ~ppc-macos The tutorial from the homepage runs fine. I have not checked USE="-X -scanner" because this is not really relevant for OSX :)
Works with +X, scanner fails because of an unkeyworded dep. Scanner can be use.masked in the profile. Suggestions?
Is it possible to keyword the scanner dep? Or is it useless on OSX? If so, mask the keyword (if not global), and feel free to keyword ~ppc-macos.
> Is it possible to keyword the scanner dep? Or is it useless on OSX? If so, > mask the keyword (if not global), and feel free to keyword ~ppc-macos. Uses scanner something like media-gfc/sane-frontends? If yes, perhaps this would be interesting to port. Scanner support on Mac seems to be rather spotty, because there exist no official API (TWAIN is Carbon only, AFAIK)
Interesting as it may be, I don't own a scanner with which to test it. Any volunteers?
> Interesting as it may be, I don't own a scanner with which to test it. Any > volunteers? I have a Canon Lide 35 USB, which according to the SANE documentation is supported "good". So I would give it a try. IMHO this should include making media-gfx/xsane, media-gfx/sane-frontends and media-gfx/sane-backends useable on ppc-macos. AFAIK there existed no native SANE frontend for MacOSX (eg http://www.softlow.com/mac-os-x/drivers/printers/free/sane-scanner-frontend.html), but it somehow disappeared off the net. Then there is the TWAIN-SANE interface project at http://www.ellert.se/twain-sane/, which perhaps could be interesting.
> > Interesting as it may be, I don't own a scanner with which to test it. Any > > volunteers? > I have a Canon Lide 35 USB, which according to the SANE documentation is > supported "good". > So I would give it a try. I have tried to keyword media-gfx/sane-backends, which in turn need dev-libs/libusb-0.1.12 Emerging libusb fails with ###################################### ***** automake ***** configure.in:81: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER' configure.in: installing `./mkinstalldirs' configure.in:31: require version 1.7.6, but have 1.6.3 ###################################### Looks like progressive would be needed to make this run, something which I don't intend to do. Dirk
Success may yet be had using a prefixed install. Not much else we can do for / installs, however, except maybe patch the script to accept a different version of automake and see what happens.
1.1.6 is in prefix
