Ian,

The code is provided under the LGPL2 (that's what the LICENSE.txt file ends up 
saying, since CUPS has both library and program bits covered under GPL2 and 
LGPL2) with some exceptions for Apple OS's and OpenSSL.


On Jun 19, 2012, at 2:16 AM, "MacArthur, Ian (SELEX GALILEO, UK)" 
<ian.macart...@selexgalileo.com> wrote:

>>> ...
>>> Since we already provide an API that lists a directory contents, should
>> we provide other information about directory entries as well? I added this
>> to FLTK2 many years ago because the FileChooser need a sort-by-date
>> function.
>> 
>> 
>> CUPS has code for this already and abstracts away from Windows/POSIX,
>> providing filename and stat info in one place.
>> 
>> http://svn.easysw.com/public/cups/trunk/cups/dir.c
>> http://svn.easysw.com/public/cups/trunk/cups/dir.h
> 
> 
> Mike,
> 
> Those files have Apple copyright statements on them... are we allowed to 
> "look" at them for our purposes?
> 
> Or... if we dig back far enough, can we find the same code with an "easier" 
> copyright (is that even a valid thing to do?)
> 
> Or...?
> 
> 
> 
> SELEX Galileo Ltd
> Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 
> 3EL
> A company registered in England & Wales.  Company no. 02426132
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
> 
> _______________________________________________
> fltk-dev mailing list
> fltk-dev@easysw.com
> http://lists.easysw.com/mailman/listinfo/fltk-dev

_____________
Michael Sweet

_______________________________________________
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to