[gentoo-dev] Building a portage repo?

[gentoo-dev] Building a portage repo?

[alexmcwhirter]

In my work on a sparc64 port of Gentoo i have found it easier to just 
fork the portage repo, patch things, and merge upstream changes / 
resolve conflicts as they happen. The problem is that this isn't really 
the best way to test things on any kind of scale. My plan is to build a 
script that does the following.

1. pull latest portage tree from git
2. apply patches
3. merge new portage tree to rsync server for clients.

The issue is that pulling from git i seem to be missing a ton of data, 
I.E. manifests and metadata like news (i'm assuming news is metadata). 
What is the utility that is used to take the git tree and generate all 
of this metadata, egencache?

Am i correct in assuming that after applying patches, running repoman 
and subsequently egencache should give me the same type of portage tree 
that is currently officially distributed to users?

Re: [gentoo-dev] Building a portage repo?

[Michał Górny]

Dnia 14 września 2016 09:01:43 CEST, alexmcwhirter@triadic.us napisał(a):
>In my work on a sparc64 port of Gentoo i have found it easier to just 
>fork the portage repo, patch things, and merge upstream changes / 
>resolve conflicts as they happen. The problem is that this isn't really

Portage is the package manager. The repository is named gentoo. Please use correct names because till the last paragraph, I thought you were actually referring to the package manager (and wtf-ed why would you distribute its sources via rsync).

>
>the best way to test things on any kind of scale. My plan is to build a
>
>script that does the following.
>
>1. pull latest portage tree from git
>2. apply patches
>3. merge new portage tree to rsync server for clients.
>
>The issue is that pulling from git i seem to be missing a ton of data, 
>I.E. manifests and metadata like news (i'm assuming news is metadata). 
>What is the utility that is used to take the git tree and generate all 
>of this metadata, egencache?
>
>Am i correct in assuming that after applying patches, running repoman 
>and subsequently egencache should give me the same type of portage tree
>
>that is currently officially distributed to users?

Partially. You probably need to update layout.conf, to get desired manifest format first. Then remanifest, egencache with all options. You will also need to include additional repositories for news, glsas and fetch extra files for projects.xml.

Generally, it's easier to fetch https://github.com/gentoo-mirror/gentoo that has all the extra content included. However, if you want it 100% rsync compliant, you will still have to patch layout.conf and remanifest.

Also note that the manifest format will be subject to change in the future, to support fully GPG-signed repository.


-- 
Best regards,
Michał Górny (by phone)

Re: [gentoo-dev] Building a portage repo?

[alexmcwhirter]

On 2016-09-14 03:40, Michał Górny wrote:
> Portage is the package manager. The repository is named gentoo. Please
> use correct names because till the last paragraph, I thought you were
> actually referring to the package manager (and wtf-ed why would you
> distribute its sources via rsync).

Sorry, it's been a long night.

> Generally, it's easier to fetch
> https://github.com/gentoo-mirror/gentoo that has all the extra content
> included. However, if you want it 100% rsync compliant, you will still
> have to patch layout.conf and remanifest.
> 
> Also note that the manifest format will be subject to change in the
> future, to support fully GPG-signed repository.

I was unaware of that repository, thanks for pointing it out. It makes 
much more sense to start there than trying to rebuild everything, at 
least while my changes stay small anyways.

[gentoo-dev] Re: Building a portage repo?

[Martin Vaeth]

Michał Górny <mgorny@gentoo.org> wrote:
>>
>>and subsequently egencache should give me the same type of portage tree
>>that is currently officially distributed to users?
>
> Then remanifest, egencache with all options. You will also need to
> include additional repositories for news, glsas and fetch extra files
> for projects.xml.

Not to forget dtd and xml-schema.
There is app-portage/portage-postsyncd-mv in the mv overlay
which does all this (and some more) for you in various
(separately configurable) hooks in /etc/portage/repo.postsync.d/*
Well, all except changing the manifest format and remanifest,
but you can easily add another hook if you really want that.