Source strings

14 Strings 100%
Browse Translate
429 Words 100%
3,228 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
14 429 3,228
All strings Browse Translate Zen
14 429 3,228
Read-only strings Browse Translate Zen

Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch 12.0
Last remote commit Add Portuguese (Brazil) BLFS 5a031b636f
Julien Lepiller authored 7 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-0/index/
File mask blfs/*/introduction/important/position.po
Translation file Not available
Last change Sept. 1, 2023, 6:16 a.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 14 429 3,228
Translated 100% 14 100% 429 100% 3,228
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 14 100% 429 100% 3,228
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 14 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

429
Hosted words
14
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Source string added
All of the BLFS instructions install programs in <filename class='directory'>/usr</filename> with optional instructions to install into <filename class='directory'>/opt</filename> for some specific packages.
a year ago
User avatar None

Source string added
<emphasis>What is the BLFS position on this?</emphasis>
a year ago
User avatar None

Source string added
There is nothing stopping you, many sites do make their own trees, however it makes installing new software more difficult. Automatic installers often look for dependencies in <filename class='directory'>/usr</filename> and <filename class='directory'>/usr/local</filename>, and if the file it is looking for is in <filename class='directory'>/usr/site</filename> instead, the installer will probably fail unless you specifically tell it where to look.
a year ago
User avatar None

Source string added
Some people ask why not use your own directory tree, e.g., <filename class='directory'>/usr/site</filename>, rather than <filename class='directory'>/usr/local</filename>?
a year ago
User avatar None

Source string added
Or you might regularly rebuild your LFS, but want a place to put files that you don't want to rebuild each time. This way you can wipe the LFS file system and start from a clean partition every time without losing everything.
a year ago
User avatar None

Source string added
Even on a single computer, <filename class='directory'>/usr/local</filename> can be useful if you have several distributions installed simultaneously, and want a place to put packages that will be the same on all of them.
a year ago
User avatar None

Source string added
On a network of several computers all running an identical LFS system, <filename class='directory'>/usr/local</filename> could hold packages that are different between the machines. In this case local refers to the individual computers.
a year ago
User avatar None

Source string added
On a network of several machines all running LFS, or mixed LFS and other Linux distributions, <filename class='directory'>/usr/local</filename> could be used to hold packages that are common between all the computers in the network. It can be NFS mounted or mirrored from a single server. Here local indicates local to the site.
a year ago
User avatar None

Source string added
LFS users build their own system and so deciding where the system ends and local files begin is not straightforward. So the choice should be made in order to make things easier to administer. There are several reasons for dividing files between <filename class='directory'>/usr</filename> and <filename class='directory'>/usr/local</filename>.
a year ago
User avatar None

Source string added
With Linux distributions like Red Hat, Debian, etc., a possible rule is that <filename class='directory'>/usr</filename> is managed by the distribution's package system and <filename class='directory'>/usr/local</filename> is not. This way the package manager's database knows about every file within <filename class='directory'>/usr</filename>.
a year ago
Browse all translation changes