[texdoc] running from svn

[Manuel Pégourié-Gonnard]

Karl Berry a écrit :
>     I'd say symlink it into TEXMFLOCAL/texdoc.
> 
> Well, that loses on systems where TEXMFLOCAL is shared among many
> users.  But I guess symlinking into TEXMFHOME would work as well.
> 
Sure. I was suggesting TEXMFLOCAL so that you could still use TEXMFHOME
for you real personal settings.

> But that interacts with my other question, about a ~/.texdoc.cnf.
> Here's my situation: naturally, I want to run texdoc from svn (both
> texdoc svn and tl svn present the same issues), so I can be maximally
> buggy :).
> 
A very natural need indeed: what's the point in being involved in a
project if you cannot benefit from the news bugs before others? ,)

> However, I also want to set interact_switch=false (I hate being asked, I
> just want the list, thanks), and my own viewer_pdf (I hate evince,
> thanks).  I don't argue with the defaults; I just want to be able to
> override them.
> 
Sure.

> You guys say I should just set up a TEXMFHOME.  I don't like it, but I
> guess it can work: I can put my settings into
> TEXMFHOME/texdoc/texdoc-i386-linux.cnf and 
> symlink TEXMFHOME/texdoc/texdoc.cnf to the svn texdoc.cnf.  It is rather
> abusing the platform cnf file, though.
> 
Oh, suddenly I can see some use to ~/.texdoc.cnf in addition to
~/texmf/texdoc/texdoc.cnf. This platform-cnf abuse sounds rather... err...

Manuel.

PS : so ~/.texdoc.cnf whould have the greatest priority, right? The idea
being that the TEXMFHOME can be used for local updates on systems you're
using w/o admin privileges (that's the first use I made of it,
personally) (or don't want to make them globally), but a file lying
directly in your home is something really personal.