I have committed this patch, and can confirm that
sane-frontends-1.0.15git builds against released sane-backends.
allan
On Mon, May 10, 2010 at 9:37 PM, m. allan noah wrote:
> On Sun, May 9, 2010 at 4:59 PM, Ilm?rs Poik?ns wrote:
>> Hi,
>>
>>> At this point, I dont think we want to enshrine any
On Sun, May 9, 2010 at 4:59 PM, Ilm?rs Poik?ns wrote:
> Hi,
>
>> At this point, I dont think we want to enshrine anything as being part
>> of SANE2.
>
> I didn't ment exactly SANE2, just next version, if there will be any.
>
> Both #ifdef 0 in sane.h comments out code because "following are for
>
Hi,
> At this point, I dont think we want to enshrine anything as being part
> of SANE2.
I didn't ment exactly SANE2, just next version, if there will be any.
Both #ifdef 0 in sane.h comments out code because "following are for
later sane version, older frontends wont support" and "these are to
"m. allan noah" wrote:
Hi,
> At this point, I dont think we want to enshrine anything as being part
> of SANE2. The proper fix is to either remove that code, or stop
> shipping sane-frontends altogether. Frankly, scanimage should be made
> to do everything scanadf can do, and the rest of the fro
At this point, I dont think we want to enshrine anything as being part
of SANE2. The proper fix is to either remove that code, or stop
shipping sane-frontends altogether. Frankly, scanimage should be made
to do everything scanadf can do, and the rest of the frontends are not
really maintained.
all
Hi,
As I understood code in sane.h commented out with "#if 0" is for next
version SANE. Isn't it better to have one switch like SANE_API_2 in
sane.h instead of two "#if 0"? See patch to current git master in
attachment (previous patch I sent was other way round). Then there is
flexibility to switc
