Le vendredi 02 avril 2021 à 09:16 -0400, Qianqian Fang a écrit : > On 4/2/21 5:19 AM, Sébastien Villemot wrote: > > > But are those symlinks really needed in the first place? I could not find a > > place in the package where “tetgen1.5” is called (with the version number > > as a suffix). Only “tetgen” seems to be called. But maybe am I missing > > something. > > > we noticed that the mesh output are not reproducible across different > versions of tetgen. They also behave differently - some crash for > certain input, some don't. therefore, in iso2mesh, we embedded different > versions of iso2mesh and allow users to specifically choose using a flag > in several core functions. > > Because debian only provides tetgen1.5 as tetgen, to allow some existing > scripts/demos to run (at least), for example, in the octave-brain2mesh > package > > https://salsa.debian.org/pkg-octave-team/octave-brain2mesh/-/blob/master/brain2mesh.m#L205 > > > I need to create the tetgen1.5 link. > > let me know if there is a better solution.
Thanks for looking at this issue. I don’t think that creating those symlinks in iso2mesh-tools is the right solution. Such symlinks should only be created by the tetgen package, otherwise this only creates confusion over package boundaries. I think the right solution is to drop the symlinks, and rather to create a Debian-specific patch that replaces “tetgen1.5” with “tetgen” in brain2mesh.m. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
signature.asc
Description: This is a digitally signed message part
