https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #29 from Christoph Cullmann ---
(In reply to Timothée Ravier from comment #28)
> To move things forward, I'm suggesting we keep Kate on Flathub but in a Beta
> state, where we can still try to improve support while at the same time
> making
https://bugs.kde.org/show_bug.cgi?id=431223
Timothée Ravier changed:
What|Removed |Added
CC||t...@siosm.fr
--- Comment #28 from Timothée
https://bugs.kde.org/show_bug.cgi?id=431223
Kåre Särs changed:
What|Removed |Added
CC||kare.s...@iki.fi
--- Comment #27 from Kåre Särs
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #26 from Ardith Metz ---
Putting it differently: it's like running debian and complaining it doesn't use
packages from fedora :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #25 from Ardith Metz ---
Generally flatpak is supposed to be self-contained and distro agnostic. If your
system is debian then you can build something using debian tools that will work
only on debian while other developer on fedora will
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #24 from Christoph Cullmann ---
(In reply to Ardith Metz from comment #22)
> Isn't it possible use kdesrc-build inside flatpak first then use kate in the
> same environ??
>
> There is also flatpak-spawn command to allows you to execute any
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #23 from Christoph Cullmann ---
Btw. gnome builder goes to great lengths to try to emulate that system access:
https://gitlab.gnome.org/GNOME/gnome-builder/-/commit/fee5214c927c841b66cfd34c0321b8c9890149ce
If somebody steps up to do and
https://bugs.kde.org/show_bug.cgi?id=431223
Ardith Metz changed:
What|Removed |Added
CC||itgvk...@grr.la
--- Comment #22 from Ardith Metz
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #21 from Christoph Cullmann ---
Yeah, but not to the versions installed globally and used by any non-flatpak
part of your system.
E.g. no way to use kdesrc-build to build the kde stuff and then use Kate as IDE
as that lives in a totally
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #20 from Ardith Metz ---
I wanted to note that there are other IDE tools in flathub like gnome builder
or visual studio code and they generally work fine. Definitely using Sdk as
runtime is the way to go for such case which give you access
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #19 from Christoph Cullmann ---
Git commit 38944e72a3ba26ad24a7770707799491f52169ca by Christoph Cullmann.
Committed on 23/03/2021 at 18:40.
Pushed by cullmann into branch 'master'.
remove flatpak download link
flatpak doesn't allow the
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #18 from Christoph Cullmann ---
Hi, thanks that you honor our request.
I think it would be good to have Kate purged from flathub, I will remove the
download link.
For the other comments:
1) I don't consider e.g. the integrated (default
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #17 from Aleix Pol ---
I share Albert's sentiments.
If nobody feels like putting work on it, there's no need to support it. It's a
shame to ditch kate from flathub entirely because of these features who seem
fringe to me, but big part of
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #16 from Albert Astals Cid ---
I've been using kate for over 15 years and i've never used any of those
plugins, obviously i'm just 1 user, but just want to make you think you may be
overstating the usefulness of something not so many people
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #15 from Dominik Haumann ---
I'm with Christoph here. If access to system tools is not there, then the
plugins External Tools, LSP Client, Terminal, Build Plugin, and possibly some
others don't work.
Given this, I suggest we remove the
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #14 from Christoph Cullmann ---
(In reply to Aleix Pol from comment #13)
> As far as I understand, there's the possibility of providing those as
> extensions. Depending on the Sdk as the runtime rather than just the
> Platform will give us
https://bugs.kde.org/show_bug.cgi?id=431223
Aleix Pol changed:
What|Removed |Added
CC||aleix...@kde.org
--- Comment #13 from Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #12 from Christoph Cullmann ---
(In reply to Albert Astals Cid from comment #11)
> > If there is no way to just get the stuff the user has in the environment, I
> > don't think that is a solution, but perhaps I misunderstand that.
>
>
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #11 from Albert Astals Cid ---
> If there is no way to just get the stuff the user has in the environment, I
> don't think that is a solution, but perhaps I misunderstand that.
Well, the user has access to anything he has in his /home,
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #10 from Christoph Cullmann ---
Hmm, what does the SDK provide?
I somehow doubt that it has the go language server or stuff like the haskell
one, not even speaking about the ocaml one I use often.
If there is no way to just get the stuff
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #9 from Albert Astals Cid ---
hmmm, actually i think i have the solution we can change the kate runtime from
org.kde.Platform to org.kde.Sdk and then it will have access to all the devel
tools that the Sdk ships that i guess is what you
https://bugs.kde.org/show_bug.cgi?id=431223
Christoph Cullmann changed:
What|Removed |Added
Summary|Flatpack: Projects plugin |Flatpak: Projects plugin
22 matches
Mail list logo
