[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [E-devel] evas and poppler

I have no objections myself. The licensing is a little bit odd in my understanding. You could license your sourcecode as BSD, like most of E, as long as you don't copy code directly from poppler, but if you link against poppler then the executable will be GPL. So you end up with a situation where, if people get the code from CVS, they can consider it BSD licensed. If they are distributing the application, they need to treat it as GPL.

On 2/13/06, Vincent Torri <Vincent.Torri@iecn.u-nancy.fr> wrote:


for those who do not know, poppler is a library that can parse and render
pdf content to some kind of 'bitmaps'. I've written an evas frontend for
it. But the developpers don't want to include it in the poppler cvs until
"a couple of applications start using it". I don't know how people will
use that front end if it's not available.

So I would like to add the evas front end (with three widgets (evas smart
one, ewl one and etk one) and with an example for all of them) in the
proto/ directory. In addition, it will be easier for us to maintain it.

I recall that, as poppler takes code from xpdf, it's released under the
GPL licence.

Is there any objection to add that 'epdf' library in proto/ ? (licence
(i don't know much about the problems related to licence) or something


This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
enlightenment-devel mailing list