Re: Newbie Q - How to install a package?

Alan Ristow <ristow@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:tbidnW_bYOkw3FranZ2dnUVZ_vGinZ2d@xxxxxxxxxxxx:

<snip all>

Okay, I resolved my initial question that is the top post to this
thread. Here I my notes should they be of any benefit to another newbie
faced with the same problem.

These notes are directed towards other such newbies. I hope the
extended post is not bothersome to you more experienced users.

My own background is that I have used Wordperfect and MS-Word (I'll date
myself) going back to WP 1.0 and even Wordstar 1.0. I have had an
interest in Latex for some time and needing to write a formal science
paper, I wanted to also learn Latex and Tex. It seemed one way to get
started was to just use MikTex for ordinarily daily business
correspondence - letters, faxes, short memos. My descriptions below are
based on some analogies to commercial wordprocesser use.

Original problem and question was:

1) How do I make a local package directory so I can install any package
that I find in my MikTex system?

2) In what directory do you put a package to install it?

Basic objective was:

1) To be able to install and use template documents - example a basic
fax *** like the CTAN catalogue facsimile.zip file. The ability to
manage, use and particularize a template document is a basic function of
word processing software.

Problems not originally identified were:

1) The Package Manager was not connecting the internet.

2) The Package Manger kept on responding a local directory is not a
"recognized repository directory".

3) rsync command would not run from the command line.

Other questions that arose:

1) What is the correct directory on a Windows OS to put a local packages
repository?

2) How to WinEdt Template and Examples directories relate to MikTex
document directories.

Causes:

1) Newbie ignorance about basic MikTex structure.

2) An outdated MikTex version 2.4 on a Windows XP system.

Resolution:

I installed WinEdt and its associated MikTex version 2.4 from the WinEdt
site about a month ago.

The Package Manager would not connect to the internet and update. It
turned out that was caused by the older version of MikTex on my system.
I deinstalled and reinstalled the current version MikTex 2.7 (2/2008).
Then checking the WinEdt site, I noticed that the Win-Edit Team had just
issued a WinEdt update to version 5.5 was compatible through MikTex 2.7.
I deinstalled WinEdt and reinstalled the current WinEdt version 5.5.

I watched the MikTex install dialogue closely to see if it was creating
a local repository directory. During installation, MikiTex did create a
_temporary_ installation repository in the Windows C:\Documents and
Settings\ directory structure. However, this was a temporary folder
used for installation purposes only.

Once installed, tke the MikTex Settings utility listed some
configuration file directories in the Windows C:\Documents and Settings
\ hierarchy with the specific warning that "This directory is maintained
by MikTex. You should not install files in this directory." Under the
Settings utility, I also changed the option to install-packages-on-the-
fly to "Yes".

Once the new MikTex version 2.7 was installed, the Package Manager
started working properly and sought out a CTAN server at a local
university a couple of miles away. (The local CTAN server was at
math.utah.edu.)

I also ran the Update wizard to refresh all the package installations to
the most current versions.

Documentation on the MikTex site ( http://docs.miktex.org/packaging/ )
recommending using the following directory as a local package directory:

c:\packages-repository\

The documentation also suggested running from the command line the rysnc
function in order to synchronize the internet repository with the local
directory repository.

The resync command would not run and the Package Manager would not
recognize the c:\packages-repository directory. A poster here suggested
some cab files needed to be in the "c:\packages-repository" directory
for the Package Manager to function.

I used ftp and copied a couple of *.cab files from my default CTAN
package server into local directory "c:\packages-repository".

Then the Package Manager would recognize the "c:\packages-repository"
directory as a proper local packages repository.

At this point, I started questioning what I was doing, since the CTAN
internet repositories are always available.

Why make a local repository? My MikTex copy is installed on a laptop. I
work outside of wireless internet range ocassionally and cafe internet
connections frequently work intermittently when there are too many
laptop users in a cafe. Therefore, I decided that it would be a good
idea to have a complete copy of the CTAN packages server on my local
harddrive. That way, I would not be stuck rendering a Tex document if I
could not connect to the internet.

Using ftp, I made a complete copy of my nearby CTAN server mirror
packages to local directory "c:\packages-repository". Then I tested
installing and deinstalling a package using the internet CTAN server and
from the local packages repository directory. Then I set the default
Package Manager back to an internet connection with the idea of manually
updating the local "c:\packages-repository" directory every three
months.

For example, I was interested in using Torsten Bronger's simple fax
*** template package and to particularlize it for my contact
information. To use the package, launch Package Manager, find
"facsimile" on the list and install the package on your local MikTex
setup.

The next problem was, as a newbie, where do all the sample documents go
once installed and how do I use and particularize a template? I am
using WinEdt as the editor. WinEdt has its own set of document examples
and template directories.

If you are a true newbie and haven't used MikTex before, the short
answers on a Windows installation are:

A) The MikTex forms bank: C:\Program Files\MiKTeX 2.7\doc

Also see the WinEdt example forms: C:\Program Files\WinEdt Team\WinEdt
\Samples

This MikTex forms bank is the directory is where packages containing
templates get installed. If your sample template is a latex document,
the example will be in subdirectory of C:\Program Files\MiKTeX 2.7\doc
\latex\[my package template].

In each sample subdirectory is a pdf file that explains how to use the
form example. It includes tips on how to specially configure and
particularize the example for your personal needs.

For example, Torsten Bronger's fax ***, once installed with the
Package Manager, is in directory:

C:\Program Files\MiKTeX 2.7\doc\latex\facsimile\

The pdf file facsimile.pdf explains how to use the file.

Example.tex is the actual example fax ***.

I particularied the form using Torsten's instructions and saved a copy
as a personalized template named "KurtFax.tex".

B) WinEdt Templates directory: Where your particularized templates end
up.

The next question was, if I want to use that personalized template
repeatedly through my editor WinEdt, where does it go?

WinEdit has special directory - that parallels MikTex doc directory
system - called:

C:\Program Files\WinEdt Team\WinEdt\Templates

I copied my particularized fax (KurtFax.tex) and a configuration file
recommended Torsten (facsimile.cfg) by to the template directory:

C:\Program Files\WinEdt Team\WinEdt\Templates\Doc\facsimile

In WinEdt, you then install the template into WinEdt's popup fax menu
using Preferences | Templates. Use the preexisting templates in the
template setup dialogue as a guide to pointing a new entry to your fax
particularized fax template.

C) My Documents\MyMikTexDocs: Your working directory of your draft Tex
documents.


This directory is not mentioned in any MikTex or Tex manual. Once you
open your template and particularize it to send out a letter or fax, you
"save as" the text document in your working directory. This can be any
local or network directory used by yourself personally or your
organization. I use the My Documents hierarchy for consistency with the
Windows directory structure.

So for a fax, you would open the fax template described above,
particularize it and then "save as" the working document to your "My
Documents\MyMikiDocs\" directory, e.g. "FaxtoSmith2008-2.tex" .

To point WinEdt to your home working directory, in WinEdt use Options |
Configuration Wizard | Links and Shorcuts. Point WinEdt to a prefered
working directory like "My Documents\MyMikiDocs\". In the "Links and
Shorcuts" WinEdt settings dialogue, also check the checkboxes
"Persistent Startup Folder" and "Set Folder after loading file" to "on".
This will cause WinEdt to return directly to your "My Documents
\MyMikTexDocs" directory when the open template is saved. Otherwise,
WinEdt has the nuisance behaivor of going to the WinEdt Template
directory.

D) MikTex Packages Repository:

This is an internet url used by the Package Manager to automatically
distribute sample forms and to update the MikTex program.


As described above, you might also want to create a local hard drive
mirror - the directory "c:\packages-repository", so you can continue to
work in MikTex when not connected to the internet. The hassle of that
choice is you have to remember to manually update your local repository
mirror every couple of months.

Continuing Problems:


The one thing that did not work in above MikTex teething process was the
"Save As" for my particularlized Torsten Bronger's fax ***. To work
properly, the form requires a configuration file (*.cfg). A copy of that
configuration file needs to also be in the working directory - "My
Documents\MyMikTexDocs" in the example.

This can be fixed by hardcoding all particularizing information in a
frequently reused template in the template file itself. For example, I
went back into my personalize fax template "KurtFax.tex" and moved any
personalized information out of the facsimile.cfg file and put it into
the main template. Now when I want to due a quick fax and save a
completed fax in my working directory ("My Documents\MyMikTexdocs"), it
does not require the configuration file to print or review.

With the above, in WinEdt, I can now press the open template short cut
(SHIFT+CTRL+N) and quickly create a particularized template form. This
is analogous to the MS-Word and Wordperfect templates feature that works
with the same set of short-cut keys. I am on my way to creating other
commonly-used, particularlized templates for memos and letters with a
non-stressed workflow and ease of use similar to MS-Word or Wordperfect.

I hope the above helps some other poor newbie (like me) trying to break
into MikTex. Hats off to the MikTex and WinEdt Team people.

Any corrections or criticisms to the above by experience MikTex or
WinEdt users are welcomed and appreciated.

Regards and thanks to the more experienced users for the tips that
helped me get this far.

- Kurt


--
Posted via a free Usenet account from http://www.teranews.com

.

Quantcast