wiki:ReleasePractices/HotFixes

Version 6 (modified by Beman Dawes, 14 years ago) ( diff )

Fix typo, add more warnings

Patches for specific release problems

This is an experiment. Please send feedback on usefulness to the Boost Developers list.

Boost developers may occasionally make quick bug fixes available in the form of patches.

  • Patches are specific to the indicated Boost release, and may not work correctly or at all for other releases.
  • Patches assume that prior (lower numbered) changeset patches for the library have been applied.
  • Patches are not tested as rigorously as releases. It is safer to only apply patches if you actually need them.
  • Patches are generally only supplied for code contained entirely in headers.
  • Backing up a directory before applying patches is recommended.

Release 1.36.0

Library Changeset Description Directory
Filesystem 48192 Restore deprecated basic_directory_entry functions inadvertently omitted from 1.36.0. boost-root/boost/filesystem
Filesystem 48374 Restore deprecated functions has_branch_path and has_leaf, inadvertently omitted from 1.36.0 boost-root/boost/filesystem
Filesystem 48377 Revert remove changes inadvertently committed by 47006. Fully apply ticket #1972 remove fixes. Only the first patch (operations.hpp) in this changeset is required. The others can safely be ignored. boost-root/boost/filesystem

Instructions for applying patches

Prerequisite: The patch command line utility. patch is preinstalled on Mac OS X and most Linux and Unix systems. For Windows, it may be obtained from Cygwin.

  • In the table, click the link for the desired Changeset.
  • On the bottom of the Changeset page, click on "Download in other formats: Unified Diff".
  • Open a command prompt window using your operating system. Enter these two commands, replacing directory with the path to directory from the table, download-path with the path to your download directory, and # with the changeset number:
     cd directory
     patch <download-path/changeset_r#.diff

Note the "<" before the location of the download-path. If you forget it, patch will hang waiting for console input.

Note: See TracWiki for help on using the wiki.