[1.35.0] Release branch snapshots
The first attempt at a release branch snapshot is now available. See http://beta.boost.org/development/testing.html#Snapshots for more information, and a link to the actual files. Thanks to Martin Wille for setting up the hosting! The plan is to automatically build Unix and Windows snapshots on a daily basis. Right now the only snapshot available is a .zip with Windows line endings. For the moment the focus is simply getting the build process in place for both Unix and Windows. Once that is running more or less smoothly, the focus can shift to making sure the content is all there, and that other QA checks are being met. --Beman
Beman Dawes wrote:
The first attempt at a release branch snapshot is now available.
See http://beta.boost.org/development/testing.html#Snapshots for more information, and a link to the actual files.
Thanks to Martin Wille for setting up the hosting!
Yes, thanks Martin!
The plan is to automatically build Unix and Windows snapshots on a daily basis. Right now the only snapshot available is a .zip with Windows line endings.
For the moment the focus is simply getting the build process in place for both Unix and Windows. Once that is running more or less smoothly, the focus can shift to making sure the content is all there, and that other QA checks are being met.
I downloaded the .zip file and unpacked it on my Linux box converting the files endings (unzip -a). Here's a few issues I noticed in looking over the docs: 1) We need updates of all the added/changed libraries on the main page 2) link for asio is broken off the 'libraries' page -- looks like it may be missing in the doc/src/boost.xml file -- not seeing anything in the docs location. 3) system library has 2 lines on 'libraries' page 4) GIL isn't licensed under BSL -- is this ok? I thought we were trying to move as much to BSL as possible. 5) circular_buffer is missing a link from the libraries page 6) property_tree is missing a link from the libraries page I'm running a build now...I'll let you know the results. Jeff
On 03/02/2008, Jeff Garland <azswdude@gmail.com> wrote:
1) We need updates of all the added/changed libraries on the main page 2) link for asio is broken off the 'libraries' page -- looks like it may be missing in the doc/src/boost.xml file -- not seeing anything in the docs location. 3) system library has 2 lines on 'libraries' page 4) GIL isn't licensed under BSL -- is this ok? I thought we were trying to move as much to BSL as possible. 5) circular_buffer is missing a link from the libraries page 6) property_tree is missing a link from the libraries page
Another issue for the list: 7) There are two copies of the quickbook documentation, one standalone copy in tools/quickbook/doc/html and one in the combined documentation at doc/html.
Daniel James wrote:
On 03/02/2008, Jeff Garland <azswdude@gmail.com> wrote:
1) We need updates of all the added/changed libraries on the main page 2) link for asio is broken off the 'libraries' page -- looks like it may be missing in the doc/src/boost.xml file -- not seeing anything in the docs location. 3) system library has 2 lines on 'libraries' page 4) GIL isn't licensed under BSL -- is this ok? I thought we were trying to move as much to BSL as possible. 5) circular_buffer is missing a link from the libraries page 6) property_tree is missing a link from the libraries page
Another issue for the list:
7) There are two copies of the quickbook documentation, one standalone copy in tools/quickbook/doc/html
That copy is already in SVN.
and one in the combined documentation at doc/html.
Then that's the copy generated by the documentation build process. Should the tools/quickbook/doc/html directory be removed entirely from the release tarball? Thanks for catching this, --Beman
Jeff Garland wrote:
Beman Dawes wrote:
The first attempt at a release branch snapshot is now available.
See http://beta.boost.org/development/testing.html#Snapshots for more information, and a link to the actual files. ... I downloaded the .zip file and unpacked it on my Linux box converting the files endings (unzip -a). Here's a few issues I noticed in looking over the docs:
1) We need updates of all the added/changed libraries on the main page 2) link for asio is broken off the 'libraries' page -- looks like it may be missing in the doc/src/boost.xml file -- not seeing anything in the docs location. 3) system library has 2 lines on 'libraries' page 4) GIL isn't licensed under BSL -- is this ok? I thought we were trying to move as much to BSL as possible. 5) circular_buffer is missing a link from the libraries page 6) property_tree is missing a link from the libraries page
Thanks, Jeff! I'll work on getting the library page in shape. --Beman
Beman Dawes wrote:
4) GIL isn't licensed under BSL -- is this ok? I thought we were trying to move as much to BSL as possible.
I believe GIL is already under Boost Software License. What made you conclude that it isn't? Is there a header somewhere that needs changing? Lubomir
On Feb 4, 2008 4:07 PM, Lubomir Bourdev <lbourdev@adobe.com> wrote:
Beman Dawes wrote:
4) GIL isn't licensed under BSL -- is this ok? I thought we were trying to move as much to BSL as possible.
I believe GIL is already under Boost Software License. What made you conclude that it isn't? Is there a header somewhere that needs changing?
The documentation in the 1.35 release snapshot said it's the MIT license -- so it's probably just a docs change...I didn't actually look at the source code. Jeff
Beman Dawes wrote:
The first attempt at a release branch snapshot is now available.
See http://beta.boost.org/development/testing.html#Snapshots for more information, and a link to the actual files.
Thanks to Martin Wille for setting up the hosting!
The plan is to automatically build Unix and Windows snapshots on a daily basis. Right now the only snapshot available is a .zip with Windows line endings.
.gz and .bz2 files are now available with POSIX line endings. With exports from CVS, POSIX file permissions had to be adjusted. SVN export seems to have gotten the permissions closer to right, so the POSIX snapshot script isn't applying any permission changes. But I'm not all that knowledgeable about POSIX file permissions, so it would be helpful is some POSIX users would take a look and report any problems they find. --Beman
On Mon, Feb 04, 2008 at 01:57:08PM -0500, Beman Dawes wrote:
Beman Dawes wrote:
The first attempt at a release branch snapshot is now available.
See http://beta.boost.org/development/testing.html#Snapshots for more information, and a link to the actual files.
I miss a reference to a Subversion branch on this page.
Thanks to Martin Wille for setting up the hosting!
The plan is to automatically build Unix and Windows snapshots on a daily basis. Right now the only snapshot available is a .zip with Windows line endings.
.gz and .bz2 files are now available with POSIX line endings.
With exports from CVS, POSIX file permissions had to be adjusted. SVN export seems to have gotten the permissions closer to right, so the POSIX snapshot script isn't applying any permission changes.
But I'm not all that knowledgeable about POSIX file permissions, so it would be helpful is some POSIX users would take a look and report any problems they find.
I tried in a bash shell the following: $ grep -rl $'\r\n' . | grep -v '\.\(png\|gif\|jpeg\|pdf\|jpg\|vcproj\|svg\)' I explicitely added SVG files as most miss a svn:eol-style native property in Subversion which should be fixed as SVG are ordinary text files. Remaining files (reordered): Probably missing svn:eol-style native property: ./tools/regression/test/test-cases/general/bjam.log ./tools/quickbook/test/templates.quickbook ./tools/quickbook/test/code-snippet.gold ./tools/quickbook/test/code-block-2.quickbook ./tools/quickbook/test/preformatted.quickbook ./tools/quickbook/test/code-block-1.gold ./tools/quickbook/test/xinclude.gold ./tools/quickbook/test/code-block-1.quickbook ./tools/quickbook/test/import.quickbook ./tools/quickbook/test/link-side-by-side.quickbook ./tools/quickbook/test/escape.gold ./tools/quickbook/test/code-block-2.gold ./tools/quickbook/test/quickbook-manual.quickbook ./tools/quickbook/test/code-snippet.quickbook ./tools/quickbook/test/preformatted.gold ./tools/quickbook/test/templates.gold ./tools/quickbook/test/import.gold ./tools/quickbook/test/quickbook-manual.gold ./tools/quickbook/test/xinclude.quickbook ./tools/quickbook/test/escape.quickbook ./tools/quickbook/test/link-side-by-side.gold ./tools/jam/src/boost-jam.spec ./libs/config/doc/html/HTML.manifest ./libs/serialization/borland6ide/test_simple_class.bpf ./libs/test/test/test_files/errors_handling_test.pattern2 ./libs/test/test/test_files/test_tools_test.pattern ./libs/test/test/test_files/errors_handling_test.pattern ./libs/wave/samples/waveidl/idllexer/idl.re ./libs/wave/src/cpplexer/re2clex/strict_cpp_re.inc ./libs/wave/src/cpplexer/re2clex/cpp.re ./libs/wave/src/cpplexer/re2clex/cpp_re.inc ./libs/wave/src/cpplexer/re2clex/strict_cpp.re ./libs/wave/ChangeLog ./libs/interprocess/proj/cygwin/MakeAll ./libs/interprocess/proj/conceptgcc/MakeAll ./libs/interprocess/proj/mingw/MakeAll ./libs/interprocess/proj/qnx/MakeAll ./libs/interprocess/proj/linux/MakeAll ./boost/ptr_container/serialize_ptr_container.hpp OK: ./libs/statechart/example/Performance/Performance.xls ./libs/intrusive/proj/vc7ide/Intrusive.sln ./libs/smart_ptr/smarttest.zip ./libs/interprocess/proj/vc7ide/Interprocess.sln ./libs/thread/test/test.mcp ./libs/python/build/VisualStudio/boost_python.dsw ./libs/python/build/VisualStudio/boost_python.dsp ./libs/python/example/project.zip ./libs/python/build/python_v1.zip ./more/favicon.ico The file permissions are according to $ find -exec ls -l {} \; | cut -d" " -f1 | sort | uniq drwxr-xr-x insgesamt -rw-r--r-- -rwxr-xr-x probably OK, except that many files are bogusly marked executable: $ find -exec ls -l {} \; | grep -- "-rwxr-xr-x" -rwxr-xr-x 1 jens jens 2610 2007-07-06 21:47 rst.css -rwxr-xr-x 1 jens jens 1755 2007-11-15 17:31 ./tools/buildbot/config/master/alpha/master.cfg -rwxr-xr-x 1 jens jens 1143 2006-09-13 19:25 ./tools/inspect/minmax_check.hpp -rwxr-xr-x 1 jens jens 4470 2008-02-04 18:42 id646983-bb.html [many many files snipped] Check for the svn:executable property and delete it (and forbid commits from Windows users if they do not respect it :-)) Jens
Jens Seidel wrote:
On Mon, Feb 04, 2008 at 01:57:08PM -0500, Beman Dawes wrote:
Beman Dawes wrote:
The first attempt at a release branch snapshot is now available.
See http://beta.boost.org/development/testing.html#Snapshots for more information, and a link to the actual files.
I miss a reference to a Subversion branch on this page.
Added.
... I tried in a bash shell the following: $ grep -rl $'\r\n' . | grep -v '\.\(png\|gif\|jpeg\|pdf\|jpg\|vcproj\|svg\)'
I explicitely added SVG files as most miss a svn:eol-style native property in Subversion which should be fixed as SVG are ordinary text files. Remaining files (reordered):
Probably missing svn:eol-style native property:
./tools/regression/test/test-cases/general/bjam.log ./tools/quickbook/test/templates.quickbook ./tools/quickbook/test/code-snippet.gold ./tools/quickbook/test/code-block-2.quickbook ./tools/quickbook/test/preformatted.quickbook ./tools/quickbook/test/code-block-1.gold ./tools/quickbook/test/xinclude.gold ./tools/quickbook/test/code-block-1.quickbook ./tools/quickbook/test/import.quickbook ./tools/quickbook/test/link-side-by-side.quickbook ./tools/quickbook/test/escape.gold ./tools/quickbook/test/code-block-2.gold ./tools/quickbook/test/quickbook-manual.quickbook ./tools/quickbook/test/code-snippet.quickbook ./tools/quickbook/test/preformatted.gold ./tools/quickbook/test/templates.gold ./tools/quickbook/test/import.gold ./tools/quickbook/test/quickbook-manual.gold ./tools/quickbook/test/xinclude.quickbook ./tools/quickbook/test/escape.quickbook ./tools/quickbook/test/link-side-by-side.gold ./tools/jam/src/boost-jam.spec ./libs/config/doc/html/HTML.manifest ./libs/serialization/borland6ide/test_simple_class.bpf ./libs/test/test/test_files/errors_handling_test.pattern2 ./libs/test/test/test_files/test_tools_test.pattern ./libs/test/test/test_files/errors_handling_test.pattern ./libs/wave/samples/waveidl/idllexer/idl.re ./libs/wave/src/cpplexer/re2clex/strict_cpp_re.inc ./libs/wave/src/cpplexer/re2clex/cpp.re ./libs/wave/src/cpplexer/re2clex/cpp_re.inc ./libs/wave/src/cpplexer/re2clex/strict_cpp.re ./libs/wave/ChangeLog ./libs/interprocess/proj/cygwin/MakeAll ./libs/interprocess/proj/conceptgcc/MakeAll ./libs/interprocess/proj/mingw/MakeAll ./libs/interprocess/proj/qnx/MakeAll ./libs/interprocess/proj/linux/MakeAll ./boost/ptr_container/serialize_ptr_container.hpp
I'm not sure what the fix is for this. Doug? Anyone?
OK:
./libs/statechart/example/Performance/Performance.xls ./libs/intrusive/proj/vc7ide/Intrusive.sln ./libs/smart_ptr/smarttest.zip ./libs/interprocess/proj/vc7ide/Interprocess.sln ./libs/thread/test/test.mcp ./libs/python/build/VisualStudio/boost_python.dsw ./libs/python/build/VisualStudio/boost_python.dsp ./libs/python/example/project.zip ./libs/python/build/python_v1.zip ./more/favicon.ico
The file permissions are according to
$ find -exec ls -l {} \; | cut -d" " -f1 | sort | uniq drwxr-xr-x insgesamt -rw-r--r-- -rwxr-xr-x
probably OK, except that many files are bogusly marked executable: $ find -exec ls -l {} \; | grep -- "-rwxr-xr-x" -rwxr-xr-x 1 jens jens 2610 2007-07-06 21:47 rst.css -rwxr-xr-x 1 jens jens 1755 2007-11-15 17:31 ./tools/buildbot/config/master/alpha/master.cfg -rwxr-xr-x 1 jens jens 1143 2006-09-13 19:25 ./tools/inspect/minmax_check.hpp -rwxr-xr-x 1 jens jens 4470 2008-02-04 18:42 id646983-bb.html [many many files snipped]
Check for the svn:executable property and delete it (and forbid commits from Windows users if they do not respect it :-))
How do we "Check for the svn:executable property and delete it"? How do we prevent the svn:executable property from being set incorrectly in the future? AFAIK, the executable bit isn't something Windows users have any control over. Help needed on these! --Beman
On Thu, Feb 07, 2008 at 08:36:03AM -0500, Beman Dawes wrote:
Jens Seidel wrote:
On Mon, Feb 04, 2008 at 01:57:08PM -0500, Beman Dawes wrote:
Beman Dawes wrote:
The first attempt at a release branch snapshot is now available.
I tried in a bash shell the following: $ grep -rl $'\r\n' . | grep -v '\.\(png\|gif\|jpeg\|pdf\|jpg\|vcproj\|svg\)'
(Clarification: I search for DOS line endings in the UNIX tar archive.)
I explicitely added SVG files as most miss a svn:eol-style native property in Subversion which should be fixed as SVG are ordinary text files. Remaining files (reordered):
Probably missing svn:eol-style native property:
./tools/regression/test/test-cases/general/bjam.log ... I'm not sure what the fix is for this. Doug? Anyone?
A fix is simple: $ svn propset svn:eol-style native tools/regression/test/test-cases/general/bjam.log "native" ensures that a checked out file has the expected system style for end of line markers (\n on Posix, \r\n for DOS, \r for MacOS). Please read the Subversion documentation for details. (There may be some trouble if working under cygwin, I think this system gets \n which may not fit if you use a DOS/Windows editor in parallel.) Attention: This should only be set for text files. To be honest I didn't checked whether UNIX line endings in SVG files are allowod but the probability for it is > 99%.
The file permissions are according to probably OK, except that many files are bogusly marked executable: $ find -exec ls -l {} \; | grep -- "-rwxr-xr-x" -rwxr-xr-x 1 jens jens 2610 2007-07-06 21:47 rst.css -rwxr-xr-x 1 jens jens 1755 2007-11-15 17:31 ./tools/buildbot/config/master/alpha/master.cfg -rwxr-xr-x 1 jens jens 1143 2006-09-13 19:25 ./tools/inspect/minmax_check.hpp -rwxr-xr-x 1 jens jens 4470 2008-02-04 18:42 id646983-bb.html [many many files snipped]
Check for the svn:executable property and delete it (and forbid commits from Windows users if they do not respect it :-))
How do we "Check for the svn:executable property and delete it"?
$ svn propget svn:executable rst.css * $ svn propdel svn:executable rst.css property 'svn:executable' deleted from 'rst.css'.
How do we prevent the svn:executable property from being set incorrectly in the future? AFAIK, the executable bit isn't something Windows users have any control over.
Yep. But I care about the executable property in Subversion and even Windows users have control over it. It is probably not easy to avoid that it is set (and requires knownledge about it), as it is taken by default from the filesystem permission which is missing on Windows so that a default is used. Once we assume that filename suffixes allow to determine the content it is simple: Just edit the Subversion configuration file (on POSIX systems ~/.subversion/config) and enable [miscellany] ### Set enable-auto-props to 'yes' to enable automatic properties ### for 'svn add' and 'svn import', it defaults to 'no'. ### Automatic properties are defined in the section 'auto-props'. enable-auto-props = yes [auto-props] ### The format of the entries is: ### file-name-pattern = propname[=value][;propname[=value]...] ### The file-name-pattern can contain wildcards (such as '*' and ### '?'). All entries which match will be applied to the file. ### Note that auto-props functionality must be enabled, which ### is typically done by setting the 'enable-auto-props' option. *.c = svn:eol-style=native *.cpp = svn:eol-style=native *.cc = svn:eol-style=native *.h = svn:eol-style=native *.hpp = svn:eol-style=native *.dsp = svn:eol-style=CRLF *.dsw = svn:eol-style=CRLF *.sh = svn:eol-style=native;svn:executable *.txt = svn:eol-style=native *.tex = svn:eol-style=native *.png = svn:mime-type=image/png *.xpm = svn:mime-type=image/x-xpixmap;svn:eol-style=native *.jpg = svn:mime-type=image/jpeg Makefile = svn:eol-style=native Makefile.am = svn:eol-style=native You need to adapt this list ...
Help needed on these!
Should be simple using some shell magic ... Jens
participants (5)
-
Beman Dawes -
Daniel James -
Jeff Garland -
Jens Seidel -
Lubomir Bourdev