[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: broken references in jar manifests
From: |
Ricardo Wurmus |
Subject: |
Re: broken references in jar manifests |
Date: |
Tue, 20 Mar 2018 14:47:41 +0100 |
User-agent: |
mu4e 1.0; emacs 25.3.1 |
Danny Milosavljevic <address@hidden> writes:
> Hi Julien,
>
> On Tue, 20 Mar 2018 11:50:51 +0100
> julien lepiller <address@hidden> wrote:
>
>> The issue is with grafts here: the plain file with full reference to the
>> store
>> gets grafted and contains the new entry. The Manifest will not be
>> updated because
>> of line breaks, and Java will still look for the version in the
>> manifest. The GC
>> will collect it because it doesn't see any reference to the old version
>> in any
>> file (because of line breaks), and the package is broken.
>
> Oh okay, so there are two problems.
Well, they are closely related. One is that we don’t keep references
because they are broken up in the manifest; this is a minor problem,
because we can propagate inputs. The more important problem is that it
breaks grafts.
> (The specification says that INDEX.LIST is preferred if it exists)
Interesting. It’s worth playing with it.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
- Re: broken references in jar manifests, (continued)
Re: broken references in jar manifests, Ludovic Courtès, 2018/03/02
- Re: broken references in jar manifests, Danny Milosavljevic, 2018/03/20
- Re: broken references in jar manifests, julien lepiller, 2018/03/20
- Re: broken references in jar manifests, Danny Milosavljevic, 2018/03/20
- Re: broken references in jar manifests,
Ricardo Wurmus <=
- Re: broken references in jar manifests, Danny Milosavljevic, 2018/03/21
- Re: broken references in jar manifests, Ricardo Wurmus, 2018/03/21
- [PATCH] Create INDEX.LIST; Was: Fix references in jar manifests, Danny Milosavljevic, 2018/03/25