Need some help setting up rpm and deb package packing via arcade.

[AraHaan]

I been trying to figure out how to build deb and rpm installer packages using the same files I use to build msi/exe bundle installers and macos pkg installers, of which I could use the information to see if I could help clean up some files in dotnet/runtime but yet also package them in the same way as well (just with less files to maintain). This is so then I could eventually learn how I can then eventually add them to a debian package repository for install via apt-get or related package managers.

Basically, I want to build installer packages in deb and rpm format for the following generic rids:

• linux-x64
• linux-arm
• linux-arm64

Here is an PR where I tried to learn how to do this using arcade https://github.com/Elskom/EFCore-Installer/pull/48/files using test files that simply bundles efcore into an installable shared framework (it also exists as an example and a way for me to experiment with more things from arcade).

[michellemcdaniel]

I think you want the GenerateDeb and GenerateRpm targets that are in arcade. @jkoritzinsky may be able to point you to how to use them.

[AraHaan]

So basically, I might have to manually call those targets instead of the GenerateInstallers target which I thought would call into it automatically?

[AraHaan]

I tried those targets, and they seem to not have made any difference. https://github.com/Elskom/EFCore-Installer/actions/runs/3447742835/jobs/5754071449

[michellemcdaniel]

I'm not exactly sure how those targets work, but they are what runtime uses to build the rpm and deb packages for dotnet. You may want to go look at how runtime uses them in their CI

You can see what they are doing here: https://github.com/dotnet/runtime/blob/bd7e1cb81d763589b95f7bfbaa2a96dd364e9103/eng/pipelines/installer/jobs/build-job.yml#L26-L32. I believe it is the /p:BuildDebPackage=true and /p:BuildRpmPackage=true that does it for them, though I do not know how that is wired through the rest of their build.

[AraHaan]

Let's see if this works.

[AraHaan]

It looks like it still did not generate them...

[michellemcdaniel]

Sorry, that is the extent of my knowledge. Hopefully someone from runtime can pop in.

[AraHaan]

Ah I think I might know why this is. In WSL I tried testing to see if debuild and fpm are usable and this is what I found:

• sudo apt install devscripts installs debuild.
• sudo apt install ruby && sudo gem install fpm installs fpm.

It might be that github actions lacked these and so they were skipped, will test and see if the rpm and deb packages get emitted locally or not though.

[michellemcdaniel]

Ah yes, those are required to be on the path for those targets to run

[AraHaan]

And they still are not run, even when those are installed.

[jkoritzinsky]

To build the rpm and deb packages, you need to set <BuildRpmPackage>true</BuildRpmPackage> and <BuildDebPackage>true</BuildDebPackage> in your csproj. Then the targets should light up and run.

[AraHaan]

So, do not pass it to my bundleproj which passes them to the sfxproj's?

[michellemcdaniel]

@jkoritzinsky did you see AraHaan's question? @AraHaan have you been able to figure this out?