[Pkg-bitcoin-devel] miners
Scott Howard
showard314 at gmail.com
Mon Dec 10 18:57:53 UTC 2012
On Sun, Dec 9, 2012 at 11:19 PM, Dmitry Smirnov <onlyjob at member.fsf.org> wrote:
> On Mon, 10 Dec 2012 12:13:38 Scott Howard wrote:
>> No problem - we can keep the repo for now in case you or someone else
>> gets an interest in it in the future. Wait and see is appropriate, no
>> point in rushing it. I won't upload.
>
> Thank you.
>
>
>> The mining packages, however, are
>> useful - so if you get around to them let me know.
>
> Sure. At the moment "cpuminer" only need review and update for its package
> description -- I hope you could help here if you find a minute.
>
> "cgminer" needs package description and licensing/copyright review -- I'll try
> to do the latter when I can. Otherwise it should be ready.
Since cgminer is a fork of cpuminer, and is more actively maintained
than cpuminer - do you think it would be best to just have cgminer?
Are there any features in cgminer that are not present in cpuminer? If
there are, could we possibly patch cgminer to include those changes?
Let me know what you think. I think Debian would have the same benefit
from just have cgminer as it would from having both packages, so
perhaps we should just use cgminer.
For license reviews, I've just started using CDBS's license checking
targets, which are very helpful:
$ make -f /usr/share/cdbs/1/rules/utils.mk debian/stamp-copyright-check
will scan all the files and output a DEP-5 formatted
copyright_newhints file which you can use as a starting point. If you
keep that _newhints file as copyright_hints and run the CDBS check
again it will find what files have changed or been added and try to
figure out the license and copyright from the header. It's a nice way
to keep up with undocumented upstream changes
~Scott
More information about the Pkg-bitcoin-devel
mailing list