.deb files about bauh

[hg42]

I second that...

and I would add some points:

• a possibility to exclude the standard sources (the system already manages this on Debian derivates)
• a possibility to add urls that can be used to download deb packages, just a folder that contains deb files
  example:
  https://download.mediathekview.de/unstabil/

extracting the versions might be tricky, the version usually follows debian rules, but...
this link has deb files with mostly the same version number, that are only distinguished by dates, because the nightly versions all have the same official version number.

btw. AppImages could also be added from such urls

[vinifmor]

Hi folks. Sorry for the really long delay in responding to that thread. @hg42 your suggestion would fit as a separate issue.

[hg42]

I added it here, because the title is quite general and my points are closely related (e.g. files from urls) and the implementation should probably consider all the aspects.

E.g. a deb from a file or an url is basically the same when it comes to installation.
However, the url adds an update mechanism which is different from apt repositories.

Btw. lately, there is also makedeb, a kind of AUR for Debian, though these also seem to be available precompiled via apt repositories, at least I didn't find a need to install one from scratch, yet.

On Debian derivates you would probably not want to manage any packages from repositories. The apt system can much better manage dependencies, pinning, priorities, etc. And the number of installed system packages (thousands) makes other types unusable.

But there is a need for management/updates of deb packages not available in repositories.

AppImages are usually complete, flatpaks are a bit like containers (a few layers), but debs have a fine grained dependency tree that can trigger lots of changes or conflicts.