Re: [sane-devel] Getting Alpine Linux sane-backends builds compiler warning free

[Valery Kartel]

Hi,

libieee1284 is accepted, so I push a asne-backends PR with improvements
https://github.com/alpinelinux/aports/pull/2001

2017-07-25 12:24 GMT+03:00 Valery Kartel :

> Hi, Olaf
>
> I pushed a PR for libieee1284, so waiting for accept it.
> https://github.com/alpinelinux/aports/pull/1982
>
>
> And now I playing with sane-backends building with libpng, libieee1284 and
> linux-headers as you mentioned.
>
> There are some new backends enabled now:
> canon_pp
> hpsj5s
> mustek_pp
> v4l
>
> > I also see that you list the license as GPL in the APKBUILD file.
> Yes I set GPL as a license for this package and all its subpackages. But I
> saw its not so simple with some backends licensing.
>
> Can you provide me some idea or some list how to describe licensing right
> way for not-only-gpl parts?
>
> Thanks for advise
>
> Valery.
>
> 2017-07-22 15:52 GMT+03:00 Olaf Meeuwissen :
>
>> Hi Valery,
>>
>> I'm one of the SANE developers and am trying to get rid of all compiler
>> warnings on a select subset of build environments.  Alpine Linux is one
>> of them and its parallel port IO support is giving me a bit of trouble.
>> Hope you can help me out a bit.
>>
>> I don't see any libieee1284 packages for 3.6.  Is there any activity to
>> add libieee1284?  It would enable support for a few more backends.
>>
>> A few backends also provide parallel port IO support if certain Linux
>> kernel headers are present.  Looking at the `makedepends` list in the
>> sane package's APKBUILD file, I don't see kernel-headers listed.  Can
>> I assume that the Alpine package build environment makes sure that is
>> present?  If not, you may want to add it.  It would make at least the
>> umax_pp backend do something more useful.  Without that package, it
>> compiles but essentially just no-ops just about all the I/O after
>> spitting out a warning, IIUC.
>>
>> My builds have so far not included the kernel-headers package in the
>> list of packages to be installed but I'm leaning towards adding it.  It
>> would solve a major compiler warning headache for me ;-)
>>
>> If Alpine Linux' default build environment always includes it, I feel
>> more justified to "take the easy way out".
>>
>> You can find my build environment setup[1] as well as build logs[2] (the
>> middle stage, first on the drop-down list) over at GitLab.com.
>>
>>  [1]: https://gitlab.com/sane-project/ci-envs/blob/master/alpine-
>> 3.6-musl.df
>>  [2]: https://gitlab.com/sane-project/backends/pipelines
>>
>> Somewhat off-topic, but ...
>>
>> I also see that you list the license as GPL in the APKBUILD file.  Is
>> that for that file only or does that apply to the binary packages?
>> If the latter, it's not correct and really should be fixed.
>>
>> BTW, love the fact that you provide a package per backend!  Wishing
>> other distributions would do the same.
>>
>> Thanks for any feedback in advance,
>> --
>> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>>  Support Free Softwarehttps://my.fsf.org/donate
>>  Join the Free Software Foundation  https://my.fsf.org/join
>>
>
>
-- 
sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org

Re: [sane-devel] Getting Alpine Linux sane-backends builds compiler warning free

[Olaf Meeuwissen]

Hi Valery,

Valery Kartel writes:

> Hi, Olaf
>
> I pushed a PR for libieee1284, so waiting for accept it.
> https://github.com/alpinelinux/aports/pull/1982

I noticed that was accepted.

> And now I playing with sane-backends building with libpng, libieee1284 and
> linux-headers as you mentioned.

As for the CI builds, I think I'll stick to using linux-headers only so
I have a bit more diversity in the way sane-backends gets build.

> There are some new backends enabled now:
> canon_pp
> hpsj5s
> mustek_pp
> v4l
>
>> I also see that you list the license as GPL in the APKBUILD file.
> Yes I set GPL as a license for this package and all its subpackages. But I
> saw its not so simple with some backends licensing.

Indeed.

> Can you provide me some idea or some list how to describe licensing right
> way for not-only-gpl parts?

For starters, I would use the LICENSE file as a guide.

So the frontends are GPL-2.0+ and the API spec is public domain.  As for
the backends, *most* are GPL-2.0+ with exception.  The ones that are not
are, IIRC, GPL-2.0+.  BTW, I'm not sure whether the exception is exactly
the same for all backends.

A long while back I actually analysed the situation (at the office) but
I don't have access to the results anymore (assuming they still exist).
What might be one way of recourse is the debian/copyright file (from the
Debian/Devuan/Ubuntu packages).  These contain a machine processable
"bill of rights" and are normally quite carefully vetted (at least the
first time around).

It's a bit old (1.0.24!), but I've attached the one that came with my
Devuan libsane package for reference.

# Maybe I should insert SPDX[1] compliant license tags in all files and
# add a little script that can extract them ...
#
# [1]: https://spdx.org/

> Thanks for advise

You're welcome.

>> My builds have so far not included the kernel-headers package in the
>> list of packages to be installed but I'm leaning towards adding it.  It
>> would solve a major compiler warning headache for me ;-)
>>
>> If Alpine Linux' default build environment always includes it, I feel
>> more justified to "take the easy way out".

FTR, I did take the easy way out (but may want to look at disabling the
umax_pp backend if it's just going to no-op).

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: sane-backends
Upstream-Contact: 
Source: ftp://ftp.sane-project.org/pub/sane/

Files: *
Copyright: 1997-2014 Andreas Beck 
   1997-2014 David Mosberger
License: GPL-2+ with sane exception

Files: debian/*
Copyright: 1997-2002 Kevin Dalley 
   2002-2011 Julien BLACHE 
   2002-2006 Aurélien Jarno 
   2013  Mark Buda 
   2014-2016 Jörg Frings-Fürst 
License: GPL-2+ with sane exception

Files: backend/abaton.*
Copyright: 1998-1998 David Huggins-Daines
License: GPL-2+ with sane exception

Files: backend/agfafocus.*
Copyright: 1997  Ingo Schneider
   1998  Karl Anders Øygard
License: GPL-2+

Files: backend/apple.*
Copyright: 1998  Milon Firikis
License: GPL-2+ with sane exception

Files: backend/artec.*
   backend/qcam.*
   backend/dll.*
   include/sane/sanei_scsi.h
   include/sane/sanei_wire.h
   sanei/sanei_DomainOS.c
   sanei/sanei_codec_ascii.c
   sanei/sanei_codec_bin.c
   sanei/sanei_config2.c
   sanei/sanei_net.c
   sanei/sanei_wire.c
Copyright: 1996-1997 David Mosberger-Tang
License: GPL-2+ with sane exception

Files: backend/artec_eplus48u.*
Copyright: 2002  Michael Herder 
License: GPL-2+ with sane exception

Files: backend/as6e.*
Copyright: 2000  Eugene S. Weiss
License: GPL-2+ with sane exception

Files: backend/avision.*
Copyright: 1999-2007 Rene Rebe 
   1999-2001 Meino Christian Cramer 
   2002  Jose Paulo Moitinho de Almeida 
   2010-2011 Mike Kelly 
License: GPL-2+ with sane exception

Files: backend/bh.*
Copyright: 1999-2000 Tom Martone
License: GPL-2+ with sane exception

Files: backend/canon-scsi.c
  backend/canon.*
Copyright: 1997  BYTEC GmbH Germany
License: GPL-2+ with sane exception

Files: backend/canon630u.c
Copyright: 2002  Nathan Rutman  
   2001  Marcio Luis Teixeira
   1996-1997 Andreas Beck
   2000-2001 Michael Herder 
   2001  Henning Meier-Geinitz 
License: GPL-2+ with sane exception

Files: backend/canon_dr.*
 

Re: [sane-devel] Getting Alpine Linux sane-backends builds compiler warning free

[Valery Kartel]

Hi, Olaf

I pushed a PR for libieee1284, so waiting for accept it.
https://github.com/alpinelinux/aports/pull/1982


And now I playing with sane-backends building with libpng, libieee1284 and
linux-headers as you mentioned.

There are some new backends enabled now:
canon_pp
hpsj5s
mustek_pp
v4l

> I also see that you list the license as GPL in the APKBUILD file.
Yes I set GPL as a license for this package and all its subpackages. But I
saw its not so simple with some backends licensing.

Can you provide me some idea or some list how to describe licensing right
way for not-only-gpl parts?

Thanks for advise

Valery.

2017-07-22 15:52 GMT+03:00 Olaf Meeuwissen :

> Hi Valery,
>
> I'm one of the SANE developers and am trying to get rid of all compiler
> warnings on a select subset of build environments.  Alpine Linux is one
> of them and its parallel port IO support is giving me a bit of trouble.
> Hope you can help me out a bit.
>
> I don't see any libieee1284 packages for 3.6.  Is there any activity to
> add libieee1284?  It would enable support for a few more backends.
>
> A few backends also provide parallel port IO support if certain Linux
> kernel headers are present.  Looking at the `makedepends` list in the
> sane package's APKBUILD file, I don't see kernel-headers listed.  Can
> I assume that the Alpine package build environment makes sure that is
> present?  If not, you may want to add it.  It would make at least the
> umax_pp backend do something more useful.  Without that package, it
> compiles but essentially just no-ops just about all the I/O after
> spitting out a warning, IIUC.
>
> My builds have so far not included the kernel-headers package in the
> list of packages to be installed but I'm leaning towards adding it.  It
> would solve a major compiler warning headache for me ;-)
>
> If Alpine Linux' default build environment always includes it, I feel
> more justified to "take the easy way out".
>
> You can find my build environment setup[1] as well as build logs[2] (the
> middle stage, first on the drop-down list) over at GitLab.com.
>
>  [1]: https://gitlab.com/sane-project/ci-envs/blob/master/
> alpine-3.6-musl.df
>  [2]: https://gitlab.com/sane-project/backends/pipelines
>
> Somewhat off-topic, but ...
>
> I also see that you list the license as GPL in the APKBUILD file.  Is
> that for that file only or does that apply to the binary packages?
> If the latter, it's not correct and really should be fixed.
>
> BTW, love the fact that you provide a package per backend!  Wishing
> other distributions would do the same.
>
> Thanks for any feedback in advance,
> --
> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>  Support Free Softwarehttps://my.fsf.org/donate
>  Join the Free Software Foundation  https://my.fsf.org/join
>
-- 
sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org

[sane-devel] Getting Alpine Linux sane-backends builds compiler warning free

[Olaf Meeuwissen]

Hi Valery,

I'm one of the SANE developers and am trying to get rid of all compiler
warnings on a select subset of build environments.  Alpine Linux is one
of them and its parallel port IO support is giving me a bit of trouble.
Hope you can help me out a bit.

I don't see any libieee1284 packages for 3.6.  Is there any activity to
add libieee1284?  It would enable support for a few more backends.

A few backends also provide parallel port IO support if certain Linux
kernel headers are present.  Looking at the `makedepends` list in the
sane package's APKBUILD file, I don't see kernel-headers listed.  Can
I assume that the Alpine package build environment makes sure that is
present?  If not, you may want to add it.  It would make at least the
umax_pp backend do something more useful.  Without that package, it
compiles but essentially just no-ops just about all the I/O after
spitting out a warning, IIUC.

My builds have so far not included the kernel-headers package in the
list of packages to be installed but I'm leaning towards adding it.  It
would solve a major compiler warning headache for me ;-)

If Alpine Linux' default build environment always includes it, I feel
more justified to "take the easy way out".

You can find my build environment setup[1] as well as build logs[2] (the
middle stage, first on the drop-down list) over at GitLab.com.

 [1]: https://gitlab.com/sane-project/ci-envs/blob/master/alpine-3.6-musl.df
 [2]: https://gitlab.com/sane-project/backends/pipelines

Somewhat off-topic, but ...

I also see that you list the license as GPL in the APKBUILD file.  Is
that for that file only or does that apply to the binary packages?
If the latter, it's not correct and really should be fixed.

BTW, love the fact that you provide a package per backend!  Wishing
other distributions would do the same.

Thanks for any feedback in advance,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org