Re: Bug#1039604: glusterfs: Drop support for 32-bit architectures
Hello,
Am 15.07.2023 um 08:54 schrieb Michael Tokarev:
Yes, I use libglusterfs-dev in Build-Depends of samba and qemu.
I think it is already reduced to 64bits on ubuntu for samba (or,
rather, i386 is excluded).
The question is: how to specify dependencies properly and more important,
how to specify lists of files to install?
I have uploaded glusterfs 11.0-1 to experimental, it is limited to these
architectures:
amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64
So if nobody rises up I would start to fill bugs for the reverse
dependencies in the next days and after that uploading glusterfs 11.x to
unstable.
What happens with stable, there I do not have an answer, yet.
Right now I have:
d/control: Build-Depends: libglusterfs-dev
d/foo.install: /usr/lib/foo/gluster.so
I can change the first one to be something like
Build-Depends: libglusterfs-dev [amd64 arm64]
So in your depends you should use:
libglusterfs-dev [amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x
ia64 sparc64]
(with a few questions remaining: what is the complete list? How
about non-linux?). But what to do with the second, - move the
handling to d/rules, like
if [ -f debian/tmp/usr/lib/foo/gluster.so ]; then
install -D debian/tmp/usr/lib/foo/gluster.so -t
debian/foo/usr/lib/foo/
fi
IMO the best way would be continue to use dh_install, there you can also
limit the architectures:
[amd64 arm64 ppc64el ppc64 riscv64 mips64el s390x ia64 sparc64]
debian/tmp/usr/lib/foo/gluster.so
You way would work, too. But if you want to build the glusterfs module,
but it is not available (for whatever reason) you wouldnt notice it.
Reply to: