View Single Post
Old 11-11-2011, 09:59 AM   #6
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi,

Quote:
Originally Posted by ldolse View Post
The only other valid reason I could think of for trying to get the whole build system working is if you were trying to fork Calibre. Maybe if you explain to us why you feel it necessary to build the whole package we could provide some better direction.
Having volunteered on many open source projects over the years, I find this response very troubling.

The whole point of GPL is that the source is available to build and volunteers are encouraged to build their own ...

If this is a GPL project then please provide the instructions necessary to build distribution packages for all platforms that you release on.

Yes, most changes are simply changes to the python code and that is fine. But there are now binary C/C++ files in this build are their not?

Yes, they can be messy and yes they can require lots of extra dependencies, but some sort of build instructions, scripts, or make files should be made available since they have to exist.

Why all of the secrecy on how to build release dmgs, etc?

KevinH
KevinH is offline   Reply With Quote