You are not logged in.
Pages: 1
I have a couple of repos that are close in what packages they have but of course, one has a more recent package than the other so that I am finding myself in rotating door syndrome. Either I have to make a copy of my pacman.conf and point to it using --config or I have to keep swapping my repo lines in my existing pacman.conf. Any other solutions? Some of these packages are in aur, but I don't want to have to makepkg if they are already in the repos.
Last edited by nomorewindows (2014-02-26 16:38:56)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
In that case those repos suck. All you can do is either contribute to those repos, so they are more up to date, give the current maintainers a kick in the arse or just don't use them.
Offline
I have a couple of repos that are close in what packages they have but of course, one has a more recent package than the other so that I am finding myself in rotating door syndrome.
It's not entirely clear what you mean. I presume these packages are identical in every respect but name, and therefore you can't just keep both repos in pacman.conf, correct? Or does a package in one repo have a dependency in the other, or you're too impatient to wait for one maintainer to update a package the other already has, or what? In any case, if you have limited bandwidth or CPU power it's understandable to not want to build them from the AUR, but that's always going to be the second freshest source behind making your own PKGBUILDs and grabbing the source code yourself. sekret's (mostly) right: Since you don't really have the right to demand that the maintainer build packages just for you, the solution to a perpetually out-of-date repository is "Don't use that repository."
Offline
The packages from both repos overlap each other. But one repo has some packages that the other one doesn't have.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Arch packages are meant to be consistent within a repo. Just like with [testing], it's an all-or-nothing approach. Sure, often you can mix-and-match similar packages / dependencies from various repos, but it's not guaranteed to work.
Offline
It's nothing major, per se, pacman just spits out
warning: package: local (..) is newer than repo (..)I sometimes get this with packages from aur.
Last edited by nomorewindows (2014-02-26 16:05:41)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I thought you were talking about some dependency hell ...
Edit:
I sometimes get this with packages from aur.
AUR can't have packages with the exact same name as packages from the official repos, but packages from unofficial repos are fair play.
Some maintainers provide both unofficial repo and AUR packages.
Last edited by karol (2014-02-26 16:08:50)
Offline
I thought you were talking about some dependency hell ...
Edit:
nomorewindows wrote:I sometimes get this with packages from aur.
AUR can't have packages with the exact same name as packages from the official repos, but packages from unofficial repos are fair play.
Some maintainers provide both unofficial repo and AUR packages.
But if you change the order of the repos in pacman.conf, it will pick the first one that has it (AUR being at the last).
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Yup.
Various unofficial repos can have packages with the same package name or 'provides'.
Offline
Yup.
Various unofficial repos can have packages with the same package name or 'provides'.
So the only thing I was asking on forum here is if there is a better way to rotate the repos from pacman.conf that have similarities. Or maybe there's an option in pacman I wasn't aware of that says install package from specific repo.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
You can run 'pacman -S <repo name>/<package name>', but '--config' isn't a bad way either.
Offline
You can run 'pacman -S <repo name>/<package name>', but '--config' isn't a bad way either.
Ok...that's probably what I'm looking for.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Pages: 1