Re: [Boost-cmake] README.txt and Welcome.txt?
2009/1/28 Beman Dawes : > > It would be a tiny bit easier if the URL was always the same, but > that's no big deal if not convenient. I've changed it so that this will show the latest entry: lynx -dump -nolist -display_charset=utf-8 \ http://beta.boost.org/users/history/minimal.php \ > README.txt Although, that could be problematic if we ever maintain branches for point releases. Daniel ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] README.txt and Welcome.txt?
On Tue, Jan 27, 2009 at 6:35 PM, Daniel James wrote: > 2009/1/27 troy d. straszheim : >> I tweaked things when I brought cmake over so that it wouldn't insist on >> having a README.txt there, but of course it'd be good to have something >> better than the generic one that comes packaged with cmake. > > OK, I'll leave this for a future release. I'd prefer to add it this release on the theory that we've got everyone's attention and it looks easy to do, so let's get it out of the way. Daniel, if you could do two things, that should get us rolling on this. * Create http://beta.boost.org/users/history/minimal.php/version_1_38_0 (or some permanent URL, if you can pull that off.) * Update https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList "Release cycle initialization" to indicate what has to be done to set up for each new release. Thanks, --Beman ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] README.txt and Welcome.txt?
On Sun, Jan 25, 2009 at 3:34 PM, Daniel James wrote: > Beman, would it be possible for you to install lynx and add the > appropriate command to your release scripts? I installed Cygwin's lynx and it ran fine on first try, using the command line you provided. No problem adding this to the daily snapshot script that is the basis for the release script. It would be a tiny bit easier if the URL was always the same, but that's no big deal if not convenient. --Beman ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] README.txt and Welcome.txt?
Daniel James wrote: I've added a note to the changelog and the groups page on the beta site. If there are any other pages you'd like me to change, let me know. http://beta.boost.org/community/groups.html#cmake http://beta.boost.org/users/news/version_1_38_0#version_1_38_0.other_changes Perfect. Thanks! If you want to, you should be able to change the website yourself, the details are at: http://beta.boost.org/development/website_updating.html and thanks again. -t ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] README.txt and Welcome.txt?
2009/1/27 troy d. straszheim : > I tweaked things when I brought cmake over so that it wouldn't insist on > having a README.txt there, but of course it'd be good to have something > better than the generic one that comes packaged with cmake. OK, I'll leave this for a future release. > Could we get a line added to the "official" docs and changelog that > experimental CMake support is in, with a link to the archives of this list > and I spose the boost-cmake wiki pages? I've added a note to the changelog and the groups page on the beta site. If there are any other pages you'd like me to change, let me know. http://beta.boost.org/community/groups.html#cmake http://beta.boost.org/users/news/version_1_38_0#version_1_38_0.other_changes If you want to, you should be able to change the website yourself, the details are at: http://beta.boost.org/development/website_updating.html Daniel ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] README.txt and Welcome.txt?
I tweaked things when I brought cmake over so that it wouldn't insist on having a README.txt there, but of course it'd be good to have something better than the generic one that comes packaged with cmake. Could we get a line added to the "official" docs and changelog that experimental CMake support is in, with a link to the archives of this list and I spose the boost-cmake wiki pages? -t Daniel James wrote: 2008/11/2 Daniel James : 2008/11/2 Beman Dawes : Unless README.txt can be updated automatically, it is going to be a maintenance problem for release managers. The release announcement is a quickbook file, so it should be possible to generate a plain text file from it (or if that's too tricky we could use lynx to generate text from html, it does a reasonable job). Sorry, I'm just getting to this now. Generating plain text from quickbook is actually quite tricky. There doesn't seem to be any solutions for generating plain text from docbook. I had a go at converting Rene's bbook2rss script to generate text, with reasonable results, but don't fancy maintaining it. So I think using lynx is the way to go. I've just checked a small php page into the beta site that will display the release announcement in plain html, so that lynx can generate a text file from it. The command line to do this is: lynx -dump -nolist http://beta.boost.org/users/history/minimal.php/version_1_37_0 > README.txt I've attached the output for 1.37. Does it seem okay? Is there anything else I should add? Maybe some extra text at the start. Beman, would it be possible for you to install lynx and add the appropriate command to your release scripts? If you can't, I could generate this file along with the documentation. I expect we'll need to set this up for 1.38 since the cmake files are included in the release. Daniel ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] README.txt and Welcome.txt?
2008/11/2 Daniel James : > 2008/11/2 Beman Dawes : >> >> Unless README.txt can be updated automatically, it is going to be a >> maintenance problem for release managers. > > The release announcement is a quickbook file, so it should be possible > to generate a plain text file from it (or if that's too tricky we > could use lynx to generate text from html, it does a reasonable job). Sorry, I'm just getting to this now. Generating plain text from quickbook is actually quite tricky. There doesn't seem to be any solutions for generating plain text from docbook. I had a go at converting Rene's bbook2rss script to generate text, with reasonable results, but don't fancy maintaining it. So I think using lynx is the way to go. I've just checked a small php page into the beta site that will display the release announcement in plain html, so that lynx can generate a text file from it. The command line to do this is: lynx -dump -nolist http://beta.boost.org/users/history/minimal.php/version_1_37_0 > README.txt I've attached the output for 1.37. Does it seem okay? Is there anything else I should add? Maybe some extra text at the start. Beman, would it be possible for you to install lynx and add the appropriate command to your release scripts? If you can't, I could generate this file along with the documentation. I expect we'll need to set this up for 1.38 since the cmake files are included in the release. Daniel Version 1.37.0 November 3rd, 2008 12:00 GMT New Libraries * Proto: + Expression template library and compiler construction toolkit for domain-specific embedded languages, from Eric Niebler. Updated Libraries * Asio: + Enhanced CompletionCondition concept with the signature size_t CompletionCondition(error_code ec, size_t total), where the return value indicates the maximum number of bytes to be transferred on the next read or write operation. (The old CompletionCondition signature is still supported for backwards compatibility). + New windows::overlapped_ptr class to allow arbitrary overlapped I/O functions (such as TransmitFile) to be used with Asio. + On recent versions of Linux, an eventfd descriptor is now used (rather than a pipe) to interrupt a blocked select/epoll reactor. + Added const overloads of lowest_layer(). + Synchronous read, write, accept and connect operations are now thread safe (meaning that it is now permitted to perform concurrent synchronous operations on an individual socket, if supported by the OS). + Reactor-based io_service implementations now use lazy initialisation to reduce the memory usage of an io_service object used only as a message queue. * Circular Buffer: + Added new methods is_linearized() and rotate(const_iterator). + Minor bug fixes and documentation updates. * Dynamic Bitset: + Constructor "do the right thing" dispatch, a la standard sequence containers (follows the proposed resolution of library issue 438, currently in the C++0x working paper). + Improvements to documentation, code examples and implementation. * Exception: + Support for non-RTTI builds. + Optimizations. + A new macro BOOST_THROW_EXCEPTION which can be used instead of boost::throw_exception when throwing, to automatically record information about the location of the throw in the exception object. * Hash: + Minor bug fix (ticket 2264). * Interprocess: + Added placement insertion (emplace(), emplace_back()...) methods to containers. + Containers can be used now in recursive types. + Minor bug fixes. * Intrusive: + Intrusive now takes advantage of compilers with variadic templates. + clone_from functions now copy predicates and hash functions of associative containers. + Added incremental hashing to unordered containers via incremental<> option. + Minor bug fixes. * Math.Special Functions: Improved accuracy and testing of the inverse hypergeometric functions. * Type Traits: Added better support for the Codegear compiler. * Unordered: + Rename overload of emplace with hint, to emplace_hint as specified in n2691. + Provide forwarding headers at and . + Move all of the implementation inside the boost/unordered directory. Compilers Tested Boost's primary test compilers are: * GCC 4.01 on Mac OS X 10.4.10 with both Intel and Power PC * GCC 4.2.4 on Ubuntu Linux 8.10 * GCC 4.3.2 on Debian Sid * GCC 4.2.1 on HP-UX Integrity
Re: [Boost-cmake] README.txt and Welcome.txt?
On Sun, Nov 2, 2008 at 9:01 AM, Beman Dawes <[EMAIL PROTECTED]> wrote: > On Sun, Nov 2, 2008 at 8:48 AM, Doug Gregor <[EMAIL PROTECTED]> wrote: >> >> On Sun, Nov 2, 2008 at 7:27 AM, Beman Dawes <[EMAIL PROTECTED]> wrote: >> > As part of the merge to trunk, two files got added to boost-root: >> > README.txt >> > and Welcome.txt. >> > >> > Was that intentional? >> >> Yes. >> >> > If so, what are these files, why are they needed, and how are they to be >> > maintained? >> >> They're used to build the graphical installers. Welcome.txt is the >> text you see when you initially open the installer, and README.txt >> comes up as the "release notes" a little later into the installer. >> >> README.txt will need to be updated with the summary of what's changed >> in each release (the same thing the release manager does for the >> release notes on SourceForge). Welcome.txt won't change. > > Unless README.txt can be updated automatically, it is going to be a > maintenance problem for release managers. Yup, I know. > Instead of having specific text that has to be changed each release, could > it contain the URL of the release notes on the web site? That doesn't really do what we want; we'd like the release notes to be complete inside the installer. >> If having these files in the root is bothersome, we can move them into >> tools/build/CMake; I'd suggest doing that for Welcome.txt but not for >> README.txt. > > I'm primarily worried how to keep them up to date, although it does seem > that since stuff in tools/build/CMake depends on them, that > tools/build/CMake is a more natural location. That's fine by me. Or, as Daniel said, we might be able to make the generation of README.txt part of the build for CMake. > Also, does the installation build allow them to have comments? Particularly > if they are not in tools/build/CMake, it might be nice if they had comments > saying what they are and how they get maintained. They're just text files, so there's no way to have comments without the comments showing up in the installer. - Doug ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] README.txt and Welcome.txt?
2008/11/2 Beman Dawes <[EMAIL PROTECTED]>: > > Unless README.txt can be updated automatically, it is going to be a > maintenance problem for release managers. The release announcement is a quickbook file, so it should be possible to generate a plain text file from it (or if that's too tricky we could use lynx to generate text from html, it does a reasonable job). Daniel ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] README.txt and Welcome.txt?
On Sun, Nov 2, 2008 at 8:48 AM, Doug Gregor <[EMAIL PROTECTED]> wrote: > On Sun, Nov 2, 2008 at 7:27 AM, Beman Dawes <[EMAIL PROTECTED]> wrote: > > As part of the merge to trunk, two files got added to boost-root: > README.txt > > and Welcome.txt. > > > > Was that intentional? > > Yes. > > > If so, what are these files, why are they needed, and how are they to be > > maintained? > > They're used to build the graphical installers. Welcome.txt is the > text you see when you initially open the installer, and README.txt > comes up as the "release notes" a little later into the installer. > > README.txt will need to be updated with the summary of what's changed > in each release (the same thing the release manager does for the > release notes on SourceForge). Welcome.txt won't change. Unless README.txt can be updated automatically, it is going to be a maintenance problem for release managers. Instead of having specific text that has to be changed each release, could it contain the URL of the release notes on the web site? If having these files in the root is bothersome, we can move them into > tools/build/CMake; I'd suggest doing that for Welcome.txt but not for > README.txt. I'm primarily worried how to keep them up to date, although it does seem that since stuff in tools/build/CMake depends on them, that tools/build/CMake is a more natural location. Also, does the installation build allow them to have comments? Particularly if they are not in tools/build/CMake, it might be nice if they had comments saying what they are and how they get maintained. --Beman ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] README.txt and Welcome.txt?
On Sun, Nov 2, 2008 at 7:27 AM, Beman Dawes <[EMAIL PROTECTED]> wrote: > As part of the merge to trunk, two files got added to boost-root: README.txt > and Welcome.txt. > > Was that intentional? Yes. > If so, what are these files, why are they needed, and how are they to be > maintained? They're used to build the graphical installers. Welcome.txt is the text you see when you initially open the installer, and README.txt comes up as the "release notes" a little later into the installer. README.txt will need to be updated with the summary of what's changed in each release (the same thing the release manager does for the release notes on SourceForge). Welcome.txt won't change. If having these files in the root is bothersome, we can move them into tools/build/CMake; I'd suggest doing that for Welcome.txt but not for README.txt. - Doug ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
[Boost-cmake] README.txt and Welcome.txt?
As part of the merge to trunk, two files got added to boost-root: README.txt and Welcome.txt. Was that intentional? If so, what are these files, why are they needed, and how are they to be maintained? Thanks, --Beman ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
