I am sorry, but I feel frustrated a bit with the latest 0.1.6 version. Code: ./dcrinstall-linux-amd64-v0.1.6 dcrticketbuyer is still running Excuse me ? Is there a way to unpack only ? In current directory ? Not touch anything else ? I really do not care what the installer thinks is right for me. Yes, I can compile from source, but is this really necessary ? I do not see any "single file installer" in Governance - roadmap (apart from GUI, presume GUI is not included).
@root if you just want to download the files you can just grab them from https://github.com/decred/decred-binaries/releases/tag/v0.1.6 No need to use the installer if you don't want or if it doesn't do what you need.
Thanks for clarification, I feel a relief it is just a "directory structure" change. Hmmm ... I have to change scripts anyway, archive contains a subdirectory-version now.
I had some scripts to change too due to the directory naming changes so you can be sure I didn't make the change lightly. But the original naming really wasn't very good so it didn't seem like we should be stuck with it forever.
I was perfectly happy before, but I understand things do change. I just want them to change for the better.
Well our aim with the installer is to aid people that are not CLI savvy. We are obviously working toward the GUI and an installation suite to go along with it. This is just the first step in that process. If you have any input about how you think the installer should work, feel free to let us know.
As I linked above - Governance - roadmap - GUI paragraf talks about one click installer. I already posted my multiplatform GUI idea, now collecting thoughts and trying to get attention. No input at the moment, just a wish - faster ticket sync (11 minutes?) : Spoiler: daemon start - ticket sync %CPU %MEM TIME+ COMMAND 142,2 0,5 15:09.97 dcrd 23:04:11 2016-06-22 [INF] DCRD: Version 0.1.6-beta 23:04:11 2016-06-22 [INF] DCRD: Loading block database from 'dcrd/mainnet/blocks_leveldb' 23:04:11 2016-06-22 [INF] BCDB: Address index synced and loaded to height 39277 23:04:11 2016-06-22 [INF] DCRD: Block database loaded with block height 39277 23:04:11 2016-06-22 [INF] DCRD: Block ticket database initialized empty 23:04:11 2016-06-22 [INF] DCRD: Db non-empty, resyncing ticket DB 23:15:11 2016-06-22 [WRN] AMGR: Skipping bound address: address 127.0.0.1 is not routable 23:15:11 2016-06-22 [INF] BMGR: Generating initial block node index. This may take a while... 23:15:13 2016-06-22 [INF] BMGR: Block index generation complete
Work is currently underway to merge in my upstream work on btcd which makes a ton of changes in order to make use of the newer and much more efficient database that I ported over in PR#91. After that is done, the ticket database will be updated to both use the new database and the new package I submitted in PR#266 which significantly speeds up the in-memory ticket access. Once both of those are done, the entire need for ticket syncing on startup and shutdown will be gone. TL;DR: It's being worked on.
As was pointed out already, good old archive with binaries can be used from https://github.com/decred/decred-binaries/releases/tag/v0.1.6 and I do not see anything wrong or any strange errors or problems there. I noticed the new dcrinstall in git/releases before official release announcement and started this thread without knowing the context.
dcrinstall -verbose That logs everything you need to the console, or You can look at ~/decred/dcrinstatller.log for full log history
Couple ideas : 1/ --downloadonly flag, I can try to implement it and send pull request 2/ --beta / --stable flags to select the version of preference 3/ option to download blockchain backup. 7z archive saves 50% and the fresh start can be in minutes, not in hours as of now. I use it for my experiments. You can try the download speeds, they have 30 centers around the world, but this is a paid service, and only 14 days trial. (mainnet has broken GOB i think, rescan needed). PRG site : https://1533627264.rsc.cdn77.org/dcrd-testnet.7z https://1533627264.rsc.cdn77.org/dcrd-mainnet.7z Any thoughts ?
1. (--downloadonly) sounds like a reasonable idea. I don't have the time to work on it at the moment, but I do see the use in it. 2. You can already specify --manifest to pick a version which I think makes a lot more sense then beta/stable. 3. I'm not a fan of this idea. It requires putting the blockchain up somewhere (and updating it). I prefer to trust the network rather than some site like that. Second, it is faster now, but as the chain grows that becomes problematic too. Look at the old torrent file for bitcoind. The correct solution is to improve the download speed for the daemon (which the db work being done should help with).
While I understand you're trying to be helpful, I strongly recommend not using the 7z format for compression - the 7z compression libs have a recent (May 12th, 2016) exploit. I expect many users may not have a patched/updated version of the 7z tools and I consider it unnecessarily risky to suggest people use this compression format at the current time.
1/ Was quite easy, decred code is well documented, works fine, I'd like to do more tests with different flags. 2/ Specifying manifest requires more knowledge and searching than just stable/beta - easier for use I'd say 3/ My thoughts were similar to @jcv but on the other hand consider the user experience - first start in minutes (instead of hours). It would be a great success and Decred would be the only one and everybody's preferred choice. The point was to start the discussion and weight priorities. Thanks @jy-p for warning, but that was just an example, another compression can be used, I thought about lzham, but that would be even less tested. The important fact is the trust. If I trust the developers with my money, I trust the crypto/signature, I can easily trust there is valid blockchain and no evil code in provided and signed archive.