Mailing List Archive

Where does emerge --sync store the versions of pkgs for updates?
I'm trying to track down why sometimes binary packages on my server
aren't used by my client.

Does anyone know where the information gotten by emerge --sync is stored?
Re: Where does emerge --sync store the versions of pkgs for updates? [ In reply to ]
n952162 wrote:
> I'm trying to track down why sometimes binary packages on my server
> aren't used by my client.
>
> Does anyone know where the information gotten by emerge --sync is stored?
>
>
>

You can find where your is with this:


root@fireball / # cat /etc/portage/repos.conf/gentoo.conf | grep location
location = /var/cache/portage/tree
root@fireball / #


Mine is not a default location so yours will be somewhere else most
likely. 

Hope that helps.

Dale

:-)  :-) 
Re: Where does emerge --sync store the versions of pkgs for updates? [ In reply to ]
On Sat, Jun 05, 2021 at 11:00:58PM +0200, n952162 wrote:
>I'm trying to track down why sometimes binary packages on my server
>aren't used by my client.
>
>Does anyone know where the information gotten by emerge --sync is stored?
>

I'm pretty sure emerge --sync pulls ebuilds into /var/db/repos/gentoo,
as for the files the ebuild mentions they are usually downloaded into
/var/cache/distfiles and for the patches, they are located into
/var/db/repos/gentoo/[category]/[package]/files. Built packages are put
into /var/db/pkgs. I'm unsure where anything else would go.

--
Kusoneko
https://kusoneko.moe

GPG Fingerprint: 5F58 0A60 4D06 074D F624 3526 8FDE CBBC 178C 72E1
Fediverse: @kusoneko@misskey.kusoneko.moe
XMPP&E-Mail: kusoneko@kusoneko.moe

https://email.is-not-s.ms

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?