I just add ssh exactly like scp. I think it's better to include it all to
main package and allow opennssh-client to replace it with own binaries. In
other words, made it like busybox with symlinks, that are replaced by
linux-utils, coreutils etc.
10 лют. 2016 13:38 "Sören Tempel" <soeren@soeren-tempel.net> пише:
> On 08.02.16, Valery Kartel wrote:
> > +_ssh() {
> > + pkgdesc="Dropbear ssh command"
> > + depends="dropbear !openssh-client"
> > + arch="noarch"
> > + mkdir -p "$subpkgdir"/usr/bin
> > + mv "$pkgdir"/usr/bin/ssh "$subpkgdir"/usr/bin/
> > +}
>
> I like the idea of having -ssh and -scp subpackages for dropbear,
> however, correct me if I am wrong but the `/usr/bin/ssh` is just a
> symlink to dropbear multi (so is `/usr/bin/scp`) does it really make
> sense to have subpackages for symlinks? Wouldn't it make more sense to
> not use the multicall binary if we want to split this package into
> multiple subpackages?
>
> Sören.
I like the idea of having -ssh and -scp subpackages for dropbear,
however, correct me if I am wrong but the `/usr/bin/ssh` is just a
symlink to dropbear multi (so is `/usr/bin/scp`) does it really make
sense to have subpackages for symlinks? Wouldn't it make more sense to
not use the multicall binary if we want to split this package into
multiple subpackages?
S�ren.
---
Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org
Help: alpine-aports+help@lists.alpinelinux.org
---