From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:34578) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hmy7P-0007Wq-ON for guix-patches@gnu.org; Mon, 15 Jul 2019 06:22:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hmy7O-0006ZN-FF for guix-patches@gnu.org; Mon, 15 Jul 2019 06:22:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37654) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hmy7O-0006ZA-9R for guix-patches@gnu.org; Mon, 15 Jul 2019 06:22:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hmy7O-0007x3-3v for guix-patches@gnu.org; Mon, 15 Jul 2019 06:22:02 -0400 Subject: [bug#33899] [PATCH 0/5] Distributing substitutes over IPFS Resent-Message-ID: Date: Mon, 15 Jul 2019 10:21:29 +0000 From: Hector Sanjuan Message-ID: In-Reply-To: <87zhlf7glw.fsf@ambrevar.xyz> References: <20181228231205.8068-1-ludo@gnu.org> <8736pqthqm.fsf@gnu.org> <87zhlxe8t9.fsf@ambrevar.xyz> <87ftnbf1rt.fsf@gnu.org> <87ef2rr6om.fsf@gnu.org> <87zhlf7glw.fsf@ambrevar.xyz> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Hector Sanjuan Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Pierre Neidhardt Cc: Antoine Eiche , "go-ipfs-wg\\@ipfs.io" , "33899\\@debbugs.gnu.org" <33899@debbugs.gnu.org> =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Monday, July 15, 2019 12:10 PM, Pierre Neidhardt wro= te: > H=C3=A9ctor mentioned a possible issue with the IPLD manifest growing too= big > (in case of too many files in a package), that is, above 2MB. > Then we would need to implement some form of sharding. > > H=C3=A9ctor, do you confirm? Any idea on how to tackle this elegantly? > Doing the DAG node the way I proposed it (referencing a single root) should= be ok... Unless you put too many executable files in that list, it should larg= ely stay within the 2MB limit. -- Hector