Dear Alexey,
thanks a lot for your reply, now I get it.
The path in 1st argument is relative to 2nd argument, and what I thought
before was that it's relative to S="${workdir}".
Best wishes
Alexey Zapparov <
[email protected]> 于2022年7月23日周六 04:50写道：
`dosym target link_name` creates a symlink. Under the hood it calls `ln`. First argument may be either absolute path or relative to link_name. Conventionally relative targets are used.
On Fri, 22 Jul 2022, 16:56 Fabulous Zhang Zheng, <
[email protected]> wrote:
Good evening, dear list
Most binary package ebuilds have such a *dosym* statement in
src_install(), take net-im/signal-desktop-bin as an example:
dosym ../../opt/Signal/${MY_PN} /usr/bin/${MY_PN} (where the variable
is signal-desktop)
*dosym* creates a symlink of the binary under opt at /usr/bin/ according
to devmanaul.
I'm confused about the "../../", since S="${workdir}", the correct way
seems to be "dosym ./opt/Signal/xxx /usr/bin/xxx"
It's much appreciated if anyone could help ; )
└── signal-desktop-bin-5.50.0
├── distdir
│ └── signal-desktop_5.50.0_amd64.deb ->
/var/cache/distfiles/signal-desktop_5.50.0_amd64.deb
├── files -> /var/db/repos/gentoo/net-im/signal-desktop-bin/files >> ├── homedir
├── temp
│ ├── build.log
│ ├── eclass-debug.log
│ ├── environment
│ └── logging
└── work
├── opt
└── usr
<div dir="ltr"><div>Dear Alexey,</div><div><br></div><div>thanks a lot for your reply, now I get it.</div><div><br></div><div>The path in 1st argument is relative to 2nd argument, and what I thought before was that it's relative to S="${workdir}&
quot;.</div><div><br></div><div>Best wishes<br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Alexey Zapparov <<a href="mailto:
[email protected]">
[email protected]</a>> 于2022年7月23�
�周六 04:50写道：<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">`dosym target link_name` creates a symlink. Under the hood it calls `ln`. First
argument may be either absolute path or relative to link_name. Conventionally relative targets are used.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 22 Jul 2022, 16:56 Fabulous Zhang Zheng, <<a href="mailto:
[email protected]" target="_blank">
[email protected]</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Good evening, dear
list</div><div><br></div><div>Most binary package ebuilds have such a *dosym* statement in src_install(), take net-im/signal-desktop-bin as an example:</div><div><br></div><div>dosym ../../opt/Signal/${MY_PN} /usr/bin/${MY_PN} (where the variable
is signal-desktop)</div><div><br></div><div>*dosym* creates a symlink of the binary under opt at /usr/bin/ according to devmanaul.</div><br><div>I'm confused about the "../../", since S="${workdir}", the correct way seems to be &
quot;dosym ./opt/Signal/xxx /usr/bin/xxx"</div><div><br></div><div>It's much appreciated if anyone could help ; )<br></div><div><br></div><div><br></div><div>└── signal-desktop-bin-5.50.0<br> ├── distdir<br> │
└── signal-desktop_5.50.0_amd64.deb -> /var/cache/distfiles/signal-desktop_5.50.0_amd64.deb<br> ├── files -> /var/db/repos/gentoo/net-im/signal-desktop-bin/files<br> ├── homedir<br> ├── temp<br> │
├── build.log<br> │ ├── eclass-debug.log<br> │ ├── environment<br> │ └── logging<br> └── work<br> ├── opt<br> └── usr<br></div><div><br></div></div>
</blockquote></div>
</blockquote></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)