[sane-devel] Best way to release a development version of a new backend for testing?

m. allan noah kitno455 at gmail.com
Tue Dec 20 01:26:41 UTC 2011

Assuming you use sanei_* libraries, you best bet is to initially
distribute a patch against the latest release of sane-backends. Once
you have some feedback/testing, you could work that patch into shape
against the current development version, and submit it for inclusion
with the rest of sane-backends. It has been our experience that
backends which live out of tree die off, and backends which are
designed to build standalone have lots of cruft in them when they get
added to sane.


On Mon, Dec 19, 2011 at 4:42 PM, Paul Newall <p.newalls at ntlworld.com> wrote:
> Any ideas how I should get people to test my new backend for scanning on
> Kodak Aio printers?
> I've got it working, added to the sane backends on my PC.
> Should I try to create a make file that will add it to a user's existing
> installation? Maybe someone has a template I could use to do that?
> Or should I be trying to get it added to sane backends as soon as possible?
> - I hesitate to do that because I guess it will need quite a bit of tidying
> up before it's really ready for that.
> Paul Newall
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request at lists.alioth.debian.org

"The truth is an offense, but not a sin"

More information about the sane-devel mailing list