Re: error in config.sub

2000-12-19 Thread Assar Westerlund

These files are maintained by [EMAIL PROTECTED], I've added a CC:
to that.

/assar

Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> For the MiNT system, the lines in config.sub are wrong. It's missing
> the '*'-wildcard. I've applied a patch below.
> 
> 
> Greetings,
> 
> Tomas
> 
> 
> 
> --- /usr/share/automake/config.sub~ Sat Sep  2 16:05:51 2000
> +++ /usr/share/automake/config.sub  Tue Dec 19 17:44:48 2000
> @@ -985,7 +985,7 @@
> -xenix)
> os=-xenix
> ;;
> --*mint | -*MiNT)
> +-*mint* | -*MiNT*)
> os=-mint
> ;;
> -none)




Re: [pdftex] Re: BOUNCE pdftex@tug.org: Non-member submission from ["Derek R.Price" ]

2000-12-19 Thread Sebastian Rahtz

Derek R. Price writes:
 > Basically, the issue is that the GNU coding standards state that the
 > texinfo.tex you built your docs with should be included with a source
 > distribution so that an end user is sure to be able to build your docs too.

you could try telling the automake people to get real.. oh dear they
are cc-ed. :-}

 > barbarically renaming the files before calling texi2dvi.
 > Aesthetically, I think coding the filename switch inside the *texi
 > source file would be most pleasing

sure, you can test the existence of the macro \pdfoutput in the
source, and \input a different file depending on whether or not
\pdfoutput exists

 > switch, and being able to specify a complete path to a *texinfo.tex
 > on the command line would be second best since it would avoid the
 > forced creation of extra directories.
you could do that too

 tex '\def\FOO{whatever/path}\input thisfile'

where thisfile.tex uses \FOO

 > Of course, a local structure mirroring the texmf tree structure
 > which allowed KPATHSEA to do most of the work without changes might
 > be the most elegant. 
yes, that would be possible too, redefining TEXMFLOCAL for the
duration

  > Is any of this possible?

all of it. even better, forget the gnu coding standards while they
persist with something as horrible as texinfo..:-}

was that enough smilies to make sure Richard Stallman still sends me a
christmas card?

sebastian





Re: BOUNCE pdftex@tug.org: Non-member submission from ["Derek R. Price" ]

2000-12-19 Thread Raja R Harinath

"Derek R. Price" <[EMAIL PROTECTED]> writes:
> Sebastian Rahtz wrote:
> > [EMAIL PROTECTED] writes:
> >  > Assuming I have a texinfo.tex & a pdftexinfo.tex, both in '.', is there
> >  > some command that will allow 'texi2dvi foo.texi' and 'texi2dvi --pdf
> >  > foo.texi' to each find the appropriate texinfo.tex?
> >
> > surely the simpler answer is to put pdftexinfo.tex into the
> > texmf/pdftex tree, and call it texinfo.tex?
> 
> Actually, yeah, and that was my solution, but I was trying to help out the
> Automake folks who got me into this mess in the first place.  :)
> 
> Basically, the issue is that the GNU coding standards state that the
> texinfo.tex you built your docs with should be included with a source
> distribution so that an end user is sure to be able to build your docs too.
> So Automake attempts to force this issue and copy its texinfo.tex into any
> directory where docs are built unless it is overridden.  Unfortunately, if
> you are attempting to build both PDFs and other types of output in the same
> directory from the same source files, this would disable either the building
> of PDFs or it would disable everything else.

Actually, new versions of texinfo.tex from ftp.gnu.org seem to not
need a special pdftexinfo.tex.

- Hari
-- 
Raja R Harinath -- [EMAIL PROTECTED]
"When all else fails, read the instructions."  -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash




Re: BOUNCE pdftex@tug.org: Non-member submission from ["Derek R. Price" ]

2000-12-19 Thread Derek R. Price

Sebastian Rahtz wrote:

> [EMAIL PROTECTED] writes:
>  >
>  > Assuming I have a texinfo.tex & a pdftexinfo.tex, both in '.', is there
>  > some command that will allow 'texi2dvi foo.texi' and 'texi2dvi --pdf
>  > foo.texi' to each find the appropriate texinfo.tex?
>  >
>
> surely the simpler answer is to put pdftexinfo.tex into the
> texmf/pdftex tree, and call it texinfo.tex?

Actually, yeah, and that was my solution, but I was trying to help out the
Automake folks who got me into this mess in the first place.  :)

Basically, the issue is that the GNU coding standards state that the
texinfo.tex you built your docs with should be included with a source
distribution so that an end user is sure to be able to build your docs too.
So Automake attempts to force this issue and copy its texinfo.tex into any
directory where docs are built unless it is overridden.  Unfortunately, if
you are attempting to build both PDFs and other types of output in the same
directory from the same source files, this would disable either the building
of PDFs or it would disable everything else.

Anyway, I was hoping for a solution compatible with the current GNU coding
standard short of putting pdftexinfo.tex & texinfo.tex in different
directories and overriding the TEXINPUTS path dependent on the target or
barbarically renaming the files before calling texi2dvi.  Aesthetically,
I think coding the filename switch inside the *texi source file would be most
pleasing, as the Makefile structure never has to distinguish between targets
except to supply the --pdf switch, and being able to specify a complete path
to a *texinfo.tex on the command line would be second best since it would
avoid the forced creation of extra directories.

Of course, a local structure mirroring the texmf tree structure which allowed
KPATHSEA to do most of the work without changes might be the most elegant.
Is any of this possible?

Derek

--
Derek Price  CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
Conscious is what you are aware of and conscience is what you wish you
weren't.







./configure & .deps directory

2000-12-19 Thread Derek R. Price

Is there a good reason the configure script creates
$(top_builddir)/.deps during the test that sets $DEPDIR and doesn't
delete it again?  Besides some developer or other needing sleep?  ;)

My distribution certainly doesn't seem to need that directory sitting
around...

Derek

--
Derek Price  CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
I will not spank others.
I will not spank others.
I will not spank others...

  - Bart Simpson on chalkboard, _The Simpsons_







error in config.sub

2000-12-19 Thread Tomas Berndtsson

For the MiNT system, the lines in config.sub are wrong. It's missing
the '*'-wildcard. I've applied a patch below.


Greetings,

Tomas



--- /usr/share/automake/config.sub~ Sat Sep  2 16:05:51 2000
+++ /usr/share/automake/config.sub  Tue Dec 19 17:44:48 2000
@@ -985,7 +985,7 @@
-xenix)
os=-xenix
;;
--*mint | -*MiNT)
+-*mint* | -*MiNT*)
os=-mint
;;
-none)