Linux

48008 readers

921 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

192

I made a local APT repository that automatically fetches DEBs and AppImages from anywhere (jlai.lu)

submitted 2 months ago by [email protected] to c/[email protected]

59 comments fedilink hide all child comments

On Debian-based distros, when an app is available as a DEB or an AppImage (that doesn't self-update), but no APT repository, PPA or Flatpak, the only option is to manually download each update, and usually manually check even whether there are updates.

But, what if those would be upgraded at the same time as everything else using the tools you're familiar with ?

dynapt is a local web server that fetches those DEBs (and AppImages to be wrapped into DEBs) wherever those are, then serves these to APT like any package repository does.

I started building it a few months ago, and after using it to upgrade apps on my computers and servers for some time, I pre-released it for the first time last week.

The stable version will come with a CLI wizard to avoid this manual configuration.

Feedback is welcome :)

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 1 month ago (1 children)

Well, I'm just automating what people currently have to do manually : visit GitHub and download DEB and install DEB.

If the automated process would be dangerous then the manual process also would be, and that would be on the maintainer for not providing an APT repository or a Flatpak, not on the user for just downloading from GitHub.

[–] [email protected] -2 points 1 month ago* (last edited 1 month ago) (1 children)

Well, I’m just automating what people currently have to do manually : visit GitHub and download DEB and install DEB.

Yeah. You should never do that. Like ever. Build from source; or use a vendored tarball. https://wiki.debian.org/DontBreakDebian

.deb is a terribly insecure nightmare thats held up by the excellent debian packagers, gpg , and checksums, and stable release model. don't use .deb files.

[–] [email protected] 7 points 1 month ago (1 children)

I'm and end user working for end users.

[–] [email protected] -2 points 1 month ago* (last edited 1 month ago) (1 children)

I’m and end user

Yeah, we all are. What's your point?

End users are also developers. All computer users are developers. You are developing.

user working for end users

By making a script that lets me get backdoors and shitty packages with ease? The linux package distribution system is a nightmare, Debian is the least bad approach. There is basically always a better option to using a .deb file. If you come across something that isn't packaged, I recommend Flatpak, building from source (and installing unprivileged), or using the developers vendored tarball (installing unprivileged).

https://wiki.debian.org/SecureApt

By using local .debs you lose the benefit of:

Reproducible builds

GPG checksums

Stable release model

debian security team

[–] [email protected] 5 points 1 month ago

My point is that I'm working a solution for end users.

The solutions you're offering are not user-friendly.