On 03/05/2017 08:44 AM, Eric Voskuil wrote:
> This is great, thanks for the update.
>
> Note that version 3.0.0 is pending release and as such master has been versioned 4.0.0. You should be working on v3 since v4 is exactly the same presently and will undergo significant change on its way to release. I expect v3 to be tagged very soon and v4 work to progress for most of 2017.

Yes, that is why I am calling the v4 packages libbitcoin4-*

When three is tagged it should be easy for me to move the spec files to
tagged release and call them libbitcoin-* but leave the four spec files
for people who want to run it on a test machine for developing stuff.

>
> We build all repositories on Travis for each pull request and each merge on every branch. This includes various build configurations of Linux and OSX. The installer manages a couple bugs that are tedious to deal with manually. One of them is a boost-icu bug. If this is not managed properly and you build with ICU enabled you will see breaks in ICU functionality. Proper ICU operation is critical due to the inclusion of BIP39. Without the fix the build would complete as if successful and all code would run, but the results would be incorrect. So we've patched it in the installation, added test cases to catch the silent failure, and perform a run-time on-first-use test as well. See install.sh comments for details on the patch.

I will do so, I may have stumbled on the ICU issue.

>
> The generated java and python wrappers are experimental. You could leave them out of your packaging if it's a hassle.

I have them as sub-packages so they don't need to be installed by the
user if the user doesn't want them.

But I figured out the python path thing, when installing outside of /usr
just need a libbitcoin.pth file in the standard python path to tell it
where to look.

>
> e
>
> -----Original Message-----
> From: Libbitcoin [mailto:libbitcoin-bounces@lists.dyne.org] On Behalf Of Alice Wonder
> Sent: Saturday, March 4, 2017 2:01 PM
> To: libbitcoin@???
> Subject: [Libbitcoin] libbitcoin RPM spec files
>
> I made a git repo for the libbitcoin RPM spec files I am working on.
>
> https://github.com/AliceWonderMiscreations/libbitcoin-RPM
>
> Right now it only has spec files for the development 4.0.0 spec files and there are a few more I need to create and add.
>
> I'm trying to create them in such a way that someone who wants them installed in /opt/whatever instead of /usr will just have to define the alternate prefix when building and it will just work. That's really
> (imho) how package spec files should be done, even though /usr is usually what people use with RPM.
>
> The packaging of the python components of libbitcoin4-consensus needs some cleanup and I have to check about java classpath for the java component when used with an alternate install prefix.
>
> when the updated ICU package is installed in an alternate prefix, it works for building boost and for building libbitcoin but make check on libbitcoin then fails. However when ICU update is installed in /usr that isn't an issue, so I suspect that issue is with the ICU package.
>
> For the server package I have no created any systemd starup files, and I need to look at what would be required for it to work on an SELinux enforcing server.
>
> I haven't tried running the server yet, I want to build the explorer first which I haven't done yet.
>
> Anyway that's where I have the spec files, my intent is to get all the packaging issues worked out with the 4 release before creating spec files for the 3 release.
>
> And Boost - when I started, I started with Boost 1.63.0 and that resulted in some make check issues that don't happen with 1.58.0 so when I finish the 4 packaging I'll then try the various boost versions newer than 1.58.0 to find what version it breaks in and why.
>
> I guess it validates the value in always running make check.
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>