Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] Removing support for mercurial repos in repositories.xml
Date: Sat, 29 Sep 2018 07:45:17
Message-Id: 1538207086.1199.0.camel@gentoo.org
In Reply to: Re: [gentoo-dev] [RFC] Removing support for mercurial repos in repositories.xml by desultory
1 On Fri, 2018-09-28 at 23:44 -0400, desultory wrote:
2 > On 09/27/18 10:21, Michał Górny wrote:
3 > > On Fri, 2018-09-28 at 01:50 +1200, Kent Fredric wrote:
4 > > > On Mon, 24 Sep 2018 07:59:46 +0200
5 > > > Michał Górny <mgorny@g.o> wrote:
6 > > >
7 > > > > I'm against dumb timeouts. Good timeout = die if nothing happens for T.
8 > > > > Bad timeout = die if process doesn't finish for T (yet it may still be
9 > > > > doing something).
10 > > >
11 > > > Could you perhaps adjust it so that when the timeout limit is exceeded,
12 > > > the sync is aborted, and the sync status of that repository is flagged
13 > > > as "bad", and notifies you somehow to fix it manually at your leisure,
14 > > > but otherwise ceases to impede the progress of all the other
15 > > > repositories?
16 > > >
17 > > > And if you're worried that a sync interruption midway could cause a
18 > > > dirty state, maybe you could do an rsync trick where mercurial repos
19 > > > are rsynced into a sandbox location, and then only rsynced back into
20 > > > place on success?
21 > > >
22 > > > This process lets you go "sure, it may be doing something, but it took
23 > > > too long anyway, so we'll let somebody with brains work it out and
24 > > > pretend it was broken in the interim"
25 > >
26 > > No.
27 > >
28 >
29 > Elucidate.
30
31 My time is better spent elsewhere. You want mercurial, you fix it.
32 This is open source, you can write the patches.
33
34 --
35 Best regards,
36 Michał Górny

Attachments

File name MIME type
signature.asc application/pgp-signature