I'm not a lawyer. As far as I know since you are not modifying the software in any way, nor are you creating any form of derivative work you need do nothing other than provide the complete liquibase software to the user. The rights you transfer will be fullfilled by Liquibases website and associated infrastructure.
The GPL/LGPL only really get sticky with derivative works where the viral aspect of the licence comes into play. Just using the software and transferring it require very little to be done. Paul ----- Original Message ---- From: LiquiBase Community Forum <[email protected]> To: [email protected] Sent: Thursday, 13 August, 2009 19:24:40 Subject: [Liquibase-user] New Topic: GPL on target customer servers for the jar file A new topic, 'GPL on target customer servers for the jar file', has been made on a board you are watching.. You can see it at http://liquibase.org/forum/index.php?topic=120..new#new The text of the topic is shown below: GPL is always a little foggy around this area but I'd like to ask you guys. We have an installer that will need to update database on customer sites. Can we install the liquibase jar onto the customer machine and perform the DB updates? Do I need to remove the jar file after I'm done (im ok with this). Am I allowed to even plop that jar file on the target server? Thanks Bryce Unsubscribe to new topics from this board by clicking here: http://liquibase.org/forum/index.php?action=notifyboard;board=1.0 Regards, The LiquiBase Community Forum Team. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Liquibase-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/liquibase-user
