From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: broken references in jar manifests
Date: Tue, 20 Mar 2018 11:28:55 +0100 [thread overview]
Message-ID: <20180320112855.33d86b6f@scratchpost.org> (raw)
In-Reply-To: <87zi3qfwfi.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
(1) How about adding another file to the META-INF directory which is just
like manifest - just without the line breaks?
That could even be automated.
(2) Also, "jar -i" calculates an index for where which package is ("INDEX.LIST").
Is that also hard-word-wrapped? The specification
https://docs.oracle.com/javase/7/docs/technotes/guides/jar/jar.html#JAR%20Index
only mentions the 72 Byte limit for "manifest and signature files" and then specifies
Index File Specification separately.
Either would be good enough for the GC retaining the deps, right?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-20 10:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 17:11 broken references in jar manifests Ricardo Wurmus
2018-03-01 18:32 ` Gábor Boskovits
2018-03-01 18:54 ` Ricardo Wurmus
2018-03-01 19:08 ` Gábor Boskovits
2018-03-01 19:52 ` Ricardo Wurmus
2018-03-19 4:24 ` Chris Marusich
2018-03-19 4:47 ` Ricardo Wurmus
2018-03-02 13:18 ` Ludovic Courtès
2018-03-20 10:28 ` Danny Milosavljevic [this message]
2018-03-20 10:50 ` julien lepiller
2018-03-20 12:14 ` Danny Milosavljevic
2018-03-20 13:47 ` Ricardo Wurmus
2018-03-21 21:07 ` Danny Milosavljevic
2018-03-21 22:58 ` Ricardo Wurmus
2018-03-25 10:19 ` [PATCH] Create INDEX.LIST; Was: Fix " Danny Milosavljevic
2018-04-01 22:12 ` Chris Marusich
2018-04-18 13:25 ` Danny Milosavljevic
2018-05-06 18:09 ` Danny Milosavljevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180320112855.33d86b6f@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.