Simon Richter wrote:
> > I don't think this is true in general, a texinfo file could @include a
> > file that is built during the build phase.
>
> True, however that's a bad thing IMO, as it requires the user to have a
> working texinfo installation.
>
> > (For example, I generate Texinfo code do
On Mon, 2004-03-08 at 15:23, Cook, Kelley (R.K.) wrote:
> > Hi,
> >
> > [Info files being built in source dir]
> >
> > > FWIW, having a read only source directory is our goal.
> >
> > When the source dir is readonly, noone can change the texinfo
> > files. If noone can change the texinfo files,
>>> "Simon" == Simon Josefsson <[EMAIL PROTECTED]> writes:
Simon> Simon Richter <[EMAIL PROTECTED]> writes:
[...]
>> When the source dir is readonly, noone can change the texinfo files. If
>> noone can change the texinfo files, there is no need to rebuild the info
>> files, so it doesn't matte
Simon Richter <[EMAIL PROTECTED]> writes:
> Simon,
>
>> > [Info files being built in source dir]
>
>> > When the source dir is readonly, noone can change the texinfo files. If
>> > noone can change the texinfo files, there is no need to rebuild the info
>> > files, so it doesn't matter that they'r
On Fri, 2004-03-12 at 04:11, Simon Richter wrote:
> Simon,
>
> > > [Info files being built in source dir]
>
> > > When the source dir is readonly, noone can change the texinfo files. If
> > > noone can change the texinfo files, there is no need to rebuild the info
> > > files, so it doesn't matte
Simon,
> > [Info files being built in source dir]
> > When the source dir is readonly, noone can change the texinfo files. If
> > noone can change the texinfo files, there is no need to rebuild the info
> > files, so it doesn't matter that they're in a readonly directory.
> I don't think this is
Simon Richter <[EMAIL PROTECTED]> writes:
> Hi,
>
> [Info files being built in source dir]
>
>> FWIW, having a read only source directory is our goal.
>
> When the source dir is readonly, noone can change the texinfo files. If
> noone can change the texinfo files, there is no need to rebuild the i
> Hi,
>
> [Info files being built in source dir]
>
> > FWIW, having a read only source directory is our goal.
>
> When the source dir is readonly, noone can change the texinfo
> files. If noone can change the texinfo files, there is no need
> to rebuild the info files, so it doesn't matter tha
Kelley Cook <[EMAIL PROTECTED]> writes:
Sorry if this is a RTFM, but I can't find it.
The release notes for automake 1.8, mention that it changes the
defaults to go back to building the .info files in the source
directory since that is the GNU coding standards.
What do I have to p
Hi,
[Info files being built in source dir]
> FWIW, having a read only source directory is our goal.
When the source dir is readonly, noone can change the texinfo files. If
noone can change the texinfo files, there is no need to rebuild the info
files, so it doesn't matter that they're in a reado
Sorry if this is a RTFM, but I can't find it.
The release notes for automake 1.8, mention that it changes the defaults
to go back to building the .info files in the source directory since
that is the GNU coding standards.
What do I have to put in my Makefile.am to put them back to being built
in b
Sorry if this is a RTFM, but I can't find it.
The release notes for automake 1.8, mention that it changes the defaults
to go back to building the .info files in the source directory since
that is the GNU coding standards.
What do I have to put in my Makefile.am to put them back to being built
12 matches
Mail list logo
