bug#7655: conditional _TEXINFOS should be supported

[Stefano Lattarini]

On Thursday 16 December 2010, Ralf Wildenhues wrote:
 Severity: wishlist
 
 Conditional _TEXINFOS files should be supported, i.e.,
 
 if COND
 info_TEXINFOS = foo.texi
 foo_TEXINFOS = bar.texi
 nodist_info_TEXINFOS = generated.texi
 endif
 
 should work to generate and install foo.{info,pdf,...} only if COND,
 but distribute foo.texi and bar.texi always.  Similar with
 generated.texi (except for distribution, of course).
 
 Cheers,
 Ralf
 
JFTR: this is basically PR/191 from the older gnats database:
 
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-traildatabase=automakepr=191

Regards,
   Stefano

bug#7655: conditional _TEXINFOS should be supported

[Jack Kelly]

On Fri, Dec 17, 2010 at 6:09 AM, Ralf Wildenhues ralf.wildenh...@gmx.de wrote:
 if COND
 info_TEXINFOS = foo.texi
 foo_TEXINFOS = bar.texi
 nodist_info_TEXINFOS = generated.texi
 endif

 should work to generate and install foo.{info,pdf,...} only if COND,
 but distribute foo.texi and bar.texi always.  Similar with
 generated.texi (except for distribution, of course).

Disagree. foo.info should always be built, because it goes into `make
dist'. If you want to limit building for non-specific `make', then
make sure that the .info files and such all depend on `make dist', so
the tarball is correctly generated.

Agree with the remarks about not making pdfs, dvis and inhibiting
their installation.

-- Jack

bug#7655: conditional _TEXINFOS should be supported

[Ralf Wildenhues]

[ no need to keep bug-automake@ in Cc:; debbugs takes care of that ]

Hello Jack,

* Jack Kelly wrote on Thu, Dec 16, 2010 at 08:42:52PM CET:
 On Fri, Dec 17, 2010 at 6:41 AM, Jack Kelly wrote:
  On Fri, Dec 17, 2010 at 6:09 AM, Ralf Wildenhues wrote:
  if COND
  info_TEXINFOS = foo.texi
  foo_TEXINFOS = bar.texi
  nodist_info_TEXINFOS = generated.texi
  endif
 
  should work to generate and install foo.{info,pdf,...} only if COND,
  but distribute foo.texi and bar.texi always.  Similar with
  generated.texi (except for distribution, of course).
 
  Disagree. foo.info should always be built, because it goes into `make
  dist'.

Ah, a piece of logic I didn't think of.  Hmpf.

I need to reread all the long comments in automake.in, to also take the
info-in-srcdir-or-not complication into account.

  If you want to limit building for non-specific `make', then
  make sure that the .info files and such all depend on `make dist', so
  the tarball is correctly generated.

I want to be able to say no, I do not want this info file to be built
nor installed for the user.  This is what (at least some) users need.

Also, some users need to be able to generate .texi files.  I'm not sure
if it is always sufficient to let the maintainer generate them (and ship
them plus their .info files).

 Further thoughts on the above: The maintainer should always have
 access to `texinfo', and the user should never have to rebuild .info
 files, so it seems OK to me if they're not blocked when COND is false.

I don't understand what you mean with blocked nor with access to
`texinfo'.

Thanks,
Ralf

bug#7655: conditional _TEXINFOS should be supported

[Ralf Wildenhues]

Severity: wishlist

Conditional _TEXINFOS files should be supported, i.e.,

if COND
info_TEXINFOS = foo.texi
foo_TEXINFOS = bar.texi
nodist_info_TEXINFOS = generated.texi
endif

should work to generate and install foo.{info,pdf,...} only if COND,
but distribute foo.texi and bar.texi always.  Similar with
generated.texi (except for distribution, of course).

Cheers,
Ralf

Re: _TEXINFOS question

[Alexandre Duret-Lutz]

 Patrick == Patrick Guio [EMAIL PROTECTED] writes:

 Patrick Dear all,
 Patrick I am using the _TEXINFOS variables in a Makefile.am to build the
 Patrick documentation. I would like these to be built on request with a `doc'
 Patrick target for example and not with the default 'all' or 'all-am'.
 Patrick Is there a way to do that?

No friendly way.
-- 
Alexandre Duret-Lutz

_TEXINFOS question

[Patrick Guio]

Dear all,
I am using the _TEXINFOS variables in a Makefile.am to build the
documentation. I would like these to be built on request with a `doc'
target for example and not with the default 'all' or 'all-am'.
Is there a way to do that?
Sincerely, Patrick

Re: *_TEXINFOS

[Alexandre Oliva]

On May 17, 2001, Tom Tromey [EMAIL PROTECTED] wrote:

 Sometimes I wonder if this is really the right thing to do.

Perhaps it should be an option?

I often use read-only srcdir myself, so I'd like to have this
possibility.  Anyway, since we do update files that are part of the
distribution (think configure and Makefile.in), modifying info files
doesn't really add much.

OTOH, since `make dist' will now pick files from the builddir instead
of srcdir, if they exist in the builddir (unless my memory is failing
badly :-), creating files in the build tree wouldn't make much of a
difference for maintainers anyway.  Unless they wrote Makefile rules
that depended on the fact that files were in the build tree, in which
case they'd be in trouble.  `make distcheck' would hopefully tell them
so.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

*_TEXINFOS

[Lars J. Aas]

I've just started learning the texinfo format, and noticed that the
file.info files generated during make was built in $srcdir and not
$builddir.  Is this because makeinfo isn't expected to be found on
the build system, or something else?

  Lars J