1 |
Apparently, though unproven, at 11:54 on Tuesday 02 November 2010, Gary Golden |
2 |
did opine thusly: |
3 |
|
4 |
> On 11/02/2010 12:08 PM, Daniel Pielmeier wrote: |
5 |
> > 2010/11/2 Gary Golden <mail@××××××××××.me>: |
6 |
> >> Hi, list. |
7 |
> >> I keep changes of my /etc with git and I would like to include |
8 |
> >> /var/lib/portage/world file into the repository. |
9 |
> >> |
10 |
> >> Can I safely do: |
11 |
> >> |
12 |
> >> mv /var/lib/portage/world /etc/portage |
13 |
> >> ln -s /etc/portage /var/lib/portage/world |
14 |
> >> |
15 |
> >> Will portage update handle it properly? |
16 |
> >> Using hardlinks seems to be more cleaner way, but for some reason I |
17 |
> >> don't want to use it for this task. |
18 |
> > |
19 |
> > It should work. Just try it out, but make a copy of your world file |
20 |
> > before. Should be easy to switch back if anything fails. |
21 |
> > |
22 |
> > Afaik, the creation of the symbolic link should look like this: |
23 |
> > ln -s /etc/portage/world /var/lib/portage/world |
24 |
> |
25 |
> Thanks for the correction, you're right, of course. |
26 |
> Nevertheless, I've considered that using hardlinks is most porper way to |
27 |
> solve this task. It basically do what I need, make another reference to |
28 |
> the file under needed directory; without introducing compexity. |
29 |
|
30 |
|
31 |
hard links will only work if /etc/portage and /var/lib/portage are on the same |
32 |
filesystem. Frequently, they are not. |
33 |
|
34 |
|
35 |
-- |
36 |
alan dot mckinnon at gmail dot com |