From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: bug#33848: Store references in SBCL-compiled code are "invisible" Date: Thu, 27 Dec 2018 11:37:18 +0100 Message-ID: <8736qji7c1.fsf@ambrevar.xyz> References: <87r2e8jpfx.fsf@gnu.org> <877eg0i43j.fsf@netris.org> <87d0psi1xo.fsf@gnu.org> <874lb3kin6.fsf@ambrevar.xyz> <87sgynezha.fsf@gnu.org> <87tvj2yesd.fsf@netris.org> <877efwe04u.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55891) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gcT3G-00068B-Q7 for bug-guix@gnu.org; Thu, 27 Dec 2018 05:38:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gcT3C-00087L-BB for bug-guix@gnu.org; Thu, 27 Dec 2018 05:38:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:43121) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gcT3C-00085e-1w for bug-guix@gnu.org; Thu, 27 Dec 2018 05:38:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gcT3B-0008KZ-TZ for bug-guix@gnu.org; Thu, 27 Dec 2018 05:38:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <877efwe04u.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 33848@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > : > Store file names are always ASCII so problems arise when they are sto= red > : > as UTF-16 or UTF-32/UCS-4. > :=20 > : I understand that most programs stick to ASCII filenames, but what abou= t the odd > : one using non-English, special characters? >=20 > That=E2=80=99s a separate debate. :-) Essentially this restriction on s= tore > file names has always been there in Guix (and Nix before that). If we > were to change it, that would raise compatibility issues. But what happens if we attempt to store "=C3=A1" in the store? > For example I guess we could always store the file name as a literal > byte vector/list and add a call to turn that into a string. In the case of Next, that would be a simple patch, but other programs could= get much more complicated. In the end, this approach requires a linear amount = of work. Conversely, adding UCS-* support to the scanner would fix this issue= once and for all. > : > We did have a problem with Fish but I can no longer find it. Do you > : > remember what it was? Something with C++, no? > :=20 > : I think bug #30265. >=20 > Oh I see, UCS-4 as well. (I can=E2=80=99t believe this bug is still open= given > the relatively simple solutions outlined at > . :-)) Well, if currently only two packages out of 8500+ suffer from this, then I = think it's easier to go with Ludo's suggestion of patching the code to use ASCII strings. Does anyone know about more packages with this issue? It could also be that more packages suffer from this, unbeknownst to us. =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlwkq14ACgkQm9z0l6S7 zH9zbAf8C7alkC/FiNu4pb3HkuSWZXKkZ/pccOIXH0ErCiND6SwQC9pBXTgxoYew p9Y3J0SrKyUMVKHidWERkA1EnVR6wBUT3sru6idmiNF2JIBw5JC+UiNdiS5RqvXd Ka3eHjqxVXfL2kEINOOSoiB1t6P6chQsxHJjxOs9TTk+8UgFgDMF9VhtYubiaLYf oBOP7FVAIojHHGxth14ekyohT65TD4mgRqK3mTsLxPjrQ43/nAayo6aJWilx5BB1 YoRe8bjUNzHS1G0JSsM6E8ZRwwUfwBBhwdqFml2O76LpJoWi/xi358JNldRqD7j/ eV0ZNuJAZjONvVJZ9qtfJDifLPJkJQ== =IU/3 -----END PGP SIGNATURE----- --=-=-=--