Sharing Code / Embedding 2 Licenses?

[FatalRemedy]

Now that the release is tagged and people are breathing a little  
easier (I hope) I wanted to repost this email that got lost in the bug  
parade fray.


I have a question about embedded licenses as its described at: http://wiki.fluidproject.org/display/fluid/Embedded+Fluid+license

I am attempting to clean up the embedded licenses in VULab's files.  
Obviously we shouldn't put our license on exclusive phpESP files, but  
what about a file is modified?

For Instance..
database.php is from the phpESP source BUT it has been modified to  
work with the VULab files. It has its own license embedded from phpESP  
but that doesn't reflect the modifications VULab has made to the file.
(just as a refresher, VULab is currently built on phpESP another open  
source survey tool)

Do we embed both licenses? I couldn't find any examples of this  
scenario in the fluid source. Any insight into this would be great.

Thanks in advance :)
Sincerely,
Blake
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20081219/8c5e4e6d/attachment.htm>