texmf-local and texmf in the context of backup and restore of a TeX Live installationBacking up and restoring...
I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine
Suffixes -unt and -ut-
A Journey Through Space and Time
Find original functions from a composite function
Continuity at a point in terms of closure
How to type dʒ symbol (IPA) on Mac?
How is this relation reflexive?
GPS Rollover on Android Smartphones
Theorems that impeded progress
Shell script can be run only with sh command
How old can references or sources in a thesis be?
If I cast Expeditious Retreat, can I Dash as a bonus action on the same turn?
Why are 150k or 200k jobs considered good when there are 300k+ births a month?
Infinite past with a beginning?
Question about Goedel's incompleteness Proof
What is the command to reset a PC without deleting any files
Do Phineas and Ferb ever actually get busted in real time?
How can the DM most effectively choose 1 out of an odd number of players to be targeted by an attack or effect?
Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)
What do you call a Matrix-like slowdown and camera movement effect?
Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?
What defenses are there against being summoned by the Gate spell?
A function which translates a sentence to title-case
Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?
texmf-local and texmf in the context of backup and restore of a TeX Live installation
Backing up and restoring texlive 2011 (Linux)How to use the Luximono font with TeX Live?How to configure kile to run texlive 2011?Hebrew TeXLive on Ubuntu 12.04 missing fontsProblem With updmap-sysCreate a local texmf tree in UbuntuCannot set local Tex path on ubuntu with “vanilla” TeX LiveDifference between tex.fmt and plain.fmt in TeX LiveHow to incorporate a TEXMF tree managed by distro's package manager when using TeX Live from upstream on a GNU/Linux system?Manually upgrading TeXLive version?What are the latex and dvips path in jaxodraw preferences?
TeX Live 2018 is currently frozen and TL 2019 is soon to come out, and I'd like to start in the practice of backing up my old TeX Live installations. I don't usually uninstall them, but as system maintenance goes, they eventually get lost on a fresh install which happens every once in a while.
I've seen Backing up and restoring texlive 2011 (Linux) which, as far as I know, remains up to date. However, the advice there is to backup the whole texlive tree (in /usr/local/texlive by default on Unix). That plus anything you have in ~/texmf.
Those directories are described in the TeX Live documentation as:
TEXMFLOCAL
The tree which administrators can use for system-wide installation of additional or updated macros, fonts, etc.
TEXMFHOME
The tree which users can use for their own individual installations of additional or updated macros, fonts, etc. The expansion of this variable dynamically adjusts for each user to their own individual directory.
Adding, for TEXMFLOCAL:
texmf-local
TEXMFLOCAL, intended to be retained from release to release.
Which is naturally the case also of TEXMFHOME.
Now, in practice, this means the root texlive tree will have directories 2018 and texmf-local. When I install TL 2019, it will be 2018, 2019 and texmf-local. texmf in your home directory.
How should I proceed to back this up, in the hope of being able to completely reproduce the state of my current TeX Live installation in the future, and being able to restore this without messing the installation which will be then in place?
Is it enough to backup /usr/local/texlive/2018? (I'd say: no).
Being texmf-local and ~texmf needed, how to restore them without breaking the installation in place? And, considering the eventual need of a restore, what would be the best practice for backing them up in the first place? (Well, "best practice" might be too strong here, if so, "convenience tips" might convey it.)
Another related issue, particularly for the case of texmf-local. Must the backup of TL 2018 be made before the installation of TL 2019?
texlive
asked 9 hours ago
gusbrsgusbrs
8,0742842
|
show 1 more comment
TeX Live 2018 is currently frozen and TL 2019 is soon to come out, and I'd like to start in the practice of backing up my old TeX Live installations. I don't usually uninstall them, but as system maintenance goes, they eventually get lost on a fresh install which happens every once in a while.
I've seen Backing up and restoring texlive 2011 (Linux) which, as far as I know, remains up to date. However, the advice there is to backup the whole texlive tree (in /usr/local/texlive by default on Unix). That plus anything you have in ~/texmf.
Those directories are described in the TeX Live documentation as:
TEXMFLOCAL
The tree which administrators can use for system-wide installation of additional or updated macros, fonts, etc.
TEXMFHOME
The tree which users can use for their own individual installations of additional or updated macros, fonts, etc. The expansion of this variable dynamically adjusts for each user to their own individual directory.
Adding, for TEXMFLOCAL:
texmf-local
TEXMFLOCAL, intended to be retained from release to release.
Which is naturally the case also of TEXMFHOME.
Now, in practice, this means the root texlive tree will have directories 2018 and texmf-local. When I install TL 2019, it will be 2018, 2019 and texmf-local. texmf in your home directory.
How should I proceed to back this up, in the hope of being able to completely reproduce the state of my current TeX Live installation in the future, and being able to restore this without messing the installation which will be then in place?
Is it enough to backup /usr/local/texlive/2018? (I'd say: no).
Being texmf-local and ~texmf needed, how to restore them without breaking the installation in place? And, considering the eventual need of a restore, what would be the best practice for backing them up in the first place? (Well, "best practice" might be too strong here, if so, "convenience tips" might convey it.)
Another related issue, particularly for the case of texmf-local. Must the backup of TL 2018 be made before the installation of TL 2019?
texlive
asked 9 hours ago
gusbrsgusbrs
8,0742842
1
If you want entirely independent installs, you'll want to redirect the local dirs ...
– Joseph Wright♦
9 hours ago
@JosephWright I'm happy with the idea oftexmf-local(that is, of keeping some things common to each release). It is just that the purpose of making one such backup is to reproduce the current state of the TL installation, so I'd say it should be included in the backup. And simply restoring the backup will overwrite any following installation. Or, perhaps, I misunderstand what you mean by "redirecting the local dirs"...
– gusbrs
9 hours ago
One thing I might be getting wrong. I don't really know what is included intexmf-localby default. I know it is created by the installation, with corresponding subdirectories. But I am in a single user machine, and can tell you that "the administrator" did not add anything there. So, the answer in this case might well be that I simply don't need it. Is it?
– gusbrs
9 hours ago
In prep for such a significant change the /2018 /2019 would itself not be the issue it depends if you have active settings say for graphicsdir or texinputs that you may wish to duplicate related folders to texmf-local18 /temf18 and copy to /texmf-local19 /texmf19 so that they can be reassigned at will to TEXMFLOCAL and TEXMFHOME but remember that may require a system or user restart for tlmgr to not use the wrong one during each session. the downside of this approach is potential for each var having 3 conflicting locations ..18 ..19 & default when you don't remember to change env-vars together
– KJO
9 hours ago
1
Personally not the best to ask as I unusually use them to switch between different distros (MiKTeX/Live/W32) so am sometimes caught out by cross contamination if I forget to switch with caution :-) IF you are a stable user it may for you to be simpler to have a safety rollback copy of the one most likely to be affected (texmf-local) then if needs be save the 2019 local folder when replacing from 2018 rollback contents as you first hinted at. That could be done by very simple rename texmf-local to texmf-2019 and copy 2018 rollback to texmf-local and so forth.
– KJO
8 hours ago
|
show 1 more comment
TeX Live 2018 is currently frozen and TL 2019 is soon to come out, and I'd like to start in the practice of backing up my old TeX Live installations. I don't usually uninstall them, but as system maintenance goes, they eventually get lost on a fresh install which happens every once in a while.
I've seen Backing up and restoring texlive 2011 (Linux) which, as far as I know, remains up to date. However, the advice there is to backup the whole texlive tree (in /usr/local/texlive by default on Unix). That plus anything you have in ~/texmf.
Those directories are described in the TeX Live documentation as:
TEXMFLOCAL
The tree which administrators can use for system-wide installation of additional or updated macros, fonts, etc.
TEXMFHOME
The tree which users can use for their own individual installations of additional or updated macros, fonts, etc. The expansion of this variable dynamically adjusts for each user to their own individual directory.
Adding, for TEXMFLOCAL:
texmf-local
TEXMFLOCAL, intended to be retained from release to release.
Which is naturally the case also of TEXMFHOME.
Now, in practice, this means the root texlive tree will have directories 2018 and texmf-local. When I install TL 2019, it will be 2018, 2019 and texmf-local. texmf in your home directory.
How should I proceed to back this up, in the hope of being able to completely reproduce the state of my current TeX Live installation in the future, and being able to restore this without messing the installation which will be then in place?
Is it enough to backup /usr/local/texlive/2018? (I'd say: no).
Being texmf-local and ~texmf needed, how to restore them without breaking the installation in place? And, considering the eventual need of a restore, what would be the best practice for backing them up in the first place? (Well, "best practice" might be too strong here, if so, "convenience tips" might convey it.)
Another related issue, particularly for the case of texmf-local. Must the backup of TL 2018 be made before the installation of TL 2019?
texlive
asked 9 hours ago
gusbrsgusbrs
8,0742842
TeX Live 2018 is currently frozen and TL 2019 is soon to come out, and I'd like to start in the practice of backing up my old TeX Live installations. I don't usually uninstall them, but as system maintenance goes, they eventually get lost on a fresh install which happens every once in a while.
I've seen Backing up and restoring texlive 2011 (Linux) which, as far as I know, remains up to date. However, the advice there is to backup the whole texlive tree (in /usr/local/texlive by default on Unix). That plus anything you have in ~/texmf.
Those directories are described in the TeX Live documentation as:
TEXMFLOCAL
The tree which administrators can use for system-wide installation of additional or updated macros, fonts, etc.
TEXMFHOME
The tree which users can use for their own individual installations of additional or updated macros, fonts, etc. The expansion of this variable dynamically adjusts for each user to their own individual directory.
Adding, for TEXMFLOCAL:
texmf-local
TEXMFLOCAL, intended to be retained from release to release.
Which is naturally the case also of TEXMFHOME.
Now, in practice, this means the root texlive tree will have directories 2018 and texmf-local. When I install TL 2019, it will be 2018, 2019 and texmf-local. texmf in your home directory.
How should I proceed to back this up, in the hope of being able to completely reproduce the state of my current TeX Live installation in the future, and being able to restore this without messing the installation which will be then in place?
Is it enough to backup /usr/local/texlive/2018? (I'd say: no).
Being texmf-local and ~texmf needed, how to restore them without breaking the installation in place? And, considering the eventual need of a restore, what would be the best practice for backing them up in the first place? (Well, "best practice" might be too strong here, if so, "convenience tips" might convey it.)
Another related issue, particularly for the case of texmf-local. Must the backup of TL 2018 be made before the installation of TL 2019?
texlive
texlive
asked 9 hours ago
gusbrsgusbrs
8,0742842
asked 9 hours ago
gusbrsgusbrs
8,0742842
asked 9 hours ago
gusbrsgusbrs
8,0742842
asked 9 hours ago
gusbrsgusbrs
8,0742842
asked 9 hours ago
gusbrsgusbrs
8,0742842
8,0742842
1
If you want entirely independent installs, you'll want to redirect the local dirs ...
– Joseph Wright♦
9 hours ago
@JosephWright I'm happy with the idea oftexmf-local(that is, of keeping some things common to each release). It is just that the purpose of making one such backup is to reproduce the current state of the TL installation, so I'd say it should be included in the backup. And simply restoring the backup will overwrite any following installation. Or, perhaps, I misunderstand what you mean by "redirecting the local dirs"...
– gusbrs
9 hours ago
One thing I might be getting wrong. I don't really know what is included intexmf-localby default. I know it is created by the installation, with corresponding subdirectories. But I am in a single user machine, and can tell you that "the administrator" did not add anything there. So, the answer in this case might well be that I simply don't need it. Is it?
– gusbrs
9 hours ago
In prep for such a significant change the /2018 /2019 would itself not be the issue it depends if you have active settings say for graphicsdir or texinputs that you may wish to duplicate related folders to texmf-local18 /temf18 and copy to /texmf-local19 /texmf19 so that they can be reassigned at will to TEXMFLOCAL and TEXMFHOME but remember that may require a system or user restart for tlmgr to not use the wrong one during each session. the downside of this approach is potential for each var having 3 conflicting locations ..18 ..19 & default when you don't remember to change env-vars together
– KJO
9 hours ago
1
Personally not the best to ask as I unusually use them to switch between different distros (MiKTeX/Live/W32) so am sometimes caught out by cross contamination if I forget to switch with caution :-) IF you are a stable user it may for you to be simpler to have a safety rollback copy of the one most likely to be affected (texmf-local) then if needs be save the 2019 local folder when replacing from 2018 rollback contents as you first hinted at. That could be done by very simple rename texmf-local to texmf-2019 and copy 2018 rollback to texmf-local and so forth.
– KJO
8 hours ago
|
show 1 more comment
1
If you want entirely independent installs, you'll want to redirect the local dirs ...
– Joseph Wright♦
9 hours ago
@JosephWright I'm happy with the idea oftexmf-local(that is, of keeping some things common to each release). It is just that the purpose of making one such backup is to reproduce the current state of the TL installation, so I'd say it should be included in the backup. And simply restoring the backup will overwrite any following installation. Or, perhaps, I misunderstand what you mean by "redirecting the local dirs"...
– gusbrs
9 hours ago
One thing I might be getting wrong. I don't really know what is included intexmf-localby default. I know it is created by the installation, with corresponding subdirectories. But I am in a single user machine, and can tell you that "the administrator" did not add anything there. So, the answer in this case might well be that I simply don't need it. Is it?
– gusbrs
9 hours ago
In prep for such a significant change the /2018 /2019 would itself not be the issue it depends if you have active settings say for graphicsdir or texinputs that you may wish to duplicate related folders to texmf-local18 /temf18 and copy to /texmf-local19 /texmf19 so that they can be reassigned at will to TEXMFLOCAL and TEXMFHOME but remember that may require a system or user restart for tlmgr to not use the wrong one during each session. the downside of this approach is potential for each var having 3 conflicting locations ..18 ..19 & default when you don't remember to change env-vars together
– KJO
9 hours ago
1
Personally not the best to ask as I unusually use them to switch between different distros (MiKTeX/Live/W32) so am sometimes caught out by cross contamination if I forget to switch with caution :-) IF you are a stable user it may for you to be simpler to have a safety rollback copy of the one most likely to be affected (texmf-local) then if needs be save the 2019 local folder when replacing from 2018 rollback contents as you first hinted at. That could be done by very simple rename texmf-local to texmf-2019 and copy 2018 rollback to texmf-local and so forth.
– KJO
8 hours ago
1
1
If you want entirely independent installs, you'll want to redirect the local dirs ...
– Joseph Wright♦
9 hours ago
If you want entirely independent installs, you'll want to redirect the local dirs ...
– Joseph Wright♦
9 hours ago
@JosephWright I'm happy with the idea of
texmf-local (that is, of keeping some things common to each release). It is just that the purpose of making one such backup is to reproduce the current state of the TL installation, so I'd say it should be included in the backup. And simply restoring the backup will overwrite any following installation. Or, perhaps, I misunderstand what you mean by "redirecting the local dirs"...– gusbrs
9 hours ago
@JosephWright I'm happy with the idea of
texmf-local (that is, of keeping some things common to each release). It is just that the purpose of making one such backup is to reproduce the current state of the TL installation, so I'd say it should be included in the backup. And simply restoring the backup will overwrite any following installation. Or, perhaps, I misunderstand what you mean by "redirecting the local dirs"...– gusbrs
9 hours ago
One thing I might be getting wrong. I don't really know what is included in
texmf-local by default. I know it is created by the installation, with corresponding subdirectories. But I am in a single user machine, and can tell you that "the administrator" did not add anything there. So, the answer in this case might well be that I simply don't need it. Is it?– gusbrs
9 hours ago
One thing I might be getting wrong. I don't really know what is included in
texmf-local by default. I know it is created by the installation, with corresponding subdirectories. But I am in a single user machine, and can tell you that "the administrator" did not add anything there. So, the answer in this case might well be that I simply don't need it. Is it?– gusbrs
9 hours ago
In prep for such a significant change the /2018 /2019 would itself not be the issue it depends if you have active settings say for graphicsdir or texinputs that you may wish to duplicate related folders to texmf-local18 /temf18 and copy to /texmf-local19 /texmf19 so that they can be reassigned at will to TEXMFLOCAL and TEXMFHOME but remember that may require a system or user restart for tlmgr to not use the wrong one during each session. the downside of this approach is potential for each var having 3 conflicting locations ..18 ..19 & default when you don't remember to change env-vars together
– KJO
9 hours ago
In prep for such a significant change the /2018 /2019 would itself not be the issue it depends if you have active settings say for graphicsdir or texinputs that you may wish to duplicate related folders to texmf-local18 /temf18 and copy to /texmf-local19 /texmf19 so that they can be reassigned at will to TEXMFLOCAL and TEXMFHOME but remember that may require a system or user restart for tlmgr to not use the wrong one during each session. the downside of this approach is potential for each var having 3 conflicting locations ..18 ..19 & default when you don't remember to change env-vars together
– KJO
9 hours ago
1
1
Personally not the best to ask as I unusually use them to switch between different distros (MiKTeX/Live/W32) so am sometimes caught out by cross contamination if I forget to switch with caution :-) IF you are a stable user it may for you to be simpler to have a safety rollback copy of the one most likely to be affected (texmf-local) then if needs be save the 2019 local folder when replacing from 2018 rollback contents as you first hinted at. That could be done by very simple rename texmf-local to texmf-2019 and copy 2018 rollback to texmf-local and so forth.
– KJO
8 hours ago
Personally not the best to ask as I unusually use them to switch between different distros (MiKTeX/Live/W32) so am sometimes caught out by cross contamination if I forget to switch with caution :-) IF you are a stable user it may for you to be simpler to have a safety rollback copy of the one most likely to be affected (texmf-local) then if needs be save the 2019 local folder when replacing from 2018 rollback contents as you first hinted at. That could be done by very simple rename texmf-local to texmf-2019 and copy 2018 rollback to texmf-local and so forth.
– KJO
8 hours ago
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483663%2ftexmf-local-and-texmf-in-the-context-of-backup-and-restore-of-a-tex-live-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483663%2ftexmf-local-and-texmf-in-the-context-of-backup-and-restore-of-a-tex-live-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
If you want entirely independent installs, you'll want to redirect the local dirs ...
– Joseph Wright♦
9 hours ago
@JosephWright I'm happy with the idea of
texmf-local(that is, of keeping some things common to each release). It is just that the purpose of making one such backup is to reproduce the current state of the TL installation, so I'd say it should be included in the backup. And simply restoring the backup will overwrite any following installation. Or, perhaps, I misunderstand what you mean by "redirecting the local dirs"...– gusbrs
9 hours ago
One thing I might be getting wrong. I don't really know what is included in
texmf-localby default. I know it is created by the installation, with corresponding subdirectories. But I am in a single user machine, and can tell you that "the administrator" did not add anything there. So, the answer in this case might well be that I simply don't need it. Is it?– gusbrs
9 hours ago
In prep for such a significant change the /2018 /2019 would itself not be the issue it depends if you have active settings say for graphicsdir or texinputs that you may wish to duplicate related folders to texmf-local18 /temf18 and copy to /texmf-local19 /texmf19 so that they can be reassigned at will to TEXMFLOCAL and TEXMFHOME but remember that may require a system or user restart for tlmgr to not use the wrong one during each session. the downside of this approach is potential for each var having 3 conflicting locations ..18 ..19 & default when you don't remember to change env-vars together
– KJO
9 hours ago
1
Personally not the best to ask as I unusually use them to switch between different distros (MiKTeX/Live/W32) so am sometimes caught out by cross contamination if I forget to switch with caution :-) IF you are a stable user it may for you to be simpler to have a safety rollback copy of the one most likely to be affected (texmf-local) then if needs be save the 2019 local folder when replacing from 2018 rollback contents as you first hinted at. That could be done by very simple rename texmf-local to texmf-2019 and copy 2018 rollback to texmf-local and so forth.
– KJO
8 hours ago