From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.218.138 with SMTP id hq10cs19880icb; Sat, 18 Dec 2010 12:12:44 -0800 (PST) Received: by 10.224.2.209 with SMTP id 17mr2378885qak.94.1292703164118; Sat, 18 Dec 2010 12:12:44 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id g11si3715811qcq.144.2010.12.18.12.12.43; Sat, 18 Dec 2010 12:12:44 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id C7A4318583C0; Sat, 18 Dec 2010 15:12:43 -0500 (EST) Received: from www.cquest.utoronto.ca (www.cquest.utoronto.ca [192.82.128.5]) by rubyforge.org (Postfix) with ESMTP id 263F818583BC for ; Sat, 18 Dec 2010 15:12:35 -0500 (EST) Received: from pinkfloyd.chass.utoronto.ca ([128.100.160.254]:58497 ident=93) by www.cquest.utoronto.ca with esmtp (Exim 4.43) id 1PU38s-0003gq-Rd for sup-talk@rubyforge.org; Sat, 18 Dec 2010 15:12:34 -0500 Received: from bwalton by pinkfloyd.chass.utoronto.ca with local (Exim 4.72) (envelope-from ) id 1PU38s-0002UL-Qo for sup-talk@rubyforge.org; Sat, 18 Dec 2010 15:12:34 -0500 From: Ben Walton To: sup-talk In-reply-to: <1292702329-sup-1169@tilus.net> References: <1271023429-sup-9851@zyrg.net> <1271249704-sup-1088@masanjin.net> <1271254358-sup-3024@pinkfloyd.chass.utoronto.ca> <1271260552-sup-9153@masanjin.net> <1271261164-sup-4109@pinkfloyd.chass.utoronto.ca> <20101215081955.GF568@icsi.berkeley.edu> <1292432651-sup-6834@jamestaylor.org> <20101218051216.GS60419@icsi.berkeley.edu> <1292649662-sup-8863@jamestaylor.org> <20101218190427.GU60419@icsi.berkeley.edu> <1292699674-sup-8221@pinkfloyd.chass.utoronto.ca> <1292702329-sup-1169@tilus.net> Date: Sat, 18 Dec 2010 15:12:34 -0500 Message-Id: <1292703012-sup-2641@pinkfloyd.chass.utoronto.ca> User-Agent: Sup/git Subject: Re: [sup-talk] current state of synching upstream? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Tero Tilus's message of Sat Dec 18 15:02:46 -0500 2010: > Ben Walton, 2010-12-18 21:21: > > The only downside to this is that my sources.yaml file needs manual > > twiddling at restart to add the sources that were added during > > runtime. > > How come? For what I know sup should save sources.yml (the call to > SoureManager.save_sources is in Index.save) upon graceful exit. > That's exactly how sup-add modifies sources.yml. I'm not sure as I haven't had the time to look into it. I only discovered this after the first time sup restarted after adding this hook (a few months later). I rarely restart sup and when I do, I don't usually have time to poke at the problem (work mail and all...). I might be able to just make the SourceManager.save_sources call manually. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk