Mahlet-Inc / Mahlet-Inc/hobbits

Add deb and rpm distribution to CI

Open
#22 5 comments 1 reaction 0 assignees View on GitHub
build engineering
Dominant language
Python
Stars
751
Forks
49
PR merge metrics
No merged PRs in 30d

Description

It would be nice to have hobbits packaged in a way that let plugin developers update the application/headers/library easily using a package manager. We could provide the following packages:
- **hobbits-devel** (requires everything?)
- **hobbits** (requires everything except libhobbits-devel and hobbits-qt-creator-wizards)
- **hobbits-gui** (gui binary, requires libs and plugins)
- **hobbits-runner** (CLI runner binary, requires libs and plugins)
- **hobits-core-plugins** (core plugin binaries, requires libs)
- **hobbits-qt-creator-wizards** (wizard templates for Qt creator)
- **libhobbits-devel** (includes headers for plugin development, requires libs)
- **libhobbits** (binary libraries, requires Qt 5.12+)

A few non-trivial things that might need to be addressed:
- where do we host these?
- which parts of hobbits-core are "public"? everything right now?
- how do we make the packages? (seems like CMake can help, see #13 )

@KOLANICH

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the CMake packaging approach referenced in issue #13 and the repository's CI configuration. Define the public package boundaries, dependencies, hosting location, and CI steps for producing deb and rpm packages; done means the proposed hobbits, library, plugin, and development packages are built and distributed consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp, python
Domain
build-system, ci-cd, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.