What repositories does Neon take from? Since it is based on Ubuntu LTS, is it right that it's built from Ubuntu with KDE minus Gnome?

Neon uses it's own Repo's for all the KDE stuff, & the Ubuntu LTS Repo's for everything else.
So by installing the Neon iso, you basically get a vanilla KDE Desktop with Firefox thrown in. Everything else you want you have to install from the Repo's.
So technically it is built from the Ubuntu base, with the latest KDE on top.

personal preference: after a fresh installation, i delete 5-6 kde-(neon) packages/applications i do not need (office program stuff, et cetera; i've got one app-image for that - that's enough.

of course only if this doesn't cause any additional losses - so i always pay attention to what might be uninstalled as well resp. i pay attention to the dependencies. discover delivers this indicators in a simple way. it's possible - in contrast to opensuse, which destroyed kde/the system completely afterwards.

i had no problem with it on kde-neon so far (i also remove kde-connect, because i hate smartphones & co. - a "stallman thing").

well. that's freedom. install what you need, deinstall what you do not need, but keep what the system needs (and that's really vanilla on kde-neon).

therefore: i prefer as little classical packages - with all their dependencies - as possible. the rest: isolated flatpaks and snaps (for example brave). if there is no snap or flatpak for a specific application = classical packages. discover delivers all three possibilities. the system keeps clean, stable and is prepared for the future (actually already for the present).

rule: i try to forget ubuntu.

update/upgrade only per:

https://masonbee.nz/updating-kde-neon/

i also do this:

Code: Select all

systemctl disable ModemManager.service

after

Code: Select all

systemd-analyze blame

& necessary for the vpn to work:

Code: Select all

sudo apt install network-manager-openvpn

& keep everything clean:

Code: Select all

sudo apt autoclean; sudo apt clean; sudo apt autoremove --purge

&

Code: Select all

sudo apt-get purge $(dpkg -l | grep '^rc' | awk '{print $2}')

affter

Code: Select all

dpkg  --get-selections | grep deinstall

and/or

Code: Select all

dpkg -l | grep ^rc | awk '{print $2}'

&

Code: Select all

sudo apt purge --auto-remove xul-ext-ubufox

( thx @german kde-fanpage: https://www.kde-neon.de/blog/ )

&

Code: Select all

flatpak uninstall --unused

&

i deactivate kde-wallet

&

i use vaults.

&

i install & configure the "simple monitor" widget/plasmaoid

&

i install & configure yakuake

&

.. ... so many other things (system-settings) 4 look & feel & workflow.

it's kde.

a kernel update no longer appears to be necessary since the last security-kernel update. but it's possible:

viewtopic.php?f=14&t=159973&p=414725&hilit=kernel#p414725


ps: & what i absolutely need is this - thx @kde - awsome anyway.

https://twitter.com/kdecommunity/status ... 6083914755

pps: not to forget: the ufw - firewall. based on iptables & a little outdated (not only because of docker-problems; but docker is outdated too: keyword: daemon-less podman & co.).

imho - i would prefer a kde-fw-gui-solution or something completely new).

but it's all about privacy/security. therefore: for the moment and under abdominal pain because of that (imho) per se unaesthetic - concept of a "firewall" which already pained me under windows (of course on a much bigger scale than under linux) :

Code: Select all

sudo ufw status

Code: Select all

sudo ufw enable

Code: Select all

sudo su

Code: Select all

ufw allow 9001/tcp

Code: Select all

ufw allow 6881/tcp

Code: Select all

ufw allow 6881/udp

( = tor & qbittorrent).

and if you need that:

Code: Select all

ufw allow ssh

disable ufw:

Code: Select all

ufw disable

reset ufw rules:

Code: Select all

ufw reset

a final look @ ufw & iptables :

Code: Select all

sudo ufw status verbose

&

Code: Select all

sudo iptables -L

waynes wrote:Neon uses it's own Repo's for all the KDE stuff, & the Ubuntu LTS Repo's for everything else.
So by installing the Neon iso, you basically get a vanilla KDE Desktop with Firefox thrown in. Everything else you want you have to install from the Repo's.
So technically it is built from the Ubuntu base, with the latest KDE on top.

Ah, figured it'd be like that. It's one of the reasons why I love it; but it seems like the packaging repo for Neon are just patches unless I''m doing something wrong. The combo is partly why I'd like to compile my own; Ubuntu's apt, and I love it, keeps pushing outdated packages for just Bionic. If I compiled a tweaked version with my own repos that would blacklist non-Neon packaging and having the peace of mind that I won't be breaking any dependencies.

martinki wrote:pps: not to forget: the ufw - firewall. based on iptables & a little outdated (not only because of docker-problems; but docker is outdated too: keyword: daemon-less podman & co.). [...]

]

Nice, thanks! This is helpful, I'm wanting to develop mobile apps and you won't believe how insecure everything is. I'd look into fail2bban for n additional layer of protection.

chan wrote:Ah, figured it'd be like that. It's one of the reasons why I love it; but it seems like the packaging repo for Neon are just patches unless I''m doing something wrong. The combo is partly why I'd like to compile my own; Ubuntu's apt, and I love it, keeps pushing outdated packages for just Bionic. If I compiled a tweaked version with my own repos that would blacklist non-Neon packaging and having the peace of mind that I won't be breaking any dependencies.

Some questions:
What do you mean by build Neon from scratch, specifically?
The whole distro, or just the Plasma part that Neon provides?

What do you mean by 'patches', in terms of Neon's Plasma, et al?
And what i outdated in the base OS? Sure, it may not be 110% current, but core system is hardly outdated. I will guess that what you see are security fixes.

Also, if you build your own Plasma, Applications, and Frameworks from source code, you lose benefit of using apt for what you build.

claydoh wrote:

chan wrote:Ah, figured it'd be like that. It's one of the reasons why I love it; but it seems like the packaging repo for Neon are just patches unless I''m doing something wrong. The combo is partly why I'd like to compile my own; Ubuntu's apt, and I love it, keeps pushing outdated packages for just Bionic. If I compiled a tweaked version with my own repos that would blacklist non-Neon packaging and having the peace of mind that I won't be breaking any dependencies.

Some questions:
What do you mean by build Neon from scratch, specifically?
The whole distro, or just the Plasma part that Neon provides?

What do you mean by 'patches', in terms of Neon's Plasma, et al?
And what i outdated in the base OS? Sure, it may not be 110% current, but core system is hardly outdated. I will guess that what you see are security fixes.

Also, if you build your own Plasma, Applications, and Frameworks from source code, you lose benefit of using apt for what you build.

From scratch meaning to compile it and build a live environment that can install.
The whole distro, with what Neon is made from. The goal is to have a system that runs on newer packages but keeps its 'identity' and (eventually) catches up when packages that aren't from Neon's PPA are up to date.

Ubuntu has packages that are months behind, and some . It makes sense, given how difficult it is to maintain distro wide stability.
I think what I need to do to satisfy my itch is make my own unix based system with KDE, but Gentoo seems like the best solution at the moment. I've found over the past couple days how time consuming it is to read installation guides, find their dependencies, recursively read some more (lol). Pinning Disco backports could be an easy option but it doesn't feel quite right.

If anyone is interested, I added Sid (unstable Debian distro) repos to my list. I've been able to compile them but always errors. Why does the Official Admin's Guide have conflicting information with the official documentation?

Here's Sid:
https://lists.debian.org/debian-devel-a ... 00001.html
Download and add keys using wget -q http://thisistheurl.com -O- | apt-key add -

Append this to your sources.list
deb http://deb.debian.org/debian/ unstable main contrib non-free
deb-src http://deb.debian.org/debian/ unstable main contrib non-free

In /etc/preferences.d, make a file to pin it low (real damn important). I have mine set at 99 and 100. Have the repos match, and while you're there question why a rolling distro has a xenial override.

Here's a command to try to make listing packages in a 'prettier' way. I wish pkcon had syntax lighting. Btw, I just wrote these so apologies if they dont fucntion the best.

Code: Select all

pkcon get-packages  | grep debian | grep -v ubuntu[ /code]

PKG="pkg"
[code]pkcon search $pkg | grep '^[Available/neon]' | grep -v ubuntu | sed 's/Available    //' | sed 's/+p18.04+git/    /' | sed 's/201.*ain)//g'

I don't expect to keep these repos on long, only to grab what I need. Edit: For anyone who does grab packages from other distros, it seems like you need to regenerate the symlink for apt_pkg.so, referencing this as a solution: https://askubuntu.com/questions/1043484 ... installing

I picked the wrong distro haha....I love Neon but APT is not quite the best. I am going to do a upgrade to disco, with pinning priority and apt-mark to keep me safe.
I have been using the --simulate operator with great success; it has been showing me if installing a new package would break anything. Unfortunately packages don't recursively add their own dependencies resulting in upgrades breaking the system; I'll have to devise a way to fix that. I'll keep this posted for those who are interested.