We will investigate it and take care to create a new package for the libmlx5-dev according debian policy, and sending it as a follow up patches. On Tue, Feb 14, 2017 at 8:05 PM, Jason Gunthorpe <jgunthorpe@xxxxxxxxxxxxxxxxxxxx> wrote: > On Tue, Feb 14, 2017 at 07:52:19AM +0200, Leon Romanovsky wrote: > >> Sorry, but I'm still missing how mlx5 installation will be handled. >> >> The ibverbs-provider installs different *-rdmav2.so files and it should >> install libmlx5-rdmav2.so among them. > > No, the symlink from -rdmav2.so needs to go to a real file not another > symlink. > >> If we move libmlx5.so to libibverbs-dev, how will symlink be >> created? > > libmlx5.so is the 'devel' symlink, it is only used by the compiler > during linking which is why it must be placed in the -dev package. > >> What will user see after installing libibverbs + ibverbs-provider? > > libmlx5-rdmav2.so should be ../libmlx5.so.1.0.13 > >> And what will be in case of libibverbs-dev + ibverbs-provider? > > Then you get libmlx5.so -> libmlx5.so.1.0.13 and the man pages and > header files. libibverbs-dev will need to depend on the > ibverbs-provider package also. > > This is all also true for RPM systems. > > Jason > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
