(+martinvonz for visibility)

On Mon, Apr 13, 2020 at 07:23:45PM +0530, Pulkit Goyal wrote:
> Hey everyone,
>
> I hope you are doing well.
>
> I am working on implementing the ShareSafePlan
> (https://www.mercurial-scm.org/wiki/ShareSafePlan) which aims to fix
> bugs caused by shared repositories not sharing config and
> requirements. The plan page does a good job in explaining it.
>
> The plan is to share config files and requirements between shared
> repositories and introducing a repository requirement for that.
>
> Sharing config files
> ===============
>
> We need a way to share config of original repository with the shared
> ones. The idea is to make shared repositories read `.hg/hgrc` of
> original repository and add a `.hg/nonsharedrc` for that repository
> only config. This way, by default all configs are shared unless
> specified in a different non-shared file.
> Another way which I can think of is having a `.hg/store/hgrc` where
> user adds config to be shared among shares. This way the configs which
> user explicitly added to `.hg/store/hgrc` will be shared.
> Which one sounds better?

I suspect adding a new non-shared rc file is better, as it'd be
somewhat less surprising? I'm having trouble envisioning a usecase for
a non-shared config file, but that's probably lack of imagination on
my part.

>
> Sharing requirements
> =================
>
> The idea is to have `.hg/store/requires` and `.hg/requires` for store
> level and working copy requirements.
>
> Above mentioned work will introduce a new repository requirement
> `sharedsafe` which will convey that the repositories can be shared
> safely and preventing old clients from making shares of this repo.
> Initially the requirement thing will be gated behind a config option.
> The plan also involves teaching debugupgraderepo to upgrade
> repositories to use the new requirement.
>
> This is mostly a dump of the plan page and I look forward to various
> ideas, improvements and discussion around how to implement this plan.
>

This all seems sensible to me.

> Thanks!
> Pulkit
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel@mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Reply via email to