OpenRV icon indicating copy to clipboard operation
OpenRV copied to clipboard

RPM release

Open danielpodwysocki opened this issue 2 years ago • 7 comments

Hello,

Is an RPM release in the plans for this ? It would be great to have one to easily get this deployed.

danielpodwysocki avatar Jan 18 '23 10:01 danielpodwysocki

Good idea. :-)

khw7096 avatar Jan 18 '23 14:01 khw7096

Hi @danielpodwysocki @khw7096,

I'm curious to know why you want an rpm package. We aim to have an RV archive that contains all the dependencies required to run it, so we can only unzip/untar and run.

The current commercial version doesn't have an RPM, and it's not something that causes issues.

geffrak avatar Jan 18 '23 15:01 geffrak

Hi! If you're asking about that because you'd like to build it on one machine and distribute it throughout the facility, you could potentially zip/tar the installation directory and use that.

rogernelson avatar Jan 18 '23 18:01 rogernelson

If it's got a cmake build system now, it should be straightforward to augment it with cpack instructions which can make rpm (and many other package formats) out of the built results. Adding that would, I'm sure, make a great contribution to the project, and it's just build script changes and shouldn't require any knowledge of the rv internals.

(The mechanics of how if or how the ORI org might build and distribute binaries are a separate topic. I'm just commenting on the topic of "how can one build an rpm that can then be distributed.")

lgritz avatar Jan 18 '23 18:01 lgritz

Hi @geffrak ,

For most medium to big studios I think it's not as relevant and that's why it hasn't come up for the commercial version. We all have own deployment workflows this can fit into.

However, now that this is open source, individual users and smaller houses wanting to try it out would benefit greatly - running a couple yum commands is way more straightforward than having to deal with this on their own.

danielpodwysocki avatar Jan 18 '23 20:01 danielpodwysocki

@lgritz GitHub supports automated releases - there are other options, but this one would be the most "plug&play" and not require anything extra.

danielpodwysocki avatar Jan 18 '23 20:01 danielpodwysocki

I understand the need. It is not something available right now because the focus was to put the code public.

The goal is to eventually have some CI/CD in place (because we can’t use Autodesk’s one) and maybe it will gives us installable artifacts.

Thank you for your input!

geffrak avatar Jan 18 '23 20:01 geffrak