Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100112
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.195 as permitted sender)
To: Anatol Belski <ab@php.net>, Sara Golemon <pollita@php.net>,
 Remi Collet <remi@php.net>
Cc: PHP internals <internals@lists.php.net>
References: <HE1PR02MB1052738F154F495E4B061B40BABC0@HE1PR02MB1052.eurprd02.prod.outlook.com>
Message-ID: <519cc2c4-2547-1160-2d61-161cee28dfe6@gmail.com>
Date: Sat, 29 Jul 2017 13:15:33 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <HE1PR02MB1052738F154F495E4B061B40BABC0@HE1PR02MB1052.eurprd02.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Size of release tarballs
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Lately there was a discovering about some files causing size growth
> of the release tarballs
> https://github.com/php/php-src/commit/469206c84e502e3e349655b802899d5e4d560f72
> . Usually we strive to keep tarballs as small as possible and avoid
> disproportional growth of the size. This case seems to be of the
> exact nature. I would like to ask for an explicit response from RMs
> on this case.

I'd say we probably should not include multi-megabyte images in the
distros. Most tests should be fine with a small image.

> Perhaps it were also a good point to discuss a way to prevent big
> binary files to land in the repo. So far some files in the repo can

I think we can handle it in the old-fashioned way now - just notify the
RMs and clean up the repos.

-- 
Stas Malyshev
smalyshev@gmail.com