1 in other, will Debian automatically prefer higher version?

being large is a bad thing

having backwards compatibility is hard to work with

directx, on windows, is separated into three different things on linux, for instance

yeah, very hard to learn, categorise and easy to get confused.

this

directx, in short terms, is responsible for connecting devices to programs

A debian question:

Let’s say I have two different repos in sources.list and they both got a package let’s say XYZ.

on linux, on the other hand, we have libseat to assign seats to users, but applications don’t have direct access to these seats, as such. if they do, that’d cause issues (as when using ALSA, for example)

Which package will get installed?

instead, we have pulseaudio/pipewire to assign audio nodes to programs, a compositor to deliver a window frame, and network managed by a network driver

(audio, video and network are the three core elements of directx, btw)

probably the first one

@alexmb7 can you confirm?

And what if both sources are defined under separate .list files in /etc/apt/sources.list.d/ ?

How would Debian decide which one comes first?

Also if the XYZ has version 1.0 in one repo and 1.1 in other, will Debian automatically prefer higher version?

probably alphabetically, but better ask xmb about it

i am talking out of my ass

yeah

Considering both have 500 as Pin Priority

newer versions always get priority

on void linux its configurable

nice

why would you ever choose a lower version though lol

Yes makes sense. That’s how debian-updates repo is able to overwrite old packages from debian

Got it

this just works for me

experimental gets priority, so yeah

its either latest version or best matching/relevant i think

how does it decide match%

idk tbh

id rather not touch that option for now

one of the most horrible cpu i’ve seen running debian