On Thu, May 30, 2024 at 06:06:02PM +0200, Antony Stone wrote:
> Hi.
>
> Would anyone mind explaining to me how the Devuan package repository works?
>
> My understanding is that it actually contains only the packages which have
> been forked by Devuan, and any packages which are systemd-free in Debian are
> simply "linked-through" in some way so that accessing the repository at
> http://deb.devuan.org/merged gives the combined Devuan (if forked) and Debian
> (if not forked) packages.
>
> I assume this is the origin of the path "merged" in the URL.
>
> How has that been done, please?
>
> I have modified some Debian packages in ways nothing to do with systemd, and I
> currently assign them slightly different version numbers from Debian's, and
> then pin them on the machines I want to use them on so that they don't get
> "upgraded" to a newer version of the Debian package which doesn't have my
> modifications.
>
> However, if I could simply set up my own repository which contains my packages
> and passes through requests for anything else to the Devuan repository, this
> could make life quite a bit easier (and more consistent).
>
> So, assuming my basic understanding of how this works is correct, can anyone
> explain to me how it's been done please?
>
It's called Amprolla.

amprolla is an apt repository merger originally intended for use with the Devuan infrastructure. This version is the third iteration of the software.

https://git.devuan.org/devuan/amprolla3

-- hendrik

>
> Antony.
>
> --
> "Can you keep a secret?"
> "Well, I shouldn't really tell you this, but... no."
>

>                                                    Please reply to the list;
>                                                          please *don't* CC me.
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng