Topic: Question about P2Pool Version (Read 969 times)
Thanks for the response. If I wanted to design my own front end. Is there a way to make changes and not have a dirty version?
I must have missed your question in the p2pool thread. It has to do with a git command. The version info is pulled from you local git repo of p2pool. Basically, in __init__.py, it makes a call like this:
Code:
git describe --always --dirty
As you rightfully suspect, if you've added files to your local repository (for example, a custom front end), then git will return back that your repository is "dirty".
I've been searching for this answer and haven't been able to find one. I also posted this question in the Pool thread, but nobody has responded with an answer.
When looking at someone's p2pool node. Some of them say Version: 13.4-57-gdfad3cd. And others will say something like: Version: 13.4-57-gdfad3cd-dirty. What does the
-dirty represent? Has code been changed that needs to be verified?
I just want to make sure that if i'm going to mine in a new node that there isn't any funny business. All I can seem to narrow it down to is certain nodes have custom front ends and those all say dirty.
Any response would be appreciated.
Thank you
When looking at someone's p2pool node. Some of them say Version: 13.4-57-gdfad3cd. And others will say something like: Version: 13.4-57-gdfad3cd-dirty. What does the
-dirty represent? Has code been changed that needs to be verified?
I just want to make sure that if i'm going to mine in a new node that there isn't any funny business. All I can seem to narrow it down to is certain nodes have custom front ends and those all say dirty.
Any response would be appreciated.
Thank you
Jump to: