See below…

Gregory Casamento
GNUstep Lead Developer / Black Lotus, Principal Consultant
http://www.gnustep.org - http://heronsperch.blogspot.com
https://www.patreon.com/bePatron?u=352392 - Become a Patron
https://www.openhub.net/languages/objective_c
https://www.gofundme.com/f/cacao-linux-a-gnustep-reference-implementation


On Thu, Jul 24, 2025 at 04:28 Riccardo Mottola <[email protected]>
wrote:

> Gregory Casamento wrote:
> >
> > Unfortunately this can’t really happen. All of the apps
> > In the GitHub repository are assigned to the FSF. Gap contains work
> > that isn’t assigned or has a license different from the gpl. So it
> > would need to have a separate identity.
>
> Theoretically we could partially unbundle GAP and put separate projects
> here and there, e.g. things in the gnustep-nonfsf project.
> I don't think it is worth the effort, the loss of history, but it could
> be done.


I agree. I think things should stay as they are for now. I still can’t seem
to commit to Savannah though I think that is a certificate issue.

All apps and libraries I work on are LGPL/GPL - although Terminal has
> the infamous "V2 only" version.


I believe it carries this restriction because of the Linux console code it
has incorporated.  I would have liked to have ported some of the apps from
OPENSTEP to work as a terminal as those were more vt100/ vt200 compliant.

If GAP can't stay in gnustep project, it cannot stay probably also with
> the current read/write repository copy we have now, following the same
> logic.


Indeed.  I only put it into the GNUStep repo for convenience but it
shouldn’t be there for a number of reasons.  I am going to use this weekend
to get any changes that are in it back into Savannah.  At some point though
I really would like to consider moving it to a git based repo, not
necessarily github.

Riccardo
>
Yours, GC

Reply via email to