Skip to content
This repository has been archived by the owner on Oct 10, 2024. It is now read-only.

Help get SH3D up to date in the package ecosystem (indirectly related to this project) #6

Open
luzpaz opened this issue Sep 20, 2024 · 4 comments

Comments

@luzpaz
Copy link

luzpaz commented Sep 20, 2024

Packaging status

So the idea is to get some of the other downstream package version up to date so that if someone is on one of those distros they will be up to date with latest stable SH3D which hopefully this workbench will target.

@luzpaz
Copy link
Author

luzpaz commented Sep 20, 2024

Ping @outpaddling any chance you could help with this FreeCAD-related side-project of getting SweetHome3D up-to-date in freebsd ports1 ?

BTW, found an ancient open ticket2 requesting to update to v7.2

Footnotes

  1. https://www.freshports.org/cad/sweethome3d

  2. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274849

@rostskadat
Copy link
Owner

Hello @luzpaz

Correct me if I'm not understanding you right, but are you suggesting that we try to get downstream distros to update their SH3D version?

If that is the case, wouldn't it be more productive to test that different version of SH3D files are properly imported in FC?

Thanks for your feedback

@luzpaz
Copy link
Author

luzpaz commented Sep 23, 2024

If that is the case, wouldn't it be more productive to test that different version of SH3D files are properly imported in FC?

It depends on what is the minimal version of SH3D that you are planning to support going forward, i guess.

@outpaddling
Copy link

Ping @outpaddling any chance you could help with this FreeCAD-related side-project of getting SweetHome3D up-to-date in freebsd ports1 ?

BTW, found an ancient open ticket2 requesting to update to v7.2

Footnotes

1. https://www.freshports.org/cad/sweethome3d [↩](#user-content-fnref-1-75c33145c0d4be94cf7133dc81a6704b)

2. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274849 [↩](#user-content-fnref-2-75c33145c0d4be94cf7133dc81a6704b)

I'll take a look. Sounds non-trivial, but maybe the maintainer has just forgotten about it and the problem has gone away by now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants