vinifmor / bauh

Graphical user interface for managing your Linux applications. Supports AppImage, Debian and Arch packages (including AUR), Flatpak, Snap and native Web applications
zlib License
931 stars 71 forks source link

.deb files #324

Open Rik44444 opened 1 year ago

Rik44444 commented 1 year ago

hi, I'm on Ubuntu 20.04. Is it correct that software installed via the CLI with "apt-get install" are added to the gauh overview of installed packages (when aptitude is installed), but that .deb that are downloaded and double-clicked to install are not? If so, I would like to make a feature request for enabling somehow to load .deb files from Bauh (like .appimage files) and/or that when you double-click a downloaded .deb file that you get the option to install it via Bauh. thanks Rik

hg42 commented 1 year ago

I second that...

and I would add some points:

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 commented 1 year ago

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

hg42 commented 12 months ago

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.