Skip to main content ↑ ↓
Topic: Using x86_64-v3 repositories (Read 5648 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Using x86_64-v3 repositories

Reply #15 –
Quote from: gripped – on
The point of accessing the ALHP API would be to check for updates to ALHP packages already installed locally and then download them and add them to the local repo. Which is going to require an internet connection anyway. To check the packager in the local database does not require an internet connection.
It is pointless when you add CachyOS repos to the mix, there's no API for that, when writing my script I went with generic local db probing instead.

Quote from: gripped – on
...
Quote
I've poked around for solutions
Sometimes you have to make your own.
I have various scripts to help me.
But in the main I won't be sharing them on here as it's likely people will break their systems and then blame me no matter how many warnings I include.
Plus I worry that some of what I do personally could be seen as disrespectful to the Artix devs if I try and promote it. So I don't.
Yeah, I did write a solution to that, I initially wanted to post it here, but it's just not worth the effort for so little performance uplift in my case and a waste of time waiting for tracking verification to finish so I just abandoned the idea without optimising it.

Spoiler (click to show/hide)

Re: Using x86_64-v3 repositories

Reply #16 –
Quote from: Shoun2137 – on
It is pointless when you add CachyOS repos to the mix, there's no API for that, when writing my script I went with generic local db probing instead.
Don't add it into the mix then.
Quote
and a waste of time waiting for tracking verification to finish
You lost me there ?
Quote
I don't know the lore around your work here
That makes two of us.
Quote
the world has become so fragile in recent years that I’ve simply lost faith in people
A sad statement, yet a sentiment I unhappily share. Though with the prefix 'many' people

Re: Using x86_64-v3 repositories

Reply #17 –
so after adding their repos and installed some pkgs from there, I think it will be ok to use the vanilla version pacman instead of cachyos team's modded one, it looks like this :
Code: [Select]
:: Searching AUR for updates...
:: Searching databases for updates...
 -> findutils: local (4.10.0-2.1) is newer than system (4.10.0-2)
 -> fzf: local (0.55.0-1.1) is newer than world (0.55.0-1)
 -> gsmartcontrol: local (1.1.4-1.1) is newer than world (1.1.4-1)
 -> gvfs-gphoto2: local (1.56.0-1.1) is newer than world (1.56.0-1)
 -> hdparm: local (9.65-2.1) is newer than system (9.65-2)
 -> lld: local (18.1.8-1.1) is newer than world (18.1.8-1)
 -> usbmuxd: local (1.1.1-4.1) is newer than world (1.1.1-4)
 -> Packages not in AUR: cachyos-keyring  cachyos-mirrorlist  cachyos-v3-mirrorlist
 -> Missing AUR Debug Packages: unzip-zstd-debug
 -> Flagged Out Of Date AUR Packages: parabolic  xnviewmp
 there is nothing to do
So in my understanding, the pkgs from cachyos-v3 repo will always append .1 version to it, making it newer to the pkg from artix/arch repos. So as long as cachyos-v3 repo has this pkg built and ready first, I will always have this pkg updated from their repo?

have to put cachyos-core-v3 below [system],
and cachyos-extra-v3 below [galaxy],
otherwise they bring in systemd complaints , or segmentation fault
 

Re: Using x86_64-v3 repositories

Reply #18 –
This is also partly a limitation of pacman to blame, if it's e.g. the exact same version number in both repos it will not be fetched.
To fetch these above packages run -Syyuu, pacman thinks it will "downgrade" them.

Alpine based distros just slap .9999 to ports for it to pass always :)