| 1 |
Dear Alexey, |
| 2 |
|
| 3 |
thanks a lot for your reply, now I get it. |
| 4 |
|
| 5 |
The path in 1st argument is relative to 2nd argument, and what I thought |
| 6 |
before was that it's relative to S="${workdir}". |
| 7 |
|
| 8 |
Best wishes |
| 9 |
|
| 10 |
|
| 11 |
|
| 12 |
Alexey Zapparov <alexey@××××××××.com> 于2022年7月23日周六 04:50写道： |
| 13 |
|
| 14 |
> `dosym target link_name` creates a symlink. Under the hood it calls `ln`. |
| 15 |
> First argument may be either absolute path or relative to link_name. |
| 16 |
> Conventionally relative targets are used. |
| 17 |
> |
| 18 |
> On Fri, 22 Jul 2022, 16:56 Fabulous Zhang Zheng, < |
| 19 |
> zheng1181822466@×××××.com> wrote: |
| 20 |
> |
| 21 |
>> Good evening, dear list |
| 22 |
>> |
| 23 |
>> Most binary package ebuilds have such a *dosym* statement in |
| 24 |
>> src_install(), take net-im/signal-desktop-bin as an example: |
| 25 |
>> |
| 26 |
>> dosym ../../opt/Signal/${MY_PN} /usr/bin/${MY_PN} (where the variable |
| 27 |
>> is signal-desktop) |
| 28 |
>> |
| 29 |
>> *dosym* creates a symlink of the binary under opt at /usr/bin/ according |
| 30 |
>> to devmanaul. |
| 31 |
>> |
| 32 |
>> I'm confused about the "../../", since S="${workdir}", the correct way |
| 33 |
>> seems to be "dosym ./opt/Signal/xxx /usr/bin/xxx" |
| 34 |
>> |
| 35 |
>> It's much appreciated if anyone could help ; ) |
| 36 |
>> |
| 37 |
>> |
| 38 |
>> └── signal-desktop-bin-5.50.0 |
| 39 |
>> ├── distdir |
| 40 |
>> │ └── signal-desktop_5.50.0_amd64.deb -> |
| 41 |
>> /var/cache/distfiles/signal-desktop_5.50.0_amd64.deb |
| 42 |
>> ├── files -> /var/db/repos/gentoo/net-im/signal-desktop-bin/files |
| 43 |
>> ├── homedir |
| 44 |
>> ├── temp |
| 45 |
>> │ ├── build.log |
| 46 |
>> │ ├── eclass-debug.log |
| 47 |
>> │ ├── environment |
| 48 |
>> │ └── logging |
| 49 |
>> └── work |
| 50 |
>> ├── opt |
| 51 |
>> └── usr |
| 52 |
>> |
| 53 |
>> |
Archives