Re: [sdcc-devel] sdcc libraries license change, sdcc 3.0 release

[Borut R. <bor...@si...>]

Hi Philipp,

my opinion is that we should make the release, even that everything is 
not in the shape we would like it to be (actually it never is). Even if 
we postpone the release, there is no guarantee if/when the remaining 
issues will be fixed.

About "change sdcc libraries license to GPL+LE": the most critical are 
the functions written by Jean-Louis Vern, which are "core" functions 
used on all targets. I tried to reach him several times, but I always 
received the undeliverable e-mail message. I asked Google, but didn't 
find any useful info. I even asked Sandeep if he knowns how to contact 
Jean-Louis Vern, but he don't have any additional contact info.

So I gave up hope :-( . I propose to leave it as it is for the 3.0.0 
release. After that we have to consider to rewrite the missing functions...

The other missing items are platform specific and I still hope that we 
will get the permission to change the license at least for some of them.

I like the #warning idea. I propose to do it in the way that it is shown 
only in case the (for example) CLOSED_SOURCE symbol is defined.

Borut


On 09/12/2010 06:35 PM, Philipp Klaus Krause wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> What shall we do about the 6 open (and 4 qusidone) items at
> http://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.0.0%20Release
> ?
>
> IMO #2870755 is the most important, since it seems to be the main
> disadvantage sdcc has over other compilers often resulting in
> sdcc-generated code being more than twice the size than what others can
> do. Nevertheless it is the one most likely to break something, thus I
> suggest to postpone it.
>
> #1196045 only affects hc08, so postponing would probably be ok.
>
> #1477149 and #1406219, #1505956 could be more complicated to fix, and
> thus to avoid regressions, could be postphoned.
>
> How about #2942343?
>
> The 3 quasidone items related to bool probably should probably be
> completed for at least hc08, pic14 and pic16 since those three need it
> the most, currently not having any bool at all.
>
> #2932327 is the quasidone library license conversion. Looking at
> https://sourceforge.net/apps/trac/sdcc/wiki/Files%20and%20Licenses it
> seems most remeining problematically licensed files are port-specific,
> which IMO is tolerable for sdcc 3.0. However there are three that look
> like they could taint multiple ports:  ./lib/_decdptr.c,
> ./lib/_divuint.c,  ./lib/_divulong.c, all by Jean-Louis Vern? Do these
> really affect multiple ports? If yes, something should be done about it,
> even if that means delaying the sdcc 3.0.0 release.
> Furthermore IMO users should be warned about problematically licensed
> files. A #warning per file should do.
>
> Philipp
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkyNATwACgkQbtUV+xsoLpoyjQCg7PgwROC0km8hPwjCpjjoSV9Z
> joAAni6QkuVu3suaPMCsrSrm/mc4kId0
> =OvvF
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> sdcc-devel mailing list
> sdc...@li...
> https://lists.sourceforge.net/lists/listinfo/sdcc-devel
>
>