Re: [gentoo-portage-dev] Re: How to have several gentoo repos on one machine?

[Joakim Tjernlund <joakim.tjernlund@transmode.se>]

On Thu, 2015-10-22 at 02:29 +0000, Duncan wrote:
> Joakim Tjernlund posted on Wed, 21 Oct 2015 11:08:02 +0000 as excerpted:
> 
> > I need to more than one gentoo repo in my computer.
> > 
> > So I add to repos.conf:
> >  [tm-cusfpv3]
> >  auto-sync = yes
> >  sync-type = rsync
> >  sync-uri = rsync://devsrv.transmode.se/tm-cusfpv3
> >  location = /usr/local/portage/tm-cusfpv3
> > 
> > this did not work as "portageq repositories_configuration /" complains:
> > !!! Section 'tm-cusfpv3' in repos.conf has name different from
> > repository name 'gentoo' set inside repository
> > 
> > I figured the name in repos.conf would just override
> > /usr/local/portage/tm-cusfpv3/profiles/repo_name ?
> 
> While it's not quite clear to me either why you'd need two identical 
> gentoo repos (and if they're not identical, why is the non-gentoo-
> official mirror still using the gentoo name?) or exactly what this config-
> line does, the aliases= attribute, along with force=aliases, in 
> repos.conf, may be what you're looking for.

I use one for my host and the other for cross building our products root FS
and they are not in sync. That rules out the aliases I guess?

> 
> See the portage (5) manpage, repos.conf section, attributes supported in 
> sections of repositories subsection, under aliases and force.  
> Unfortunately, the description for aliases is anything but clear, tho the 
> usage (including comment) further down in the example subsection does 
> help some.
> 
> If that doesn't help, then while the portage devs may have some other 
> suggestions, the workaround that occurs to me is to use rsync's exclude/
> filter options, so rsync ignores that file and doesn't sync it.  I do[1] 
> that with a few custom files/dirs that I don't want synced, and rsync 
> ignores them just as I told it to. =:^)

Right, I will test this but I consider it an workaround and it will only
work with rsync.

> 
> See the rsync (1) manpage, --exclude, --exclude-from, --include, --
> include-from and --filter=RULE options, as well as the filter rules, 
> include/exclude pattern rules, and anchoring include/exclude patterns 
> sections.  However, be prepared to spend a bit of time studying, as these 
> options are very powerful/flexible/configurable and thus take some time 
> to figure out.
> 
> Once you have rsync ignoring the repo_name file, you can rename it as you 
> like.

I don't plan on renaming anything in the repo_name file, it should just
be ignored and the name I have select in repos.conf should used.

I don't see any value in repo_name file now that we have the new repos.conf,
possibly it could be a fallback only for PORTDIR users.

> 
> However, do be aware that (as the repos.conf force option docs mention) 
> messing with this is very likely to invalidate the pre-generated metadata 
> cache, and if you don't regenerate it (egencache), portage will take a 
> *VERY* long time figuring stuff out, *MUCH* longer than usual, as it 
> won't have the benefit of the metadata cache for that repo.

OK, will have to look into that. Our main use will be binary pks only and
even this is slow. emerge is usling a lot of time to figure out what to
update even when using binary packets only(even when PKGDIR is empty or almost empty)

> 
> Which again has me asking why you need two separate gentoo repos.  Either 
> they're identical and the one should suffice, or the unofficial one 
> should be named something other than gentoo.  In fact, at least in 
> theory, in addition to all the headaches not using a different name is 
> forcing on users, that's potentially trademark violation if it's publicly 
> available, different from the official gentoo mirror, and yet still 
> calling itself gentoo.
> 
> ---
> [1] rsync exclude options: I actually use gentoo's git-based usersync repo 
> on github, now, and thus don't rsync any repos all any more, here, and 
> git of course has its git-ignore feature/files, which I use now.  But I 
> used rsync's exclude as suggested above, for years.  Worked fine. =:^)

Nice, I am heading the same was, using git all the way but I not there yet.
One problem is that using git is disk space I think. Files are just
ignored but still present in the repo so syncing to our embedded target
will take a lot more space. 
Any thoughts on that?

 Jocke