-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hiya,
First off, thanks everybody for the suggestions. It seems like people aren't keen to mirror the large tables on our mirrors, but no one's mentioned a reason for not doing so. Is there an infra reason behind that or did everyone just take my caution and run with it? On 16/10/13 02:40, Chí-Thanh Christopher Nguyễn wrote: > I suggest that you add a "large" USE flag, and if it is enabled, > download and install the whole thing. If disabled, just print the > URLs in a log message, so the user can download themselves if they > wish. So downloading them manually is a pain (the larger tables aren't in a single zip, they're split amongst 12 files for each table), and the ebuild to do the downloading is already built. I'll include a postinst note indicating that the tables are getting stored twice, and I should even be able to give them an indication of how much space they're wasting. I'll also provide a URL they can visit if they want to download manually instead. The question then becomes, do I split the ebuild into two (giving us three ebuilds for what is otherwise a tiny package) just so some SRCs are mirror-restricted and others aren't? All of that hinges on whether our servers can handle the extra size... Mike 5:) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlJeWR4ACgkQu7rWomwgFXq8bQCfRde/Tg7sAirqT05d5spckC+s fUIAoIH1SlXvLmM3CqM0x1vQN0oPdiKi =qqsa -----END PGP SIGNATURE-----
