Re: [bug #46007] texi2dvi Msys support

[Vincent Belaïche]

Le 24/09/2015 12:33, Gavin Smith a écrit :
> On 23 September 2015 at 22:03, Vincent Belaïche
> <address@hidden> wrote:
>> Anyway, with the simple patch
>> https://savannah.gnu.org/bugs/download.php?file_id=34939 , texi2dvi
>> works with MikTeX for the basic case when users don't use TEXINPUTS-like
>> envvars.
>>
>> It would also work with this simple patch if the user:
>>
>> 1) sets the TeX envvars without tailing // and without empty dir in the
>>    middle, and
>> 2) the envvars are in MSYS format before calling texi2dvi (the
>>    conversion could be done by a not-so-thin wrapper)
>>
>> I have prepared another patch (see my previous emails):
>>
>> https://savannah.gnu.org/support/download.php?file_id=34966
>>
>> It is slightly more complex, but on the other hand that would allow
>> MSYS/texi2dvi compatibility in all cases. Its ticks is just to work
>> always in MSW style within texi2dvi for all filenames except for PATH,
>> so there aren't any conversions.
>
> I committed the simpler of these two patches.

Great, that is far enough for me as I don't use the TEXINPUTS-like
variables anyway for installed files (MikTeX has some interface to do
the same thing, and it makes compilation faster as the file name data
base has already some has), and for project files, when I don't place
everything in the same directory I rather user the command line argument
includes.

The only thing that I was asking it so be able to compile Texinfo
documents with all the options that the original texi2dvi offers (MikTeX's
 does not have --tidy).

:-)) Thank you for your immense patience w.r.t. those plague-stricken
users of that obsolete system named MSWindow. I don't like MSW either,
not for technical reasons, but because there is not guarantee that it
does not have any backdoor allowing the NSA to spy on you.

Back to texi2dvi and how to support MSYS, I would like to add that I
think that this is the right decision for consistency: the MSYS approach
is that MSYS does the conversion job so that you can write the script
exactly the same as in Linux. So it would be a paradox that for MSYS you
have more work and tricks to play. This means that what is missing is
rather some additional feature in MSYS to configure additional envvars
for conversion and the rules in use for conversion thereof. Ideally MSYS
should be like that, and texi2dvi would not care about MSW at all (be it
Cygwin, djgpp or MSYS), that should be ':' only for all (no path_sep
variable).

VBR,
        Vincent

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
http://www.avast.com