On Thu, Jun 16, 2005 at 02:05:40PM +0200, Florian Weimer wrote:
> * Drew Scott Daniels:
>
> > I think the first objection that I have is that there doesn't seem to be
> > source code to the Sun Studio 10 compiler (I may be wrong though)
>
> I would be really surprised if Sun released their compil
Glenn Maynard wrote:
On Wed, Jun 15, 2005 at 09:44:55PM -0700, Sean Kellogg wrote:
Given that we are all concerned about copyrights and having proof that the
code is free and not ripped off from SCO or whoever, identification seems to
be a worthy goal of free software, which must be balanc
On 16 Jun 2005 10:44:44 GMT, MJ Ray <[EMAIL PROTECTED]> wrote:
> Dariush Pietrzak <[EMAIL PROTECTED]> wrote:
> > > with a package where upstream are untrustworthy lying bastards.
> > It's sad to see that discussion is returning to those levels, oh well..
>
> It's expected. See http://people.debian
On Thu, Jun 16, 2005 at 09:15:06AM -0700, Sean Kellogg wrote:
> But the two have substantially different meenings... like, seriously
> substantial. "Use" is not a well defined term in the Copyright statute and
> control of "use" is generally accepted to be beyond the exclusive rights
> granted
On Tue, 31 May 2005 02:35:36 -0400 Maykel Moya wrote:
> As much of you probably know. Cuba is know giving the very first steps
> toward Software Libre inclusion in our society and in the
> infrastructure of the goverment.
Mmmh, this is good news! :)
>
> I'm a member of LiHab, the Havana's LUG,
Arnoud Engelfriet wrote:
Usually the advice is to write your own code based on descriptive
information about the protocol, without looking at the original
implementation. In other words, use the RFC, not the code.
This avoids accusations about nonliteral copying.
Arnoud
Too bad it's a closed
M?ns Rullg?rd wrote:
> Mike <[EMAIL PROTECTED]> writes:
> > If I were to study GPL'ed source in order to understand a protocol
> > that it implements, would I need to and if so how would I cite this in
> > any program I create which uses any knowledge gained?
>
> Stating where you obtained the inf
Mike <[EMAIL PROTECTED]> writes:
> Hello all,
>
> If I were to study GPL'ed source in order to understand a protocol
> that it implements, would I need to and if so how would I cite this in
> any program I create which uses any knowledge gained?
Stating where you obtained the information is alway
Hello all,
If I were to study GPL'ed source in order to understand a protocol that
it implements, would I need to and if so how would I cite this in any
program I create which uses any knowledge gained?
Michael Spang
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscri
On Wed, Jun 15, 2005 at 03:22:18PM +0200, José Luis Tallón wrote:
> This was done so as to avoid name conflicts. I was advised to use the
> "bacula-" namespace to disambiguate naming. As long as it is documented
> in README.Debian, this shouldn't be that much of a problem?
I only read the statemen
On Wednesday 15 June 2005 10:24 pm, Glenn Maynard wrote:
> On Wed, Jun 15, 2005 at 09:44:55PM -0700, Sean Kellogg wrote:
> > > That said, it's usually a bit of a leap to call "discrimination" on a
> > > license clause, since on one hand, there's usually some underlying
> > > freedom that the person
On Thu, Jun 16, 2005 at 01:24:55AM -0400, Glenn Maynard wrote:
> I find it somewhat curious that people throw around the word "compromise"
> in the context of the software freedoms as if it's actually desirable--"we
> should compromise, give up our principles and our freedoms in order to
> have mor
* Drew Scott Daniels:
> I think the first objection that I have is that there doesn't seem to be
> source code to the Sun Studio 10 compiler (I may be wrong though)
I would be really surprised if Sun released their compilers together
with OpenSolaris. Sun's compilers haven't been part of Solaris
Dariush Pietrzak <[EMAIL PROTECTED]> wrote:
> > with a package where upstream are untrustworthy lying bastards.
> It's sad to see that discussion is returning to those levels, oh well..
It's expected. See http://people.debian.org/~mjr/mplayer.html#difficult
--
To UNSUBSCRIBE, email to [EMAIL PR
14 matches
Mail list logo