Re: heavy dependencies of libvtk-dev

2023-10-24 Thread Johannes Thrän
>
> * Johannes Thrän  [2023-10-23 19:58]:
> >libpcl-dev has uneccessarily heavy dependencies. This is, because it
> >depends on the visualization part of pcl, which in turn pulls in libvtk
> and
> >libvtk-qt and with it a desktop environment.
>
> In principal pcl consist of independent libraries that could be packaged
> separately. I'm happy to guide you on that.
>

the library itself, not the -dev package, seems to be split into several
independent packages already.
Would it make sense to have a -dev package for each of those?

BR, Johannes
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Re: heavy dependencies of libvtk-dev

2023-10-24 Thread Jochen Sprickerhof

Hi Johannes,

* Johannes Thrän  [2023-10-23 19:58]:

libpcl-dev has uneccessarily heavy dependencies. This is, because it
depends on the visualization part of pcl, which in turn pulls in libvtk and
libvtk-qt and with it a desktop environment.


In principal pcl consist of independent libraries that could be packaged 
separately. I'm happy to guide you on that.


Cheers Jochen


signature.asc
Description: PGP signature
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Re: heavy dependencies of libvtk-dev

2023-10-24 Thread Anton Gladky
Hi Johannes,

packaging of the vtk9 is placed here [1]. If you have some technical solution,
how to solve the issue, feel free to contribute. Yes, vtk9 is a large package.

[1] https://salsa.debian.org/science-team/vtk9

Best regards

Anton

Am Mo., 23. Okt. 2023 um 20:22 Uhr schrieb Johannes Thrän
:
>
> Hi,
>
> libpcl-dev has uneccessarily heavy dependencies. This is, because it depends 
> on the visualization part of pcl, which in turn pulls in libvtk and libvtk-qt 
> and with it a desktop environment.
>
> In containerized build environments, where one just need respective headers 
> to link against, this is problematic. To my knowlegde, there's no way around 
> it.
>
> How could we help to improve on this situation?
>
> BR, Johannes
>
>
> --
> debian-science-maintainers mailing list
> debian-science-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers