[Nix-dev] Jar files

[Tomasz Kontusz]

Nix only scans for hashes, and there's a good chance they'll be kept intact when compressing.

If that's not good enough, then you'll have to make a file with references either by hand or by unpacking the jars. I don't know how often this will actually be needed - is Java retaining paths to dependencies after compilation?

Dnia 28 sierpnia 2015 15:02:19 CEST, Daniel Peebles <pumpkingod at gmail.com> napisał(a):
>Hi all,
>
>We don't have much of a Java presence in Nixpkgs, but I was thinking of
>growing it. This leads to what seems like a bit of a thorny issue: most
>java code is distributed in jars, which are glorified zip files. Can
>anyone
>see the problem?
>
>The one I'm afraid of is one of runtime dependencies: normally we're
>fine
>embedding other nix store paths in code, under the assumption that the
>literal string will show up somewhere in the resulting binary. If you
>zip
>the result, that's no longer true without smarter scanning logic.
>
>So is the solution to make our java packaging never produce any jars,
>and
>explicitly unpack any we encounter? That feels kind of gross.
>Alternately,
>we could have a post-processor that scans the unpacked zip files for
>store
>paths and then replicates them somewhere in nix-support. Also doesn't
>feel
>ideal!
>
>Are there other options? Am I misunderstanding something or is this
>really
>an issue?
>
>Thanks,
>Dan
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>nix-dev mailing list
>nix-dev at lists.science.uu.nl
>http://lists.science.uu.nl/mailman/listinfo/nix-dev

-- 
Wysłane za pomocą K-9 Mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20150828/27c7b07f/attachment.html