From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0621E158089 for ; Sat, 23 Sep 2023 14:02:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 03AA62BC07E; Sat, 23 Sep 2023 14:02:11 +0000 (UTC) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A157B2BC01B for ; Sat, 23 Sep 2023 14:02:10 +0000 (UTC) Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-5041bb9ce51so5880740e87.1 for ; Sat, 23 Sep 2023 07:02:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qap-la.20230601.gappssmtp.com; s=20230601; t=1695477729; x=1696082529; darn=lists.gentoo.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=TnrQAL9e1K2wZlYpF5uWREWEuy91TVFWLdjWR+vXNdE=; b=YIRIitrPwm8MBb1M0sFMo/pziKA6BjCj93qH3IwWpz0TCOI/Lxh32+6aqLkFkPtBGj m7tSA2PmctPRQBVNj9gBji4K/+f6DET7++nbbKdUy7fOnrXDMpGHQV/4JrnIQoIiGc3i ck+2COlOFZKV4AO5JQZ9Qk/sW5jHNKzE2t4s6zGRALVRBquC1MaGv0Kh8fvhSqNTfNQu TcbR2ObypdhxiGmSUUo9QVhbk2GmrSXT7EzvYN8Skjv0WKmixofKT9dLvMBH+ix7V/NQ pQHIfABNEtx9tv5iiXEx/lz2idY/1LQQg04ZvDLIe87s7aN0QH2+vOdBN07B6sfZsZma UqNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695477729; x=1696082529; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=TnrQAL9e1K2wZlYpF5uWREWEuy91TVFWLdjWR+vXNdE=; b=rwKMJPFcTzMLLjQtqRyXCYKV1rxvbVqIK/GHOgf9vvG0NJ5yYyfGD1+khrppDe7rkG y0pZ9NiV43UkdTxTRznc9IfSY+gZcv42qpbIzJfBzBIYCIAI4ceyOTuhdMaWleGa+UtX 4xkQFiZ/3qnwZzEuW+8QecNCaJZQzs/xCQxIi92xK9xGoTIEhHkLCqZMvFbOLYEkphpW E4hr/zghLmW4dr4YugO4nhZEKIaiN/07b4SgCeyeTIcDeE55w6ViPRPYPecPtn9EaeIS OL9rxPFy3DRCleKAvQmXUSR4d1dBveqIVD4VyZi0wPyiJXGJ65hXjOd6yaagMgld2Ihd AATA== X-Gm-Message-State: AOJu0YzsJ13IpBUh1bD+4Nr5i7nWwo3uNGizUu+SdIY/AOJKDkG796+f H1mlQakrZlI352DJI5rEna1ZNvrPg76MPZ/PBEQ35dleaoca5OqA X-Google-Smtp-Source: AGHT+IFMaTzmPXDUIa1T7efyw5/en+vICJQh14hzqCyGnJTcHJUruN1Wi1DQzA5lgjruo/ZlA+YX2IV5UoAd1dcoTO0= X-Received: by 2002:a05:6512:239f:b0:502:a0e9:8820 with SMTP id c31-20020a056512239f00b00502a0e98820mr2014062lfv.47.1695477728631; Sat, 23 Sep 2023 07:02:08 -0700 (PDT) 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <5b5dfbfd-9c7d-a26b-65e7-9f8c5e48bb8f@gentoo.org> <87msxfjix6.fsf@gentoo.org> <878r8yjohn.fsf@gentoo.org> <871qeqjmup.fsf@gentoo.org> In-Reply-To: From: Alex Boag-Munroe Date: Sat, 23 Sep 2023 15:01:57 +0100 Message-ID: Subject: Re: [gentoo-dev] Re: Standard parsable format for profiles/package.mask file To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 9c64b178-7187-4715-aa79-6fb2f04891f2 X-Archives-Hash: 4ef7292e24f76fd4de84e2c92d65535b On Sat, 23 Sept 2023 at 08:03, Ulrich Mueller wrote: > This seems rather restrictive, adds unnecessary redundancy, and would > make it hard to type an entry without the aid of special tools. > > Also, there are other files like use.mask which probably shouldn't have > a completely different format. Their entries often have the author/date > line plus a one line comment which says all that is needed. Adding > massive header blocks there would be excessive. > > IMHO Arthur's original proposal was fine. Let's not over-complicate > things. > > Ulrich I'm confused, you're against adding "massive header blocks" but you're fine with Arthur's 9 line entry but not my 8 line one. My idea was a stop gap to add something easily parsed once the comments are stripped but keeping the comments in place currently for backwards compatibility. Since parsing was part of the OP it made sense to me to suggest an "already existing made for humans to read/write while tools can already parse it" structure. What special tools do you think are needed to write it? I wrote the above in Kate after double checking the configparser docs. A standard template would be trivial. -- Ninpo