public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* RE: texmf-related *.lnk files in /bin/ : invalid?
@ 2002-04-19  2:27 Robert Collins
  0 siblings, 0 replies; 2+ messages in thread
From: Robert Collins @ 2002-04-19  2:27 UTC (permalink / raw)
  To: fergus, cygwin

Setup create the .lnk style symbolic shortcuts based on the tar file
contents. Nothing is brojen, nothing needs changing, norton is making
assumptions.

If it is of enough concern, the tar file creator could alter their
symlinks before they create the tarball to reference the .exe's instead.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* texmf-related *.lnk files in /bin/ : invalid?
@ 2002-04-19  1:16 fergus
  0 siblings, 0 replies; 2+ messages in thread
From: fergus @ 2002-04-19  1:16 UTC (permalink / raw)
  To: cygwin; +Cc: fergus

Using W98 after a complete install including texmf* : then, one of Norton's
diagnostic checking procedures picked up 5 *.lnk files in /bin/ as "invalid
shortcuts". They are
        elatex.lnk, pdflatex.lnk, pdfelatex.lnk, lambda.lnk, latex.lnk.
They seem to be intended links to
        etex.exe, pdftex.exe, pdfetex.exe, omega.exe, tex.exe,
respectively. They are binaries so it is difficult to check their syntax. I
would not have been bothered by Norton's diagnostics if several other items
of (what seem to me to be) similar status such as
        pdfinitex, pdfeinitex, ...
had failed the check too; but they passed. So, could (should?) the binary
file elatex.lnk (and the other 4, similarly) be turned into one-line text
files containing the line
    !<symlink>etex
(and pdftex, pdfetex, omega, tex, similarly), then renamed without the .lnk
extension, and then given the +s (not +r) attribute? That way they might
achieve the same purpose as is presently intended, but without tripping up
Norton (and other?) diagnostics programs?
I am very _very_ sorry if I am talking complete and utter rubbish and that
this tweak, if implemented, would break what currently isn't broken. Then I
would deserve to be (and would expect to be) admonished. But, if it would
tidy what is presently untidy (as it seems to me to that it might do) would
it be possible in this case to implement the tweak at source?
Fergus


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-04-19  8:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-19  2:27 texmf-related *.lnk files in /bin/ : invalid? Robert Collins
  -- strict thread matches above, loose matches on Subject: below --
2002-04-19  1:16 fergus

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).