Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REQUEST] please add back DEB or flatpack #91

Open
chymian opened this issue Sep 2, 2024 · 8 comments
Open

[REQUEST] please add back DEB or flatpack #91

chymian opened this issue Sep 2, 2024 · 8 comments
Assignees
Labels
Feature Request Requests for new features or feedback Suggestion All kinds of suggestions

Comments

@chymian
Copy link

chymian commented Sep 2, 2024

Is your feature request related to a problem? Please describe.
Since the rewrite to 0.3.x, we lost the deb-packages.

Describe the solution you'd like
please add back deb-packages.

Describe alternatives you've considered
add flatpak as distribution-agnostic package.

Additional context
flatpak do have the big advantage (over appimages) that they do auto-upgrades and since a whole plasma-env is available as flatpaks, dependencies (themes, etc) should not be a problem

Last but not Least
Kudos to you for that piece of software -- I'm missing it on my new trixie (deb-testing) install very much

@MartinVonReichenberg MartinVonReichenberg self-assigned this Sep 4, 2024
@MartinVonReichenberg MartinVonReichenberg added Feature Request Requests for new features or feedback Suggestion All kinds of suggestions labels Sep 4, 2024
@MartinVonReichenberg
Copy link
Collaborator

Hello,

The reason why it is not there yet is because Debian 12 (Stable), Ubuntu 22.04.1 (Kubuntu) still use KDE Plasma version 5, since I do not use either Debian Testing (Trixie) or KDE Neon I simply did not compile Koi for these Linux, newer & potentially unstable, distributions.

I might give it a try, but the main reason is older stable versions of QT / Cmake / KDE . . .

And for the Flatpak variant - I am no coder and I find writing the Flatpak Build tTmplate way harder than PKGBUILD, RPM.SPEC or Debian CONTROL because there is a "multiple logic" within several files implemented and not so relating one another . . .

@chymian
Copy link
Author

chymian commented Sep 5, 2024

Servus/hello martin,

thanks for taking time to answer.

since I do not use either Debian Testing (Trixie) or KDE Neon I simply did not compile Koi for these Linux, newer & potentially unstable, distributions.

after being on debian stable (due to Proxmox) for the last decade or so, I recently moved to distrobox for virtualization/container-mgmt. and I'm quite happy with that decision.

Use any Linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Distrobox uses podman, docker or lilipod to create containers using the Linux distribution of your choice. The created container will be tightly integrated with the host, allowing sharing of the HOME directory of the user, external storage, external USB devices and graphical apps (X11/Wayland), and audio.

a.k.a. have every linux-distri at your hand with a very small footprint.
maybe that's something for you as well?

@MartinVonReichenberg
Copy link
Collaborator

after being on debian stable (due to Proxmox) for the last decade or so, I recently moved to distrobox for virtualization/container-mgmt. and I'm quite happy with that decision.

Unfortunately I do not have hardware of running full-time Proxmox instances. And in addition I am not a fan of the confusing interface especially when it comes to disk management - its graphical layout a the strict requirement for using LVM only for running multiple instances of several operating systems at once . . .

Use any Linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Distrobox uses podman, docker or lilipod to create containers using the Linux distribution of your choice. The created container will be tightly integrated with the host, allowing sharing of the HOME directory of the user, external storage, external USB devices and graphical apps (X11/Wayland), and audio.

I do not need to run more than 1-3 Linux distributions or even a FreeBSD installation at a time.
I use Windows (still) for playing games and I use Linux for documents, small development, packaging and a full-featured (server) torrenting.

Take care!

@MartinVonReichenberg
Copy link
Collaborator

MartinVonReichenberg commented Oct 29, 2024

Hello,

I will, within this week, package it for Kubuntu again . . .

@frenchcomp
Copy link

Hi,
Kubuntu 24.04 (the last LTS) use Plasma 6 and Kubuntu 24.10 Plasma 6.1

@MartinVonReichenberg
Copy link
Collaborator

Hello,

If the builds for Kubuntu 24.04 fail due to required QT 6 / KF 6 dependencies, the only way using Koi there will have to be an older version of Koi . . .

@MartinVonReichenberg
Copy link
Collaborator

Build instructions for Debian/Ubuntu are available, but I failed their compilation at the end.
Any clues ?_?

@berezovskyi
Copy link

If the builds for Kubuntu 24.04 fail due to required QT 6 / KF 6 dependencies, the only way using Koi there will have to be an older version of Koi . . .

Actually, I succeeded building and running Koi (tags/0.4-0-gd9e239dd-dirty) on Ubuntu 24.04 (KDE 5.115.0, Qt 5.15.3; KDE installed on Ubuntu after the fact, neofetch below is wrong in OS detection) following your instructions in #90 (comment)

image

These are the prerequisites I installed as per README instructions: sudo apt install 'g++' 'cmake' 'cmake-extras' 'libkf5config-dev' 'libkf5coreaddons-dev' 'libkf5dbusaddons-dev' 'libkf5widgetsaddons-dev' 'qtbase5-dev' 'kde-plasma-desktop' 'plasma-framework' 'plasma-integration' 'plasma-workspace

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Requests for new features or feedback Suggestion All kinds of suggestions
Projects
None yet
Development

No branches or pull requests

4 participants