Date: Sun, 29 Jan 2023 22:45:49 +0000 From: =?UTF-8?Q?Einar_Bjarni_Halld=c3=b3rsson?= <einar@isnic.is> To: python@freebsd.org Subject: Re: CHEESESHOP or GH Message-ID: <40a4721e-cd7c-3a2d-3046-0cde58e39df4@isnic.is> In-Reply-To: <64297aed-bb04-fd7a-ebcc-f0ebc2979f85@freebsd.org> References: <a149ebe7-7127-3c75-7526-0822d8babc5b@isnic.is> <64297aed-bb04-fd7a-ebcc-f0ebc2979f85@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40a4721e-cd7c-3a2d-3046-0cde58e39df4>