My main use case is end user desktops.
Which isn't user-friendly.
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.
Why the OOP structure and syntax ? Sorry but it makes it difficult to read for me even in my own language ๐
I didn't know there was one, that's interesting, thanks.
Updates must still be delayed because of being third-party though.
I'd be willing to implement additional features for people who are extra careful about security.
Could you please explain what does this consist in ?
Thanks
What's a FIFO ?
I've also looked into VFS but found nothing I'd have the skills to implement. ๐
I'll look into it, thanks !
Discord not automating downloads of DEBs is one of the reasons motivating me to do this.
Personally I need the desktop client because I mod it with plugins that are so useful that I can't do without these anymore.
Alternatively, there are third-party repositories here and here.
There still is delay between Discord releases and repository updates so I still believe dynapt to be the better solution.
Sorry to ask
Don't be. I would love to know that an existing and more experienced program does what mine does.
I've been looking for it myself for a long time before deciding to build it.
isnโt this basically the same thing as apt-cacher-ng?
Here's what I'm reading :
Apt-Cache-ng is A caching proxy. Specialized for package files from Linux distributors, primarily for Debian (and Debian based) distributions but not limited to those.
A caching proxy have the following benefits:
- Lower latency
- Reduce WAN traffic
- Higher speed for cached contents
+------------+ +------------+ +------------+ | Apt Client | <------+ Apt Cache | <------+ Apt Mirror | +------------+ +------------+ +------------+
So, not the same thing.
It locally mirrors existing repositories containing existing packages, it doesn't locally create a new repository for new packages from standalone DEBs.
local repo with
file://
scheme
With that, I couldn't trigger a download when apt update
is ran, I could only do a cron, i.e. a delay, that I do not want.
custom apt-transport
I thought about that, but found no documentation on how to do it. If you have any, I'm interested.
Even just finding documentation on how to generate DEBs and APT repository metadata files was very hard.
I'm and end user working for end users.