Hi again, Derick.

As long as I can see, the two files that were created for the timezonedb 
extension have PHP License according to their headers. Then, there are several 
other files from the Olson database that are under public domain. So the whole 
package should be considered under the PHP License.

Well, I'm a bit stunned about this situation, and I don't know very well what 
else to do.

How to convince you of doing something that, according to my point of view, 
should be simple and not causing any trouble at all, but you've already said 
say it's a silly requirement by the people that build the binaries for the 
extensions...

Thousands of people that have Windows servers using PHP would take advantage of that 
little file, this "silly" requirement, but that is legally needed for a binary 
to get distributed, and because of that, it is needed too for allowing the binary 
generation.

What can I do?  Would this situation progress if I say "please, please, please" 
and I use my Puss-in-Boots face[1]?

[1] 
http://fc04.deviantart.net/fs19/f/2007/227/6/9/Puss_in_Boots_2_by_PuszekOkruszek7.jpg

Thanks for your attention.

Best regards,
--
David Marín Carreño
Ingeniero en Informática
SICE - Dirección Técnica
Dpto. de Software Interurbano
Tfno: +34 91 623 23 36
Móvil: +34 650 460 569
E-mail: [email protected]<mailto:[email protected]>


El 27/10/2014 a las 9:54, Pierre Joye escribió:

hi,

On Mon, Oct 27, 2014 at 2:50 PM, David Marín Carreño 
<[email protected]><mailto:[email protected]> wrote:


Hi all, again.

Excuse me if I'm being insistent, but please, someone add that LICENSE file
to the repository for the Windows binaries to be generated.
According to the two files in the source code, the license should be the PHP
license.



As far as I remember Derick was not keen to do it. So convince him and
you are in.

Cheers,
Pierre
.






________________________________
Este mensaje y cualquier fichero anexo está dirigido exclusivamente a los 
destinatarios especificados. La información contenida puede ser confidencial 
y/o estar legalmente protegida y no necesariamente refleja la opinión de esta 
compañía. Si usted recibe este mensaje por error, por favor comuníqueselo 
inmediatamente al remitente y elimínelo.

This message and any attached files are intended solely for the addressee/s 
identified herein. It may contain confidential and/or legally privileged 
information and may not necessarily represent the opinion of this Company. If 
you receive this message in error, please immediately notify the sender and 
delete it.
_____________________________________________________________________________________________________________________________________________________________________________________________________________

Reply via email to