After a compile run (yes, I had to install automake and build-essential) the stuff is now properly put into /usr/local/share/tlf and /usr/local/bin, which is where it belongs.
During run time the philosophy is to create a separate working directory per contest and start tlf from there. I personally use a tree like: ~/tlf ~/tlf/qso ~/tlf/dxp_TS7N ~/tlf/dxp_ED8A ~/tlf/cqww2006 ~/tlf/cqww2007 ~/tlf/cqwpx2007 etc... and start tlf inside the relevant directory. There is a logcfg.dat in each of these directories to make sure tlf is configured for the relevant contest. Hope this helps, Rein > -----Ursprüngliche Nachricht----- > Von: <[EMAIL PROTECTED]> > Gesendet: 19.12.07 20:35:07 > An: <tlf-devel@nongnu.org> > Betreff: Re: [Tlf-devel] New bug fix release of tlf > > > >> > >> 3 - I can fix this with a wrapper script but all of the working files > >> are being dumped into ./ instead of a ~/tlf or ~/.tlf, which is o.k., > >> but is this a "new feature" or is this unintended ? > >> > > > > > > Forgot to tell, you need to run autoconf after changing configure.in > > > > > > Regards, > > Joop > > > Well, yes the aclocal is required AND automake as well, i.e. the code will > not configure or compile without using these tools. > > Item three is a *runtime* situation. Um, I also checked and it appears to > do this with the last version as well. Further notes on this: .paras, > tlfmarkers, and a cqww.log file are being dumped into whatever is the > 'working directory' during a "test run" of '/usr/bin/tlf' . > > SO.... I guess a wrapper script is in order IF there is not going to be a > ~/.tlf/ or ~/tlf/ for such things. > > > Vy 73; > > Bob > w9ya > > > > > > _______________________________________________ > Tlf-devel mailing list > Tlf-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/tlf-devel > > > -- http://pa0r.blogspirit.com _______________________________________________ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
