At 11:08 AM 2/19/2003, Douglas Gregor wrote:
>On Wednesday 19 February 2003 10:46 am, William E. Kempf wrote:
>> Beman Dawes said:
>> > I'd like to hold off as many changes as possible until after the
>> > release. I don't have time to think clearly about the problems
>> > involved, and I'd like
On Wednesday 19 February 2003 10:46 am, William E. Kempf wrote:
> Beman Dawes said:
> > I'd like to hold off as many changes as possible until after the
> > release. I don't have time to think clearly about the problems
> > involved, and I'd like to actually try out some of the software too.
> >
On Tuesday 18 February 2003 08:46 pm, Darryl Green wrote:
> It may be easier to use a platform dependent (or user selectable) xslt
> tool rather than try to build/install a cross platform one? Anyone who
> has a recent enough IE installed on Windows has XSLT installed - why not
> use it.
Absolutel
Beman Dawes said:
> At 11:56 AM 2/18/2003, William E. Kempf wrote:
>
> >Well, I'm in favor of that, since we're moving at least some of the
> documentation to Boost.Book with this release (or so I gathered). So
> what's the group opinion on this one?
>
> I'd like to hold off as many changes as p
At 11:56 AM 2/18/2003, William E. Kempf wrote:
>Well, I'm in favor of that, since we're moving at least some of the
>documentation to Boost.Book with this release (or so I gathered). So
>what's the group opinion on this one?
I'd like to hold off as many changes as possible until after the releas
> -Original Message-
> From: William E. Kempf [mailto:[EMAIL PROTECTED]]
> This a minor difference here, though. The bjam executable boot straps
> fairly easily on most platforms. XSLT processors aren't quite as
> convenient. At least that was my experience that last time I tried to
do
>
On Tue, 18 Feb 2003, William E. Kempf wrote:
> > If there are no complains, I would _love_ to move BoostBook out of the
> > sandbox and into its (presumably) permanent place in Boost CVS.
>
> Well, I'm in favor of that, since we're moving at least some of the
> documentation to Boost.Book with this
Douglas Paul Gregor said:
> On Tue, 18 Feb 2003, William E. Kempf wrote:
>> Douglas Gregor said:
>> A reasonable concern. But if we keep only release versions of
>> generated documentation in CVS, I don't think it will be too severe.
>> Intermediate doc changes would either have to be accessed d
On Mon, 17 Feb 2003, Beman Dawes wrote:
> At 06:24 PM 2/17/2003, Douglas Gregor wrote:
> >Well, you'll have the doc source on your machine, and can generate
> whatever
> >format you want.
>
> Where is this documented? How long does it take? It there a way to only
> regenerate the files that chang
On Tue, 18 Feb 2003, William E. Kempf wrote:
> Douglas Gregor said:
> > You probably caught me messing with the scripts (and therefore
> > regenerating the documentation in-place).
>
> Long term, this wouldn't be satisfactory. The scripts should be generated
> in a seperate location to minimize t
Douglas Gregor said:
> On Monday 17 February 2003 04:49 pm, Beman Dawes wrote:
>> At 02:00 PM 2/17/2003, Douglas Gregor wrote:
>> >They're always available here, regenerated nightly in HTML, DocBook,
>> FO, PDF, and man pages:
>> > http://www.cs.rpi.edu/~gregod/boost/doc/html/libraries.html
>>
At 06:24 PM 2/17/2003, Douglas Gregor wrote:
>On Monday 17 February 2003 04:49 pm, Beman Dawes wrote:
>> Having the docs locally on my own machine is just a lot more
>> satisfactory. Cheaper, too (my Internet access is metered service.)
>
>Well, you'll have the doc source on your machine, and can
On Monday 17 February 2003 04:49 pm, Beman Dawes wrote:
> At 02:00 PM 2/17/2003, Douglas Gregor wrote:
> >They're always available here, regenerated nightly in HTML, DocBook, FO,
> >PDF, and man pages:
> > http://www.cs.rpi.edu/~gregod/boost/doc/html/libraries.html
>
> That really isn't very sa
> >We don't want to stick all of the generated HTML into CVS (too big).
>
>If it is too big for the regular CVS, isn't it too big for the >distribution
too? How big is big?
This is a radical idea, but maybe that's what's needed.
What if we did this:
1) Create a new CVS repository ala the sandbox
At 02:00 PM 2/17/2003, Douglas Gregor wrote:
>On Monday 17 February 2003 11:21 am, Beman Dawes wrote:
>> Ouch! That means the current HTML docs for these libraries aren't
>> available to Boosters who depend on CVS to keep up-to-date,
>
>They're always available here, regenerated nightly in HTML, D
On Monday 17 February 2003 11:21 am, Beman Dawes wrote:
> Ouch! That means the current HTML docs for these libraries aren't available
> to Boosters who depend on CVS to keep up-to-date,
They're always available here, regenerated nightly in HTML, DocBook, FO, PDF,
and man pages:
http://www.cs.rp
At 12:04 AM 2/17/2003, Douglas Gregor wrote:
>I've removed the HTML-only documentation for these three libraries from
>CVS,as the documentation for each is now maintained in BoostBook.
>/index.html forwarding documents are in place to get to the
>generated documentation (in doc/html), and when we
At 12:04 AM 2/17/2003, Douglas Gregor wrote:
>I've removed the HTML-only documentation for these three libraries from
>CVS, as the documentation for each is now maintained in BoostBook.
>/index.html forwarding documents are in place to get to the
>generated documentation (in doc/html), and when we
I've removed the HTML-only documentation for these three libraries from CVS,
as the documentation for each is now maintained in BoostBook.
/index.html forwarding documents are in place to get to the
generated documentation (in doc/html), and when we near the release I will
provide a tarball/zip
19 matches
Mail list logo
