From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C675B59CA3 for ; Fri, 11 Mar 2016 02:41:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 01AEE21C019; Fri, 11 Mar 2016 02:40:48 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CC868E0869 for ; Fri, 11 Mar 2016 02:40:46 +0000 (UTC) Received: from localhost (unknown [100.42.98.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: chutzpah) by smtp.gentoo.org (Postfix) with ESMTPSA id 4A65734091A; Fri, 11 Mar 2016 02:40:45 +0000 (UTC) Date: Thu, 10 Mar 2016 18:40:31 -0800 From: Patrick McLean To: Brian Dolbec Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Repoman rewrite stage3. Migrate check data to the tree Message-ID: <20160310184031.4c9dd658@gentoo.org> In-Reply-To: <20160310183007.027bb5f1.dolsen@gentoo.org> References: <20160310183007.027bb5f1.dolsen@gentoo.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 6c2c3f2f-7fc4-4129-b874-883b3f9fd0e7 X-Archives-Hash: 34c164443e81158a957b7318b0122dc0 On Thu, 10 Mar 2016 18:30:07 -0800 Brian Dolbec wrote: > So, where do we place this directory and what rules do we > establish about it's modifications? > > location? : in the metadata dir alongside the install-qa-check.d > directory? That sounds reasonable to me, it is certainly metadata. > > name of the directory? : repoman, qa-rules, qa-data, > repo-qa-data, ... ideas? Something not project name specific, so nothing about repoman. Perhaps something like "repo-checks", my personal vote would be make it a directory with the contents being merged (so repo-checks.d maybe?) > > data format? : json (my favorite) > compatible with many lanquages/interfaces > is flexible to match various data types > ie: dictionaries, lists, strings... > is human readable/editable > can be validated > > xml (PLEASE NO!) > > native python file (too language dependant) > > ini style (python configparser compatible) meh :/ > > other ideas? YAML - like JSON but made to be edited/read by humans (comment support is a big feature). Also valid JSON is valid YAML. Also can be validated just like JSON can.