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 (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1A02B158042 for ; Sat, 16 Nov 2024 22:05:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 56090E096A; Sat, 16 Nov 2024 22:05:47 +0000 (UTC) Received: from mail-qt1-f174.google.com (mail-qt1-f174.google.com [209.85.160.174]) (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 B5EDDE095F for ; Sat, 16 Nov 2024 22:05:46 +0000 (UTC) Received: by mail-qt1-f174.google.com with SMTP id d75a77b69052e-460e6d331d6so18102961cf.2 for ; Sat, 16 Nov 2024 14:05:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731794746; x=1732399546; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=ryB6whpqypIQUXZblL41VZRsev+D+ex42FKEMWdQChQ=; b=uhLSQudJv+S+BH4A/hMPzPatYiURlxy40s4edJkfLddDPrrr5y/g5o8z32FXE4sX/C b5mrVwL7RJfC/HNyBBrZFu+1dbpHeCyLUtMgs3gIrp7Ko5cLeJ3Tq9GRHYTuois6I1jt F9CaT74tjrUUQU4HLYDVth2XwOzPP46UWFcDgjV3DXJg1YotVhAqkxgphTuvKTcVKkY1 66aoUpXfleKK9qp+7W+uK98z/MrNR72EGMY+kre9EnnxFtwXuHSRA9Plbb2XiHayIg2b COioxnv7Z5MmPkdS00pS88T+5N1zlJdXCpKg+2oKuX/rN3wPBL5b5sORUOvj3eSapp/f tOmA== X-Gm-Message-State: AOJu0Yy1Rst5/hGBkPXeBq0lLEAyu4FQjwC2bmzOptR0vBLPA0tZpTKp Ff+s5S2U3/T2dm9xfVie/BRDBWZwoezZ+1s7BvAJKDRYQrf5RvuYskBxNkoLumXwN4Roa3RqoYA l X-Google-Smtp-Source: AGHT+IHxyZcTWTmARRrrwYC429o9aBWEGMbeuwhnXOMJDHYLYCO+jA9hZI9duflqMB2MyJtRhM11ug== X-Received: by 2002:a05:622a:19a0:b0:45d:9357:1cca with SMTP id d75a77b69052e-46363e0cd27mr89792511cf.14.1731794745773; Sat, 16 Nov 2024 14:05:45 -0800 (PST) Received: from [192.168.1.20] (32-216-196-135.bng01.wlmn.ct.frontiernet.net. [32.216.196.135]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7b35c99c6easm302039685a.31.2024.11.16.14.05.43 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 16 Nov 2024 14:05:44 -0800 (PST) Message-ID: <28995acc-18ab-476e-a6fb-6d71b2a3c7da@users.sourceforge.net> Date: Sat, 16 Nov 2024 17:04:43 -0500 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: gentoo-user@lists.gentoo.org From: Jack Ostroff Subject: [gentoo-user] Question on ebuild naming/numbering Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: 51b88550-1bfc-429c-bb2c-72c16e16fa1a X-Archives-Hash: 9522b921861ce3bb7176f88bc8ff7962 There's been an update to the gkrellm mailing list about progress on the gtk3 conversion.  It seems much of the work is being done in a specific git branch.  If I want to create an ebuild to track that branch instead of master, what would be an appropriate numbering of that ebuild?  Just using a different name with 9999 would work - but then those two names would have to block each other, since I don't think they could co-exist.  Are there any examples I can look at?  Just adding something after the 9999 doesn't seem right, nor does something like 9998. Any thoughts or suggestions? Thanks.