Re: [PHP4BETA] moving uses of strncpy/cat to srtlcpy/cat? (fwd)
| From: | Joey | Date: | Tue, 14 Sep 1999 17:31:28 +0000 |
| Subject: | Re: [PHP4BETA] moving uses of strncpy/cat to srtlcpy/cat? (fwd) | ||
| Groups: | php.version4 | ||
| Request: | Send a blank email to php-version4+get-4442@lists.php.net to get a copy of this message | ||
They are under the BSD license... this is an excerpt from:
http://www.openbsd.org/policy.html
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
OpenBSD can exist as it does today because of the example set
by the Computer Systems Research Group at Berkeley and the
battles which they and others fought to create a relatively
un-encumbered Unix source distribution.
The ability of a freely redistributable "Berkeley" Unix to
move forward on a competitive basis with other operating
systems depends on the willingness of the various development
groups to exchange code amongst themselves and with other
projects. Understanding the legal issues surrounding copyright is
fundamental to the ability to exchange and re-distribute code,
while honoring the spirit of the copyright and concept of
attribution is fundamental to promoting the cooperation of
the people involved.
The Berkeley Copyright
The Berkeley copyright poses no restrictions on private or
commercial use of the software and imposes only simple and
uniform requirements for maintaining copyright notices in
redistributed versions and crediting the originator of the
material only in advertising.
Because the OpenBSD copyright imposes no conditions beyond
those imposed by the Berkeley copyright, OpenBSD can hope
to share the same wide distribution and applicability as
the Berkeley distributions. It follows however, that
OpenBSD can not include material which includes
copyrights which are more restrictive than the Berkeley
copyright, or must relegate this material to a secondary
status, i.e. OpenBSD as a whole is freely redistributable,
but some optional components may not be.
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
( I checked this with Theo before suggesting it to glibc... )
--Joey Smith
---------- Forwarded message ----------
Date: Tue, 14 Sep 1999 18:47:51 +0200
From: Andi Gutmans <andi@zend.com>
To: Joey <joey@samaritan.com>
Cc: PHP 4 Beta Test <php4beta@lists.php.net>
Subject: Re: [PHP4BETA] moving uses of strncpy/cat to srtlcpy/cat?
Hi,
I am very enthusiastic about using them. I think we are allowed to take the
OpenBSD strlcpy.c and strlcat.c files and use them in case configure
doesn't detect them on the OS. Check with Theo & Ulrich about the license
but it seems to me that they are completely free and that they can be used
also for commercial use.
Andi
At 10:26 AM 9/14/99 -0600, Joey wrote:
>Isn't there some way we could bundle them with PHP, and if they are not
>defined by the OS, use them? I really don't know about this stuff, I have
>just had a long back-and-forth with Theo de Raadt & Ulrich Drepper, and
>while Theo makes an excellent case, Ulrich is being stubborn (as is his
>perogative, I guess).
>
>I was also considering approaching the Apache Group a/b the same thing,
>but I am less intimidated by the PHP guys, as I feel I have gotten to know
>you all...Rasmus, maybe you could mention strlcat/cpy to the rest of the
>Apache guys?I know that Theo mentioned that they had created their own
>workaround that was somewhat similar, but I think it'd be easier to get
>glibc to support these functions if I could point at some major packages
>that were using them?
>
>this is all speculation...I am just feeling my way around in the dark
>here, but felt more comfortable approaching you guys than anyone else out
>there...I started with Ulrich, 'cz that really is my end goal, to get
>these into glibc, but are there things I don't know about in considering
>moving to these functions?
>
>
> --Joey Smith
>
>On Tue, 14 Sep 1999, Andi Gutmans wrote:
>