Skip to content

Feature: script for creating Debian package#1417

Merged
cbnolok merged 8 commits intoSphereserver:devfrom
mtwango:debian-packaging
May 16, 2025
Merged

Feature: script for creating Debian package#1417
cbnolok merged 8 commits intoSphereserver:devfrom
mtwango:debian-packaging

Conversation

@mtwango
Copy link
Copy Markdown
Member

@mtwango mtwango commented May 9, 2025

Add option to build deb package from source. Preconfigured for Linux x86_64 Nightly. Cmake pamars has been taken from .github/workflows/build_linux_x86_64.yml (except ccache).

Description how to build, install, update and remove included in readme.

mtwango added 7 commits April 24, 2025 11:15
- packaging script
- service and init files
- user, folders and permissions
- default admin account

@todo
- depends on Sphereserver#1400
- change email in changelog and control
- enhance manual page
- updated placeholder email address to reflect website
- update switch for loading ini folder
- fixed copying new accounts file
- updated manpage for cli switches
- remove everything during remove
- crlf -> lf files
@cbnolok
Copy link
Copy Markdown
Contributor

cbnolok commented May 9, 2025

That's great! What about moving this in another super-folder with a name like "deploy"? That could be useful also for future subfolders, like docker config files, rpm scripts, etc

@mtwango
Copy link
Copy Markdown
Member Author

mtwango commented May 12, 2025

Yeah, I think it could be done.

I put it in root directory, since if you want to distribute packages in official debian repositories, you need to use their Gitlab and CI requires proper structure. You can check it, for example: https://salsa.debian.org/apache-team/apache2

The packaging can be kept elsewhere, but it is always easier to mirror repository, than running packaging and keeping upstream branch synced. However, if this is not planned, I can move debian directory elsewhere, .gitnore it in root folder and update packaging script, so it gets copied before running packaging.

@cbnolok
Copy link
Copy Markdown
Contributor

cbnolok commented May 15, 2025

I don't think we'll ever be interested in getting in an official distro package repo, it's much less a hassle to build deb packages ourselves (if needed?) and let people pick the version from github.
I'd say i'd leave the choice to you, i'm not an expert on this field. If it doesn't complicate stuff, having a separate folder would be better, otherwise let's just have a debian folder in the main tree

- updated paths in rules
- updated readme
- .gitignore for compiled debian package
@mtwango
Copy link
Copy Markdown
Member Author

mtwango commented May 16, 2025

I've moved the directory to packaging folder and updated paths and readme accordingly. The output files are generated in root (added to .gitignore). It could be generated elsewhere, but it requires a lot of parameters and env variables during build command, so I kept it clean,

@cbnolok cbnolok merged commit 93931dd into Sphereserver:dev May 16, 2025
18 checks passed
@mtwango mtwango deleted the debian-packaging branch May 16, 2025 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants