Thread from comp.lang.tcl (3 replies)

Hi together,

i see on the wiki one comment about the unknown license of tclexecomp. In
sum, tclexecomp is only a collection of scripts, which build TclTk and the
included modules from source and together with some tcl code i got the
binaries for the different operation systems.

As of V2.0.0, there was an complete code rewrite, so it isn't based on
freewrap anymore, only the ideas of building such a batterie included
TclTk distribution has been used.

I developed this tool as it is very useful for my own TclTk projects and
as i am no coder (besides TclTk), that's my way to give something back to
the great TclTk community. Maybe it's useful for other's too.

So, what license to take ?
From my side (the scripts i wrote), everyone can use and modify it
like he want without any warranty from my side. I will update the sources
on sourgeforge soon, so everyone can even do that.

Do i have to include a license text file, where all the licenses of all
included modules, included the TclTk license are listed ?
Or is some small license text like in Ashok's Magicsplat
(https://www.magicsplat.com/tcl-installer/#license) enough ?

I'm no lawyer, so I tried to play it safe in the magicsplat 
distribution. There is a top level license that refers to the individual 
licenses in the licenses subdirectory.

You may perhaps do similar and link to the full list of licenses 
somewhere on your site.

As to whether that is adequate, who knows?

/Ashok

On 7/23/2024 3:16 AM, Michael Niehren wrote:
> Hi together,
> 
> i see on the wiki one comment about the unknown license of tclexecomp. In
> sum, tclexecomp is only a collection of scripts, which build TclTk and the
> included modules from source and together with some tcl code i got the
> binaries for the different operation systems.
> 
> As of V2.0.0, there was an complete code rewrite, so it isn't based on
> freewrap anymore, only the ideas of building such a batterie included
> TclTk distribution has been used.
> 
> I developed this tool as it is very useful for my own TclTk projects and
> as i am no coder (besides TclTk), that's my way to give something back to
> the great TclTk community. Maybe it's useful for other's too.
> 
> So, what license to take ?
>  From my side (the scripts i wrote), everyone can use and modify it
> like he want without any warranty from my side. I will update the sources
> on sourgeforge soon, so everyone can even do that.
> 
> Do i have to include a license text file, where all the licenses of all
> included modules, included the TclTk license are listed ?
> Or is some small license text like in Ashok's Magicsplat
> (https://www.magicsplat.com/tcl-installer/#license) enough ?
> 
> 

On 7/22/24 23:46, Michael Niehren wrote:
> 
> Do i have to include a license text file, where all the licenses of all
> included modules, included the TclTk license are listed ?
> Or is some small license text like in Ashok's Magicsplat
> (https://www.magicsplat.com/tcl-installer/#license) enough ?
> 

Maybe this is helpful:

https://debricked.com/blog/category/license-compliance/
https://www.zdnet.com/article/howto-pick-an-open-source-license-part-1/
https://opensource.org/license

Regards,
Erik.
--

> 

-- 
elns@       nl | Merge the left part of these two lines into one,
      xs4all.   | respecting a character's position in a line.

Hi Ashok,

so i will do it in the same way like you,

thanks,
  Michael

Ashok wrote:
> I'm no lawyer, so I tried to play it safe in the magicsplat
> distribution. There is a top level license that refers to the individual
> licenses in the licenses subdirectory.
> 
> You may perhaps do similar and link to the full list of licenses
> somewhere on your site.
> 
> As to whether that is adequate, who knows?
> 
> /Ashok
> 
> On 7/23/2024 3:16 AM, Michael Niehren wrote:
>> Hi together,
>> 
>> i see on the wiki one comment about the unknown license of tclexecomp. In
>> sum, tclexecomp is only a collection of scripts, which build TclTk and
>> the included modules from source and together with some tcl code i got
>> the binaries for the different operation systems.
>> 
>> As of V2.0.0, there was an complete code rewrite, so it isn't based on
>> freewrap anymore, only the ideas of building such a batterie included
>> TclTk distribution has been used.
>> 
>> I developed this tool as it is very useful for my own TclTk projects and
>> as i am no coder (besides TclTk), that's my way to give something back to
>> the great TclTk community. Maybe it's useful for other's too.
>> 
>> So, what license to take ?
>>  From my side (the scripts i wrote), everyone can use and modify it
>> like he want without any warranty from my side. I will update the sources
>> on sourgeforge soon, so everyone can even do that.
>> 
>> Do i have to include a license text file, where all the licenses of all
>> included modules, included the TclTk license are listed ?
>> Or is some small license text like in Ashok's Magicsplat
>> (https://www.magicsplat.com/tcl-installer/#license) enough ?
>> 
>>