Re: Status of Privoxy for iOS (and, in time, for Android)

"Ian Silvester" <[email protected]> wrote:

> On Wed, 25 Sep 2013 13:40:18 -0400, Fabian Keil <[email protected]> wrote:
> 
> > "Ian Silvester" <[email protected]> wrote:
> >
> >> I've recently moved from an iPhone to an Android phone so do not intend  
> >> to
> >> continue development of the Privoxy for iPhone release building module
> >> (iOSPackageBuilder). Here is the current status of the project:
> >>
> > [...]
> >>
> >> I would like to add the work in progress to CVS just in case someone  
> >> else
> >> takes up the baton down the line, and even think it worth publishing the
> >> installer for download from Sourceforge (once the documentation has been
> >> updated with relevant installation instructions for iOS). Given the  
> >> status
> >> described above, what do you all feel about this?
> >
> > Putting the work in progress into CVS seems reasonable to me.
> 
> Thanks Fabian, will get onto it.
> 
> > If distributing the installer binary doesn't violate the GPLv2
> > (I didn't check), uploading it makes sense to me as well.
> 
> I'm always a bit ignorant on the licensing front, but since the installer  
> is just a zip file how might that be more of a licensing concern than,  
> say, Apple's .pkg format as used on OS X? The only binary being  
> distributed is Privoxy compiled for ARM - is that your concern? As ever,  
> apologies if I'm missing a wider issue (I often do where GPL is  
> concerned!).

The packaging format indeed shouldn't matter, but if you cross-compile
from OS X to iOS using a proprietary build environment the special
exception from § 3 GPLv2 probably doesn't apply anymore:

| The source code for a work means the preferred form of the work for
| making modifications to it.  For an executable work, complete source
| code means all the source code for all modules it contains, plus any
| associated interface definition files, plus the scripts used to
| control compilation and installation of the executable.  However, as a
| special exception, the source code distributed need not include
| anything that is normally distributed (in either source or binary
| form) with the major components (compiler, kernel, and so on) of the
| operating system on which the executable runs, unless that component
| itself accompanies the executable.

I'm not familiar enough with building binaries for iOS to decide whether
or not that's really a problem, though. If you come (or already came)
to the conclusion that it isn't, that's fine with me.

Fabian

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk

_______________________________________________
Ijbswa-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ijbswa-developers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)

iQIcBAEBCAAGBQJSTq6OAAoJEGkYIpGLojccTysP/39kOeC3Y+wHY+kS4k3E3F68
YBkl319JRVHn1w0RgNKKtPYqCnU8vBzCDGuk76KbqL3CH/v8DdbMookM4bwwoAZB
yAHSijMCmIcYMmKMDtTdU8mvzQVag+VAwqR7flLOcczyBljXa1vvt8GZ/VM+HO9i
Tl3mseJP0IgDQAzMK8a+hMB08Z6rBD/oh29fCmFUnvS4+CUiZU+BRMXd3WswyCAN
JL7i1STuZMW952kUzehNgMVdlo1AJDPCibDfk09wmEYMoCgecEruH+qZz9ZG8X7d
0mbnjOGXJpxy0GOirrh+0oB/W2miMdw8iAhQWz8vv5+talUElZ8KnHGcH5KbgO/T
b0bTqQy3v9e5fW3pgfhm/+88aTW/TwIN4FDbZrxiJk0IlKAZisMHIF8oIpAHRrhZ
oUrQMVgHpXFfaLF86Z448sR1hU5VoNjoGE7fnufcSlpE6LmiNkLrbXp4OjVYuuBN
kMML6u6oEvgyaIMOikmW8FfkvvSFngklA7J1CpE8wZZFioMYBpH/85D+oeFH4zyC
fVoSEcUB0aTf7MVfTJvm5sOue8uIss2NIFdYGMtSAYpwhq+rt+j1hUMKJvXBLbr5
AWOmJbi4AY/ONGX75QzCrM3f9UW/N5P/28ONYT78ii11uXN0WAAMNVgEA+OPCqA5
cUuazqzQSkEyW9bKgJnR
=G4Nb
-----END PGP SIGNATURE-----