Best practice for publishing an open source project with third party dependancies -


i publish project codeplex. question best approach 2 third party libraries project depends on. 1 system.data.sqlite , other dapper. should put specific binaries built against repository allow user code , run without getting other dependancies, or should mentioned in documentation requirements?

i don't know how codeplex community handles typically. can speak in general.

normally not publish binaries in open-source code repository. typically windows binaries published parts of releases, times installer package. in package include binaries executable depends on.

note if publish binary (your own software) makes more sense provide dependencies. think worst case of user trying binary slightly, not compatible binary built third-party sources, , obtaining erratic behavior.

one thing have note if publish third-party software, have adhere license. in example of gpl means need ship relevant documentation , offer provide source files used build these binaries on request. in cases easier not ship them.


Comments

Popular posts from this blog

android - getbluetoothservice() called with no bluetoothmanagercallback -

sql - ASP.NET SqlDataSource, like on SelectCommand -

ios - Undefined symbols for architecture armv7: "_OBJC_CLASS_$_SSZipArchive" -