Thanks for the quick answer. I guess the quickest solution would be to
just contact me on this email. In case I could not help, I will dispatch
the issue to the appropriate member of our team.
As of right now, Prusa Slicer can be built with the libraries installed
in the system. There are exceptions but we can discuss that in detail
On 16. 05. 19 11:59, Miro Hrončok wrote:
On 16. 05. 19 11:50, Mészáros Tamás wrote:
> the new *Prusa Slicer 2.0* is almost ready and I would like to
> discuss the RPM packaging with you. To my best knowledge, you have
> been maintaining the Red Hat packages for Slic3r PE which is the
> direct predecessor of Prusa Slicer 2.0. It is the same codebase with
> some major changes and renaming applied to the upstream repository.
> I have prepared a branch named *debian
in our upstream
> repo. My hope is that you can adapt the metadata in the "debian"
> folder to convert the RPM packages of Slic3r PE to Prusa Slicer.
> A major relief is that we no longer depend on Perl to build or run
> the application.
> I would like to ask you to review this branch and help us in getting
> Prusa Slicer into Fedora and Red Hat Linux consequently.
Thank you for the heads up.
Tibbs (cc'ed) is already looking into packaging the new version for
What is the best platform to ask for help if we have problems?
Should we reach directly to you via e-mail, open issues on GitHub?
(I could probably also meet with you in real life if it helps.)
I suppose a major drawback would be lot of bundled 3rd party libraries.
I think there might be some confusion about what is "Red Hat Linux",
so to clarify, there are two things here:
Fedora - tracked above
Red Hat Enterprise Linux - never had any Slic3r in it
"Red Hat Linux" used to be a thing very long time ago.
I'm also CCing the Fedora's 3D printing mailing list for transparency.
*Ing. Tamás Mészáros*,
Prusa Research, s.r.o.