| 1 |
On Fri, Feb 10, 2017 at 4:52 PM, Harry Putnam <reader@×××××××.com> wrote: |
| 2 |
> |
| 3 |
> What is really puzzling is the the words `reconfigure' that package. |
| 4 |
> But then there is nothing said about what this `reconfiguring' |
| 5 |
> consists of. |
| 6 |
> |
| 7 |
> It used to be we just either copied the appropriate zimezone section |
| 8 |
> to /etc/localtime... or symlinked it there. |
| 9 |
> |
| 10 |
> Can anyone explain what is meant by `reconfiguring' in this context or |
| 11 |
> how it is done? |
| 12 |
> |
| 13 |
|
| 14 |
emerge --config sys-libs/timezone-data |
| 15 |
|
| 16 |
All it does is copy the timezone data to /etc/localtime. |
| 17 |
|
| 18 |
Setting /etc/timezone is still important, because it ensures that |
| 19 |
anytime the package is updated the new data is copied over (a symlink |
| 20 |
would also accomplish this). |
| 21 |
|
| 22 |
Using emerge --config is a bit more elegant since it will tell you if |
| 23 |
you made any mistakes in /etc/timezone, and perhaps at some point in |
| 24 |
the future it might do other things. But, you are correct that the |
| 25 |
instructions used to just say to copy the file and be done with it, |
| 26 |
and there is no real harm in doing it that way. Just introducing |
| 27 |
users to emerge --config probably has a little value in it. |
| 28 |
|
| 29 |
-- |
| 30 |
Rich |
Archives