I know understand the TeX distribution a bit better. There is an installer which can be used to download only needed packages. But if a decent subset is installed it will still be several 100 of MB, so for puppy it is better to install this as an sfs file.

I have prepackaged the following (from small to large, small packages are subsets of the larger ones):

There is an installer which can be used to download a custom package. It is fine for full install puppies, but for frugal installs it is not straightforward how to avoid full savefiles/disks and to build a custom sfs package (it's not too difficult either).
install-tl-unx.tar.gz

To build an automated custom texlive sfs creator would be a nice little project ...
kind regards
EmilLast edited by emil on Mon 19 Dec 2011, 03:42; edited 1 time in total

About the Path /usr/local/texlive ... it is the original path were the texlive installer puts the files. I am somewhat against placing a package in the / domain. I suggest the package stays in /usr/local. Is there any particular reason why you want it to be in /texlive?
About the environment variables - Do we need them if we leave the package in the default location? Where does it fail without them?
I also see now that the original error you reported probably originated from shifting the package out of its original place - That's a small? detail you should mention if you report an assumed error . I spent considerable time (installed 2 puppies to test them with the package) when I tried to reproduce the "failure".

Is it necessary to put texmf-local etc to /root/.texlive ?
I could see an eventual advantage if texlive is used in a multiuser environment. But in the usual puppy linux use case as a single user desktop only system?

and are the directories automatically created by texlive if need arises? Otherways this would complicate the situation - the root/.texlive directory can be included in the sfs, but I don't know how to handle additional users.

about updmap: I removed docs and sources from the packages, so this is where I probably also removed updmap. The original idea was to have sfs packages which do not change. If you want an updateable package it is better to install texlive somewhere to your hd (in Full mode) and symlink it the way you prefer it (even in /texlive). Otherways it will clobber your savefile pretty quick.

I see this as an discussion process, because I do not have enough experience with TeX to objectivly decide how that package is used best in puppy. I thought for most people it is enough to have a static version which can be put into a comparatively small sfs (so also the reuse in various puppy installations is easy and standard). Please understand that I am not completely against changing the packages, but it is a lot of work (unpacking, uploading, checking - big files) and at the moment I don't see objective reason beside your personal preference (which I don't share).

An alternative project would be to wrap the texlive installer in a "puppy tex installer script" (with GUI?), which allows to choose for build of a customized sfs or alternatively a customized full, upgradable hd install.

Take care
emilLast edited by emil on Mon 19 Dec 2011, 03:49; edited 2 times in total

I just wanted to add and clarify, that also the user specific customisation files (including the directories texmf-local and texmf-var) are generated in $HOME/.texlive correctly with the published sfs.

I tested this with user root and also with user sageadmin (I have included this user in my Sage Live puplet). After installing the devx and running updmap there are specific files in the $HOME directories.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum