> Date: Mon, 13 Jan 2014 20:09:19 +0100
> From: Magnus Larsson <[email protected]>
> To: BLFS Support List <[email protected]>
> Subject: Re: [blfs-support] No latex command? texlive-20130530
>
.
.
> >> The scripts keep asking for /opt/texmf-dist..,
> >> /home/magnus/opt/texmf-dist/scripts/texlive, but such a directory was
> >> not created after make install.
> >
> >
> > Is there a directory or symlink called 'texmf-dist' in the filesystem:
> > $ find -P / -iname 'texmf-dist' \( -type d -o -type l \) -ls
> >
I kno' u said "but such a directory was not created after make install":
but I wasn't sure exactly how 'rigourously' you were meaning that (e.g.
did you just mean that it's (obv) not at /opt/texmf-dist , nor under
/home/magnus/ , etc); and so the above find() was just to check the whole
filesys, in case it had been created somewhere else. Anyway, no need to
run that cmd now, I'd say, given the wider picture established of how
much more involved the inst may be.
> >
.
.
> > Reading the blfs-svn-texlive page
> > ('http://www.linuxfromscratch.org/blfs/view/svn/pst/texlive.html') again,
> > I'm
> > again wondering if the "At this point the installation is complete. If
> > building from source is desired, extract the source package as usual and
> > continue." is perhaps slightly misleading (no offence to anyone if that
> > impression is wrong): for, e.g., for cmmi install I'd kindof expect you
> > might
> > still need to do the 'pathappend' stuff shown above that point in the page.
>
> You are right. There is apparently much more to do besides configure,
> make and make install. The BLFS Book starts with the installer. The
> source build as stated, is for updating the applications in "bin".
>
Do feel free to come back to list and post what you'd say would be any
adjustments to the blfs-texlive page, in order - if nec - that it work
better for folks.
> Please find some feedback from [email protected]
>
> -------- Original Message --------
> Subject: Re: [tlbuild] Latex.fmt not found : texlive-20130530-source.tar.xz
> Date: Fri, 10 Jan 2014 13:36:46 -0800
> From: Paul Vojta <[email protected]>
> To: Magnus Larsson <[email protected]>
> CC: [email protected]
>
> Dear Mr. Larsson:
>
> Running "make" and "make install" are only the beginning.
>
> You also need to populate the texmf tree with all of the macros,
> configure various options (via texconfig-sys), run mklinks to create the
> symbolic links, and run
> fmtutil-sys --all
> and
> updmap-sys
>
> together with frequent runnings of mktexlsr.
>
> Mostly the source tree is there if you want to recompile something and
> replace a binary in an existing tex installation, or if you are repackaging
> TeX Live (e.g., for Debian Linux). If you want to do more than the former,
> then you'll need to learn more about how TeX runs. (I am not offering
> to teach you.)
>
> Sincerely,
>
> Paul Vojta
> ------- end -------
>
Yes, but it's dissatisfying to not be able to programmatically install a
package: so I wouldn't want to settle for interactive-installer-only
approaches.
> >
> >
> > What d'you get from:
> > $ set | grep -iE '(tex|path).*='
> I have just updated the PATH, to point to the "bin" directory in "dist"
> from ./Build (=configure, make, make install). This is probably not
> enough. The BLFS book updates only PATH, MANPATH and INFOPATH though.
>
((Usually in such a request, what's wanted is at least the output from the
command, and not solely description. But again, no need to do it now -
overtaken by events.))
rgds,
akh
--
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
