comment on

Right now, you cannot use GCC code without linking to it statically.

The GCC group has asked everyone not to dynamically link it.

You cannot use it under any other license at all.

So I am trying to license the output of it, to put in an XML gateway, and to protect that gateway from anyone else using it other than GPLed code, just like is provisioned under the GPL.

My point is that with the RGPL you can use shared libs and XML and all these funky tools, even GPLEd perl scripts, if you use the compiler via an RGPL interface.

Right now there is NO way to do any of that forseen by the gcc team,and the try an squash anyone who tries.

The introspector is a PATCH to the gcc, not a branch.

I would not distribute that patch, only the data output from it via an RGPL licence via a web service, only to GPLed projects.

Have I explained myself?

Mike

In reply to Re: (FoxUni) Re(3): OT: A Modest Proposal for a GNU infrastructure license RGPL by mdupont
in thread OT: A Modest Proposal for a GNU infrastructure license RGPL by mdupont

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks