Skip to content

Conversation

@Fuzzbawls
Copy link
Collaborator

Since we no longer require the sprout params, we can package the sapling params inside the source repository (and the release binaries) until such time that the client has the ability to fetch these params directly from the P2P network.

Overview of the changes here per-OS:

  • macOS release binaries will use the params that are bundled into the .app bundle
  • Windows installer .exe will automatically install the params into the AppData directory.
  • Linux PPA/Snap/Copr installs will automatically install the params into the appropriate directory (either $SNAP_USER_COMMON/.pivx-params or /usr/local/share)
  • Linux tarballs include a bash shell script that can be run to install the params files into $HOME/.pivx-params

Note: Windows users that choose to use the .zip binary package will need to manually copy the params files to the appropriate AppData directory on their own (to be documented later)

The install-params.sh script is also run-able on linux/macOS from repository clones or source tarball paths to install the params into the OS-appropriate location for future use.

@Fuzzbawls Fuzzbawls added this to the 5.0.0 milestone Dec 3, 2020
@Fuzzbawls Fuzzbawls self-assigned this Dec 3, 2020
random-zebra
random-zebra previously approved these changes Dec 5, 2020
Copy link

@random-zebra random-zebra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Linux and Windows gitian builds tested. Awesome job. ACK 3b8289c906d9b04c920d65a0bc902128dd42f1ba

Since we no longer require the sprout params, we can package the sapling
 params inside the source repository (and the release binaries) until
 such time that the client has the ability to fetch these params
 directly from the P2P network.

 Overview of the changes here per-OS:
 - macOS release binaries will use the params that are bundled into the
 `.app` bundle
 - Windows installer `.exe` will automatically install the params into
 the appdata directory.
 - linux PPA/Snap/Copr installs will automatically install the params
 into the appropriate directory (either `$SNAP_USER_COMMON/.pivx-params`
  or `/usr/local/share`
- Linux tarballs include a bash shell script that can be run to install
the params files into `$HOME/.pivx-params`

Note: Windows users that choose to use the `.zip` binary package will
need to manually copy the params files to the appropriate `AppData`
directory on their own (to be documented later)
@Fuzzbawls
Copy link
Collaborator Author

pushed a small update to include the install-params.sh script inside the osx64 non-app bundle tarball

Copy link

@random-zebra random-zebra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK 3e641c1

Copy link

@furszy furszy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested gitian macOS deployed bundle, working like charm as well! 🍻.
Nice job!!
ACK 3e641c1 and merging

@furszy furszy merged commit 8385a96 into PIVX-Project:master Dec 5, 2020
random-zebra added a commit that referenced this pull request Dec 7, 2020
2109aec [Build] Proper coverage for ppa, local, and snapcraft (Fuzzbawls)

Pull request description:

  Followup to #2022 to resolve the lingering issues with ppa/snapcraft builds.

  build-log of a PPA build can be seen [here](https://launchpadlibrarian.net/510054528/buildlog_ubuntu-bionic-amd64.pivx_4.3.99~202012060757+gitdc5ad4478~ubuntu18.04.1_BUILDING.txt.gz)

  This also introduces proper `desktop-launch` wrapping for the nightly snapcraft builds, which is required to successfully open the GUI wallet from the snap commands.

ACKs for top commit:
  furszy:
    utACK 2109aec
  random-zebra:
    utACK 2109aec and merging...

Tree-SHA512: e113e1037ade34cf5b23548538c2ecdb1d838edaa6ccd7020541ca1f84555e04b24ba9b9cc80424c0c10d15318030644c90924e3adfb453fc62fc49546c71724
random-zebra added a commit that referenced this pull request Dec 9, 2020
… framework.

9afec2e CMakeList, pivxd and test_pivx fix for missing MacOS framework. (furszy)

Pull request description:

  Without the framework include, CMake isn't able to find the `CFBundleGetMainBundle` and relative classes/functions. Thus why isn't compiling pivxd and the unit test target. Dependency included due #2022 changes.

ACKs for top commit:
  Fuzzbawls:
    utACK 9afec2e
  random-zebra:
    utACK 9afec2e and merging...

Tree-SHA512: a872a78738b579b28f1b05fe61e2980c7c1ddd197f3412687f8835f10a12e3ac58c3c97c6c7074c2674359193629ea38f96f2bd17565dae9d59052889c089b10
@Fuzzbawls Fuzzbawls added the Needs Release Notes Placeholder tag for anything needing mention in the "Notable Changes" section of release notes label Dec 14, 2020
@random-zebra random-zebra removed the Needs Release Notes Placeholder tag for anything needing mention in the "Notable Changes" section of release notes label Jan 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants