#3 Changes location of header installation to use %{real_name}, making boost.spec easier to use with different versions of boost
Closed 4 years ago by denisarnaud. Opened 4 years ago by tazato.
Unknown source master  into  master

file modified
+2 -2
@@ -44,7 +44,7 @@

  Version: 1.69.0

  %global version_enc 1_69_0

  %global version_suffix 169

- Release: 13%{?dist}

+ Release: 14%{?dist}

  License: Boost and MIT and Python


  %global toplev_dirname %{real_name}_%{version_enc}
@@ -1141,7 +1141,7 @@


  %files devel

  %license LICENSE_1_0.txt

- %{_includedir}/%{name}

+ %{_includedir}/%{real_name}




I naively thought that I could just change the name of the package, the version, and the source tar and package a newer version of boost with this spec.

This change is quality of life for the next person that tries to do the same.

Thanks for your contribution!

Well, a few parallel versions of Boost may be installed thanks to boost148 and boost169.
In all of those packages, %{name} (equal to boost1NN) is used rather than %{real_name} (equal to boost). It allows to install several versions in parallel. If we accept your pull request, the additional Boost packages will be not be able to be installed in parallel to the core Boost package.

An example of using those parallel-installable Boost packages is explained in https://bugzilla.redhat.com/show_bug.cgi?id=1767503#c7
For reference:

 mkdir -p build
 pushd build
 %cmake -DBOOST_LIBRARYDIR=%{_libdir}/boost148 \
  -DBOOST_INCLUDEDIR=%{_includedir}/boost148 \
  -DBoost_ADDITIONAL_VERSIONS="1.48 1.48.0" ..
 make %{?_smp_mflags}

Pull-Request has been closed by denisarnaud

4 years ago

Makes sense. Thanks for taking a look at it!