On 02 Feb 2015, at 12:14, Andreas Färber <afaer...@suse.de> wrote:

>> ... perhaps you should update the documentation to clearly define the status 
>> of 0.8.0.
> 
> It is not "my" project. I'm telling you there may well be good reasons
> for end users to use the Git version, which means building themselves.
> Unless you want to setup an automatic Git packaging and build workflow,
> e.g. on the Open Build Service, which also cross-builds some software.
> But no, I'm not volunteering, as I have no need.

I fully respect your opinions and I do not want to comment any more on your 
reasons, how good they are, and if it is ok to impose them to all end-users.

I just suggested to improve your documentation, to clearly define your reasons 
and explain them in such a way that end-users can fully understand them and 
weight the benefits of building from source code, so they can decide themselves 
whether to do it or not; we can do whatever we want, but the ultimate decision 
belongs to the user, and I think it is ok to be so.

I just added an explicit note about building from sources to the OpenOCD 
Install page in my documentation.

If, after a while, you'll succeed to convince all end-users to build from 
sources and site anlytics will show no more binary downloads, then both Freddie 
Chopin and myself will have a problem less to worry about and we'll no longer 
have to distribute the binary versions.


Regards,

Liviu






------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to