lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] Sharing git repositories


From: Vadim Zeitlin
Subject: Re: [lmi] Sharing git repositories
Date: Wed, 11 Mar 2020 01:13:03 +0100

On Tue, 10 Mar 2020 23:33:34 +0000 Greg Chicares <address@hidden> wrote:

GC> Wouldn't it make more sense to return to the original design intention,
GC> so that /var/cache_for_lmi/ would hold only bare repositories with
GC> 'core.sharedRepository' set for all? Thus, we'd:
GC>  - set up bare 'core.sharedRepository' repos on /srv/cache_for_lmi/ and
GC>  - bind-mount them as read-only inside each chroot
GC> For the wx repository, we'd only need to override this line:
GC>   
remote_host_url=${remote_host_url:-"https://github.com/wxWidgets/wxWidgets.git"}
GC> e.g. with
GC>   remote_host_url="file:///cache_for_lmi/vcs/wxWidgets.git"
GC> provided that such a file exists.

 Yes, this would work and would indeed be more logical.

GC> Would it be even better to use the local cache as a "reference repository"?

 I don't think it makes sense to use reference repository in this case, as
cloning locally just hardlinks the files anyhow, i.e. there shouldn't be
any increase in the disk consumption (you should be able to check it by
running "df" before and after cloning).

GC> Well...we'd have
GC>  - a single script to configure the "host" system
GC>  - a single script to create the debian-testing chroot
GC>  - a single script to be run once per user

 If you're fine with this, I surely am too. Ideally I'd also like to be
able to run the script to set up the official lmi build environment on my
own machine, without creating a new chroot (because I already have enough
of those), but it's just an extra side goal and not really a requirement,
as I can always tweak the script to fit my needs myself or just create
another chroot if really necessary.


 I've removed the rest of your message from this reply because there didn't
seem to be any questions there, but please let me know if I missed anything
and if there is still something you'd like to have my input on.

 Thanks,
VZ

Attachment: pgpGwUmsaox97.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]