@@ -0,0 +1,185 @@ RPM Spec File Notes ------------------- The RPM spec file provided here is for Bitcoin-Core 0.12.0 and builds on CentOS 7 with either the CentOS provided OpenSSL library or with LibreSSL as packaged at [ LibreLAMP.com](It should hopefully not be too difficult to port the RPM spec file to most RPM based Linux distributions. When porting the spec file to build for a particular distribution, there are some important notes. ## Sources It is considered good form for all sources to reference a URL where the source can be downloaded. Sources 0-9 should be reserved for source code tarballs. `Source0` should reference the release tarball available from and `Source1` should reference the BerkeleyDB source. Sources 10-99 are for source files that are maintained in the [ Bitcoin git repository](but are not part of the release tarball. Most of these will reside in the `contrib` sub-directory. Mencari Peninggalan Hokage Keempat! / Episode 164: 'Sennin Mode Mencapai Batas' / Episode 165: 'Kyuubi Tertangkap' / Episode 166: 'Pengakuan' / Episode 167: 'Chibaku Tensei' / Episode 168: 'Hokage Keempat' / Episode 169: 'Dua Murid' / Episode 170: 'Petualangan Besar! Mencari Peninggalan Hokage Keempat! Part 2' / Episode 172: 'Pertemuan' / Episode 173: 'Pain yang Asli' / Episode 174: 'Kisah Naruto Uzumaki' / Episode 175: 'Pahlawan Konoha' / Link Alternative Buat yang ga mau ribet pake aja Single Link ini. Part1' / Episode 171: 'Petualangan Besar! Naruto shippuden 175. ![]() ![]() Sources 10-19 should be reserved for miscellaneous configuration files. Currently only `Source10` is used, for the example `bitcoin.conf` file. Sources 20-29 should be reserved for man pages. Currently only `Source20` through `Source23` are used. Sources 30-39 should be reserved for SELinux related files. Currently only `Source30` through `Source32` are used. Until those files are in a tagged release, the full URL specified in the RPM spec file will not work. Aug 6, 2017 - ~/rpmbuild/SPECS: The spec files we will have to construct. We cannot accept software that does not allow us to freely distribute it. Well, it appears that you have been reading this HowTo, which is a good beginning. You can get them from the git ropository where you retrieved this file. Sources 100+ are for files that are not source tarballs and are not maintained in the bitcoin git repository. At present only an SVG version of the Bitcoin icon is used. ## Patches In general, patches should be avoided. When a packager feels a patch is necessary, the packager should bring the problem to the attention of the bitcoin developers so that an official fix to the issue can make it into the next release. ### Patch0 bitcoin-0.12.0-libressl.patch This patch is only needed if building against LibreSSL. LibreSSL is not the standard TLS library on most Linux distributions. The patch will likely not be needed when 0.12.1 is released, a proper fix is already in the Bitcoin git master branch. ## BuildRequires The packages specified in the `BuildRequires` are specified according to the package naming convention currently used in CentOS 7 and EPEL for CentOS 7. You may need to change some of the package names for other distributions. This is most likely to be the case with the Qt packages. ## BerkeleyDB The `build-unix.md` file recommends building against BerkeleyDB 4.8.30. Even if that is the version your Linux distribution ships with, it probably is a good idea to build Bitcoin Core against a static version of that library compiled according to the instructions in the `build-unix.md` file so that any changes the distribution may make in the future will not result in a problem for users. The problem that can exist, clients built against different versions of BerkeleyDB may not be able read each other's `wallet.dat` file which can make it difficult for a user to recover from backup in the event of a system failure. ## Graphical User Interface and Qt Version The RPM spec file will by default build the GUI client linked against the Qt5 libraries. If you wish instead to link against the Qt4 libraries you need to pass the switch `-D '_use_qt4 1'` at build time to the `rpmbuild` or `mock` command used to build the packages.
0 Comments
Leave a Reply. |