Add `apt autoremove`

[rmdes]

@girish have seen this, but like 2 years ago ?

[robi]

Wow this really exploded while I slept.

@girish That is not a correct conclusion.
@mehdi is correct above.

Even with Cloudron not installing anything new, the system will over time end up with orphaned dependencies that can be removed. This includes old kernels.

It will not harm the system, only keep it less cluttered and do the right thing(tm).

Please do the needful.

[mehdi]

Even if not automatic, I think a button do to it manually would do the job.

That plus a warning for admins that the boot partition is nearly full would cover a great majority of usecases i think

[robi]

@mehdi Why give the admin yet another button when it can be eliminated altogether? I'd rather do it on CLI then.

Point is, I don't want to see autoremove whenever I run apt or have to deal with kernels filling up for poorly planned partitions or side-effects of OS vendor releasing lots of kernels and not cleaning up.

[necrevistonnezr]

@robi said in Add `apt autoremove`:

Point is, I don't want to see autoremove whenever I run apt or have to deal with kernels filling up for poorly planned partitions or side-effects of OS vendor releasing lots of kernels and not cleaning up.

If autoremove gets integrated in the Cloudron apt update routine, you wouldn't "see" it?!

[robi]

@necrevistonnezr No, as it would be run regularly in the background.

Hence when I run apt install blah manually, it has a low chance of finding it needs to remove something via autoremove.

[mehdi]

@robi said in Add `apt autoremove`:

Hence when I run apt install blah manually

Aren't you not supposed to install stuff manually on cloudron?

[nebulon]

Indeed one shouldn't (install manually) to avoid breaking on updates, but in the end it is still ones own server

[necrevistonnezr]

@mehdi Exactly, we're talking about Cloudron background routines, not manual installing on the server.

[robi]

Are you telling me that apt install screen is going to break updates?