> [Kazuya]
> > I heard next code freeze is on next Sunday(20 Feb.). Could you
> > postpone the code freeze, and include NEC backend in the next
> > release. I will test backend in 27, Feb.
>
> I do not think a new backend is not enough to postpone the code
> freeze. We will release SANE versions after 1.0.2 as well, and
> backends missing in the next release should be included in a later
> version.
Ok, I have many times to test NEC backend.
> If the nec backend does not make it into the first release, we will
> include a .desc file with information on where to find the backend.
> Does it have a home page or a FTP distribution site?
>
Thanks, but it is not available.
> > I don't have SANE CVS write access. Plaese add NEC backend CVS tree.
>
> I test compiled the backend with the current CVS version on my Linux
> box. It gave lots of warnings. You should test your backend with the
> current CVS snapshot to have a look at the problems.
>
I'll test it
> Did you make sure 'scanimage -T' works? Check backend/GUIDE to make
> sure you remembered everything. :-)
I check NEC backend just same as SHARP backend.
> If you want CVS write access, let me know.
>
I will e-mail to you.
Kazuya
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Fri Feb 18 2000 - 04:08:27 PST