From nobody Sun Jan 29 22:45:49 2023 X-Original-To: python@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P4mcl1LVFz3cLdK for ; Sun, 29 Jan 2023 22:45:59 +0000 (UTC) (envelope-from einar@isnic.is) Received: from mx01.isnic.is (mx01.isnic.is [193.4.58.133]) (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 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx01.isnic.is", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P4mcj4kCKz3sw0 for ; Sun, 29 Jan 2023 22:45:57 +0000 (UTC) (envelope-from einar@isnic.is) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=isnic.is header.s=20200921 header.b=a4eqKit+; spf=pass (mx1.freebsd.org: domain of einar@isnic.is designates 193.4.58.133 as permitted sender) smtp.mailfrom=einar@isnic.is; dmarc=pass (policy=quarantine) header.from=isnic.is Received: from ht-mailstore01.isnic.is (ht-mailstore01.isnic.is [IPv6:2001:67c:6c:56::2]) by mx01.isnic.is (Postfix) with ESMTPS id 86C6942F65 for ; Sun, 29 Jan 2023 22:45:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isnic.is; s=20200921; t=1675032349; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9yqxPepB2o7nfkbX0JnoGGffh+zDcRBkNBOJMkK01zc=; b=a4eqKit+8u+pXlPWm5p/eJUqjnXgNqHKgN4z/r+02iih2djy8WcK4w99S9yybv7cMP/s9N KVwVUwYze83cfEanxdHnIlI9edjjU+hVAdBXfhG9po3eMS3z6qu1I6bNCYorgxJmYCmhiQ yUkP4ohjegQ6O7McfQ6I3P+VAljPo+WRixZkDV+UY9booUjN5lXGJ2nCZuEdFoApKVhrkW MaXRSIkBM9G99KmUtbiHvxMweXGlZ0iWhZZfvECfBDZv6r1vB8++vz2tz9tDydzB2fUI3Q eTnpzRsTKZDKTCv9eY6IRf5kgWuaMTZvsDwHWssyOoVCfru/AdeVPORCJrgkqw== Received: from [IPV6:2001:67c:6c:f100::194] (unknown [IPv6:2001:67c:6c:f100::194]) by ht-mailstore01.isnic.is (Postfix) with ESMTPS id 6BCAC57BE2 for ; Sun, 29 Jan 2023 22:45:49 +0000 (UTC) Message-ID: <40a4721e-cd7c-3a2d-3046-0cde58e39df4@isnic.is> Date: Sun, 29 Jan 2023 22:45:49 +0000 List-Id: FreeBSD-specific Python issues List-Archive: https://lists.freebsd.org/archives/freebsd-python List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-python@freebsd.org X-BeenThere: freebsd-python@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: CHEESESHOP or GH Content-Language: en-US To: python@freebsd.org References: <64297aed-bb04-fd7a-ebcc-f0ebc2979f85@freebsd.org> From: =?UTF-8?Q?Einar_Bjarni_Halld=c3=b3rsson?= In-Reply-To: <64297aed-bb04-fd7a-ebcc-f0ebc2979f85@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; DMARC_POLICY_ALLOW(-0.50)[isnic.is,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:193.4.58.0/23]; R_DKIM_ALLOW(-0.20)[isnic.is:s=20200921]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:1850, ipnet:193.4.58.0/23, country:IS]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[python@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[isnic.is:+]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[python@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4P4mcj4kCKz3sw0 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Hi Charlie, On 1/28/23 01:47, Charlie Li wrote: > I commented. This guideline isn't specific to python@ per se, but > something that applies to all ports: proper release distributions > (usually source tarballs) are preferred over source code management tags. > > For this port, you can go either way, but if you choose to fetch from > GitHub, make sure to add a comment in the Makefile explaining the > situation (and maybe reference the upstream issue). > > It's unfortunate when individual projects choose to disregard proper > release engineering practices. Part of our job as port maintainers is to > serve as that check-and-balance such that if projects want their stuff > in software repositories, they have to put some consideration as well. > Thank you very much. I saw your comment and learned alot from it. Hopefully it'll persuade them to change their mind. If not, I'll switch to fetching from github, but I'll make sure to add a comment to the Makefile explaining the situation. .einar