Same as it's always been. Add a new file to /etc/apt/sources.list.d/ that clearly identifies the repos purpose, then add in the required content.
Debians Repos through the lifecycle of development
DebianExperimental
DebianUnstable
DebianTesting
DebianBackports
DebianStable - We are here
Ubuntus Repos for each major release take a snapshot of Debian Repos and taking elements from all, they merge them into one of their own.This is what makes Ubuntu a bad fit for anything outside of its own, and by weighing it up against the Don't break Debian page, is a Frankendebian.
Taking any element from their repos and using it verbatin is like playing a game of Russian Roulette because it may require one or more of their mixed elements. Same goes for any PPA.
This is why we will never add the capability to use PPAs' and why we warn against both using them and any foreign repos.
Now, to an extent, we too sometimes take up-line content from the Testing repos and pull it into our builds, primarily those that improve drivers, but, they're always carefully tested and reworked to keep their dependencies in line with our Debian Stable base, making them safe to use and ensuring no conflicts will arise that will cause major breakage. On a few occasions, we have been caught out and we've acted quickly to put things right, but to my knowledge, it's never ended up with a total loss, something I've seen repeated across all Ubuntu based builds for many years running.
With our AHS builds, we employ more content from Testing to bring driver support to facilitate the use of new hardware developments, that are usually 1 year past their initial release. For example, a brand new 11th Gen Intel machine should have better than 98% hardware utilisation, but a 13th gen Intel may not work so well.
Debians Repos through the lifecycle of development
DebianExperimental
DebianUnstable
DebianTesting
DebianBackports
DebianStable - We are here
Ubuntus Repos for each major release take a snapshot of Debian Repos and taking elements from all, they merge them into one of their own.
Code:
DebianUnstable....\DebianTesting......\ |--- Ubuntu-<name of some animal>DebianBackports..../DebianStable....../Taking any element from their repos and using it verbatin is like playing a game of Russian Roulette because it may require one or more of their mixed elements. Same goes for any PPA.
This is why we will never add the capability to use PPAs' and why we warn against both using them and any foreign repos.
Now, to an extent, we too sometimes take up-line content from the Testing repos and pull it into our builds, primarily those that improve drivers, but, they're always carefully tested and reworked to keep their dependencies in line with our Debian Stable base, making them safe to use and ensuring no conflicts will arise that will cause major breakage. On a few occasions, we have been caught out and we've acted quickly to put things right, but to my knowledge, it's never ended up with a total loss, something I've seen repeated across all Ubuntu based builds for many years running.
With our AHS builds, we employ more content from Testing to bring driver support to facilitate the use of new hardware developments, that are usually 1 year past their initial release. For example, a brand new 11th Gen Intel machine should have better than 98% hardware utilisation, but a 13th gen Intel may not work so well.
Statistics: Posted by m_pav — Wed Dec 27, 2023 7:22 pm