On Fri, May 8, 2009 at 11:33, Randal L. Schwartz wrote:
>> ""Chas" == "Chas Owens" writes:
>
> "Chas> Neither license prevents people from selling the software in question,
> "Chas> but both require that source be available (or made available), so
> "Chas> anyone charging an arm and a leg for
> ""Chas" == "Chas Owens" writes:
"Chas> Neither license prevents people from selling the software in question,
"Chas> but both require that source be available (or made available), so
"Chas> anyone charging an arm and a leg for it will rapidly find free
"Chas> versions being made available (
From: Steve Bertrand
> Chas. Owens wrote:
>> On Thu, May 7, 2009 at 22:04, Steve Bertrand
wrote:
>> snip
>>> I like the BSD license, and I am a BSD person, but I'm asking for
>>> feedback from the creme-de-la-creme with regards to making code
public,
>>> so that I can put something in my code to e
On Fri, May 8, 2009 at 00:51, Steve Bertrand wrote:
snip
> I wish all of my code be free, ie: I don't care if a commercial entity
> uses it for their benefit or not, I don't care if derivatives are used
> in commercial products or not, all I really care about is that my
> current code is protected
Chas. Owens wrote:
> On Thu, May 7, 2009 at 22:04, Steve Bertrand wrote:
> snip
>> I like the BSD license, and I am a BSD person, but I'm asking for
>> feedback from the creme-de-la-creme with regards to making code public,
>> so that I can put something in my code to ensure that someone else
>> d
On Thu, May 7, 2009 at 22:04, Steve Bertrand wrote:
snip
> I like the BSD license, and I am a BSD person, but I'm asking for
> feedback from the creme-de-la-creme with regards to making code public,
> so that I can put something in my code to ensure that someone else
> doesn't decide that they wan
> "Adam" == Adam Theo <[EMAIL PROTECTED]> writes:
Adam> on the matter of compiling perl: this is something i have also been
Adam> wanting to look into, for the reason of speeding up my programs,
As the FAQ entry says, Perl is already compiled by the time it hits
runtime, so there's not much
Hello, all, Adam Theo here;
i didn't catch the first half of this thread, just the posts from the
last digest.
on the matter of compiling perl: this is something i have also been
wanting to look into, for the reason of speeding up my programs, and
being able to distribute my programs to people w
On Sat, 2 Jun 2001 17:36:29 +0100, Nigel G Romeril said:
> Licensing and restriction are tied together, If I write a Perl program and
> license it to a client and he cannot easily copy or pass it on to a third
> party then I can continue to profit from my work. If the source is available
> he
At 09:37 AM 6/2/01 -0700, Randal L. Schwartz wrote:
>Yes, I think these "perl2exe" vendors are really doing the community a
>disservice. They're merely "installation bundlers", not true
>compilers (except in the sense of "compile" as "bringing together").
>The runtime of the program is not improv
make money then I should have a right to secure some of this.
-Original Message-
From: Abdulaziz Ghuloum <[EMAIL PROTECTED]>
To: Robin Lavallee (LMC) <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Date: 02 June 2001 17:12
Subject: Fw: Re: Licensing
>Hello
> "Nigel" == Nigel G Romeril <[EMAIL PROTECTED]> writes:
Nigel> I do not have any direct experience of this, but I read in
Nigel> magazine that these Perl to exe interpreters embed the perl
Nigel> into the exe as plain text. The original code can be recovered
Nigel> by opening the exe in an
Hello
It seems like you got two issues mixed up slightly. One is the licensing issue
and the other is the restriction issue. Let me elaborate:
Licensing is an agreement between the program supplier and the user regarding
the use of the program, redistribution restrictions, the freedom to modif
Hello
It seems like you got two issues mixed up slightly. One is the licensing issue
and the other is the restriction issue. Let me elaborate:
Licensing is an agreement between the program supplier and the user regarding
the use of the program, redistribution restrictions, the freedom to modif
.
-Original Message-
From: Robin Lavallee (LMC) <[EMAIL PROTECTED]>
To: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
Date: 01 June 2001 16:49
Subject: RE: Licensing
>
>> Hi people,
>>
>> Has anyone been able to conceive some kind of licencing scheme in
> Hi people,
>
> Has anyone been able to conceive some kind of licencing scheme in Perl ?
> That is, I want to deploy a Perl program that the customer will only be
> able to use for 30-60-90-30n days. This causes great problem to implement
> in
> Perl since the customer could simply comment-out
[snipped and reformatted]
Hi people,
Has anyone been able to conceive some kind of licencing scheme in Perl ?
That is, I want to deploy a Perl program that the customer will only be
able to use for 30-60-90-30n days. This causes great problem to implement in
Perl since the customer could simply
On Fri, 1 Jun 2001, Robin Lavallee (LMC) wrote:
> Has anyone been able to conceive some kind of licencing scheme in
> Perl ?
> That is, I want to deploy a Perl program that the customer will only be
> able to
> use for 30-60-90-30n days. This causes great problem to implement in Perl
> sin
18 matches
Mail list logo
