Change build.sh to apply patches to version-bumped git build about rtorrent-ps HOT 8 CLOSED

🏁 Status: git builds and runs as 0.9.7/0.13.7, but without patches

from rtorrent-ps.

Looks like the function should be removed from rtorrent-ps, now that pyroscope's request to merge the "cmd_ui_current_view" function into rtorrent has been accepted.

from rtorrent-ps.

No it shouldn't, since that 'd break release builds. The problem is Jari not bumping the version to 0.9.7 after release, which makes these conditions not work:

#if RT_HEX_VERSION <= 0x000906

So patch the configure.in to proper dev versioning before building a git version.

from rtorrent-ps.

Just now improving git build proces to carry proper versions.

from rtorrent-ps.

but without patches

• you can grab all my (0.9.7/0.13.7) patches if you use the same commits that are in my build.sh.
  • rt patches modified to use the same dir level as libtorrent pathces (build.sh has been modded as well acording to this)
• also you have to a look which your files (*.cc) are modifed to handle various stuff

from rtorrent-ps.

Oh, I almost forgot it, 1 more:

• I also applied Add ability in build script to use 'all' in librottent patches
• this all keyword also applies all the other patches: misc, ps, etc.

I also labelled all my issues with build when some important change happened in build.sh.

Now, your original build.sh script is perfect! :)

from rtorrent-ps.

When a git build is properly patched (carries a 0.9.7/0.13.7 version like it should), things do work by now (if not, reopen with a problem description).

build.sh has the code to do that patch, and now also supports multi-version tagging in patch file names (so you can do 0.9.7 only, or *_0.9.6_0.9.7_*).

from rtorrent-ps.

Awesome!

and now also supports multi-version tagging in patch file names

:) I forgot to mention this one.

from rtorrent-ps.