From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 48815 invoked by alias); 9 Mar 2017 17:31:42 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 48801 invoked by uid 89); 9 Mar 2017 17:31:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=our X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 09 Mar 2017 17:31:40 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6BD2761D1E; Thu, 9 Mar 2017 17:31:40 +0000 (UTC) Received: from deadbeef.usersys.redhat.com (ovpn-204-17.brq.redhat.com [10.40.204.17]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v29HVbwA014883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Mar 2017 12:31:39 -0500 Subject: Re: Questions about Sourceware To: "Frank Ch. Eigler" References: <367dc6b2-8d38-eaa9-40a9-a2adeb8a08c4@redhat.com> <20170309155526.GC3979@elastic.org> Cc: Frank Eigler , overseers@sourceware.org From: Marian Csontos Message-ID: <61cb52d7-b780-dcb5-5950-5ddf1852fc3d@redhat.com> Date: Thu, 09 Mar 2017 17:31:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170309155526.GC3979@elastic.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-q1/txt/msg00116.txt.bz2 On 03/09/2017 04:55 PM, Frank Ch. Eigler wrote: > Hi - > >> [...] >> For each ikiwiki there will be needed: >> 2 public accessible group writable git repos - setup and content, somewhere >> under $poject-home, linked from /git,... >> >> How to create them? >> - Ask overseers to have them created for us. > > ^^ this. > >> These will be checked out from the above git repos. As generated >> content, should this be under /sourceware/projects or is there >> another preferred location? > > There will be a project home directory made for you. Is it /sourceware/projects/lvm2-home ? Or more likely /sourceware/something-else/lvm2, which would make e.g. rsync bit easier ? Whatever, I can now start with scripting, and will update as we agree on the final locations. Will push to a git repo too, so if there is anyone setting another wiki, or cloning and contributing, it could be reused. Thanks! -- Martian > > >> And few more related questions: >> Shall I send you script(s) for */sourceware/infra/bin/*? >> ...and if so, as ikiwiki's auto.setup is interactive, is command >> line preferred, or is interactive accepted as well? > > Do these need to go into infra/bin? If they are for ikiwiki only, > you could put them under some /bin subtree of your own. > >> [...] >> May I ask, why sourceware does not use gitweb's automatic repo search? > > Not sure; maybe that wasn't available in the prehistoric versions when > we first set them up. > >> Would it mean less work for you, if groups had group writable >> directory under /git, /sourceware/www/sourceware/htdocs/git/,...? >> [...] > > It depends on how many such repos you will end up needing. If it's > just the one or two, don't worry about it; our symlink widgetry will > do. If it's a slew, then something like the cygwin-apps/ structure > will be needed. > > > - FChE >