Re: [Vala] Vala and GLib license

[Jens Georg]

Yes. Obviously the two licenses are not compatible then. The only way 
out there
would be a compatibility layer that translates those runtimes into 
something

GLib can live with.


Even if that would violate licence from Sony and Microsoft? Obviously,
sharing that code with someone who already has license from them to
use their API is not a problem at all. But sharing that code with
those who don't have such license will put me into trouble with that
companies, but even if people will have those sources - they are
useless without previous agreement with Sony/Microsoft and their SDK.
That's the one of the moments that kind of preventing me to look into
Vala more seriously in view of professional game development. I never
know where it will end. The thing is - I have bunch of old code that I
may to do some refactoring - go from old C code into C++ with bunch of
own new and old bicycles or just went with Vala step by step, maybe
even ending with helping community in places where I may be useful.
But even how much I don't like C++ as the language, at least I know I
won't have any license headache later. Vala looks way better in
comparison, but the license of it's core runtime... That was the whole
point of the subject.

On Jul 11, 2016 5:25 PM, "Jens Georg"  wrote:


But If I would need to patch GLib to work on PS4 or XBONE? I doubt
that
those platforms will allow me to share usage of their internal
API. Can I
keep those patch closed and share them only with people who has
licenses
for PS4 and XONE (you aren't able to put that patch in anyway if
you are
just standard customer and user of the console and not the
developer) so
they would able to use that new code as well, but not with others,
because
that may violate license of console platforms.


No. Because you're patching (L)GPL code you would have to grant
access to the modified sources
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] Vala and GLib license

[Jens Georg]

But If I would need to patch GLib to work on PS4 or XBONE? I doubt that
those platforms will allow me to share usage of their internal API. Can 
I
keep those patch closed and share them only with people who has 
licenses
for PS4 and XONE (you aren't able to put that patch in anyway if you 
are
just standard customer and user of the console and not the developer) 
so
they would able to use that new code as well, but not with others, 
because

that may violate license of console platforms.


No. Because you're patching (L)GPL code you would have to grant access 
to the modified sources

___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] Vala and GLib license

[Aleksandr Palamar]

But If I would need to patch GLib to work on PS4 or XBONE? I doubt that
those platforms will allow me to share usage of their internal API. Can I
keep those patch closed and share them only with people who has licenses
for PS4 and XONE (you aren't able to put that patch in anyway if you are
just standard customer and user of the console and not the developer) so
they would able to use that new code as well, but not with others, because
that may violate license of console platforms.

On Mon, Jul 11, 2016 at 4:46 PM, Guillaume Poirier-Morency <
guillaumepoiriermore...@gmail.com> wrote:

> According to GNU's site, if you statically link with GLib, you have to
> at least provide users with object files (not necessarily sources) so
> that they can link against any version they like of the library under
> the LGPL.
>
> https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic
>
> For the rest, I cannot tell, but I'm pretty sure that LGPL is
> sufficiently permissive.
>
> Le lundi 11 juillet 2016 à 16:29 +0300, Aleksandr Palamar a écrit :
> > Hi, Vala-List users.
> >
> > I'm curious about GLib license (which is the core of Vala runtime),
> > mainly
> > because I'm thinking about using Vala in closed source (or zlib if
> > that
> > would be possible in future) project, which may (or not) be used on
> > different platforms including iOS (which doesn't allow dynamic
> > linkage),
> > PS4 and XBoxOne. Would it require to make application available under
> > LGPL
> > as well or I would able to kept application under any license I like
> > while
> > sharing (if target platform allows it, because I doubt about PS4 and
> > XONE)
> > changes for GLib if there was any. Just don't want to go wrong way
> > and
> > force myself to drain inside license problems in future.
> >
> > Regards, Aleksandr Palamar
> > ___
> > vala-list mailing list
> > vala-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/vala-list
> --
>
> Guillaume Poirier-Morency 
>
> Étudiant au baccalauréat en Informatique à l'Université de Montréal
> Développeur d'application web
>
> Mon blog: https://arteymix.github.io/
> Mon projet de coopérative: https://pittoresque.github.io/
> Clé PGP: B1AD6EA5
> ___
> vala-list mailing list
> vala-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/vala-list
>
>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

[Vala] Vala and GLib license

[Aleksandr Palamar]

Hi, Vala-List users.

I'm curious about GLib license (which is the core of Vala runtime), mainly
because I'm thinking about using Vala in closed source (or zlib if that
would be possible in future) project, which may (or not) be used on
different platforms including iOS (which doesn't allow dynamic linkage),
PS4 and XBoxOne. Would it require to make application available under LGPL
as well or I would able to kept application under any license I like while
sharing (if target platform allows it, because I doubt about PS4 and XONE)
changes for GLib if there was any. Just don't want to go wrong way and
force myself to drain inside license problems in future.

Regards, Aleksandr Palamar
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list