[Box Backup] Exclude lists

Chris Wilson boxbackup@fluffy.co.uk
Tue, 22 Feb 2005 00:11:11 +0000 (GMT)


Hi all,

>>> Or perhaps you could require that Box Backup was built, and then link
>>> in the .a files which are produced as part of the build process? Quite
>>> a handy set of libraries.
>> 
>> Perhaps making a libboxbackup.so would be the way to go here, meaning
>> that the only requirement for building the gui would be a working
>> installation of box. It also helps clearly delineate between code with
>> the two different licences.
>
> As a developer of DarwinPorts (a porting system), I'd prefer to see this 
> approach. It would be better for the dependency checking if the GUI depended 
> on a working boxbackup installation vs. building a built-in copy of the code.

Unfortunately I do need Box's headers as well as the shared library, and 
since I have neither at the moment without a copy of Box itself, I am just 
looking for permission to distribute Box (without changing its license) 
together with my application.

Cheers, Chris.
-- 
_ ___ __     _
  / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |