On 06/28/2016 05:24 PM, Daniel Pfeifer wrote:
> I have attached a patch that adds a script to update liblzma from
> upstream (closely modeled after the other update scripts).  I am not
> sure how these kinds of scripts need to be run.
> 
> We currently have a copy of liblzma version 5.0.5. The latest version
> on the 5.0 branch is 5.0.8. Once the script is introduced, we may
> consider switching to the 5.2 branch.

I've merged an `update-libarchive` topic to `next`:

 Merge topic 'update-liblzma' into next
 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4e7bb44e

that uses your update script with minor tweaks.  First I re-imported
the existing version with it to transition the infrastructure.  I
manually edited the parent of the new import root commit to connect
to the old import branch.  Then I ran the update to 5.0.8 and
resolved the conflicts.

Once that is in `master` please look at following the pattern to
update to 5.2.2.  Just resolve conflicts on the first merge and
then follow up with changes to port back to C90 in separate commits.
See the log of the Utilities/cmliblzma directory for how this was
done before.

Thanks,
-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Reply via email to