Perfect! Thank you all :) // Fredrik
Den tisdagen den 10:e september 2013 skrev Deke Kincaid: > You could also just point them to the official repository on gitorious > > > http://qt.gitorious.org/pyside/pyside-tools/source/92062bcf842814328a9f4a89f10c115bfcace0b3 > : > > Even though I’m not a lawyer, the license looks pretty clear that you can > redestribute it: > > > http://qt.gitorious.org/pyside/pyside-tools/source/92062bcf842814328a9f4a89f10c115bfcace0b3:LICENSE-uic > > > 1. Redistribution and use in source and binary forms, with or without > 2. modification, are permitted provided that the following conditions > are met: > 3. > 4. 1. Redistributions of source code must retain the above copyright > 5. notice, this list of conditions and the following disclaimer. > 6. 2. Redistributions in binary form must reproduce the above copyright > 7. notice, this list of conditions and the following disclaimer in the > 8. documentation and/or other materials provided with the > distribution. > 9. 3. Neither the name of the University nor the names of its > contributors > 10. may be used to endorse or promote products derived from this > software > 11. without specific prior written permission. > > > ----- > Deke Kincaid > Creative Specialist > The Foundry > Mobile: (310) 883 4313 > Tel: (310) 399 4555 - Fax: (310) 450 4516 > > The Foundry Visionmongers Ltd. > Registered in England and Wales No: 4642027 > > > On Mon, Sep 9, 2013 at 3:43 PM, Fredrik Averpil > <[email protected]<javascript:_e({}, 'cvml', > '[email protected]');> > > wrote: > >> Hi Nathan, >> Hm ...maybe, yes. Am I in any kind of trouble if I put pysideuic into a >> public GitHub repository along with the app? >> >> Regards, >> Fredrik >> >> >> >> >> On Mon, Sep 9, 2013 at 7:28 PM, Nathan Rusch >> <[email protected]<javascript:_e({}, 'cvml', >> '[email protected]');> >> > wrote: >> >>> Instead of requiring the end user to have an external Python >>> interpreter, a PySide build, *and* pysideuic installed, why not just >>> require that they have pysideuic available somewhere on the PYTHONPATH when >>> Nuke is launched? It’s a pretty standard way of handling external >>> dependencies for Python modules that require them... >>> >>> -Nathan >>> >>> >>> >> >> _______________________________________________ >> Nuke-python mailing list >> [email protected] <javascript:_e({}, 'cvml', >> '[email protected]');>, >> http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> >
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
