IRC channel logs


back to list of logs

<civodul>Hello Guix!
<atheia>Morning Guixers
<rekado_>For a gcj-jdk wrapper package I need a wrapper around gcj that behaves like javac. Gentoo has one, but there is no other source than this:
<rekado_>This is rather short and I wonder if I should simply write a guile script instead. How is a snippet like this to be included in a package definition?
<civodul>rekado_: similar to patches: make it a file, and add it to the inputs of the package
<civodul>see how ld-wrapper.scm is used, for instance
<civodul>however, we don't really have a convention for where to store such files
<civodul>FWIW, i package gcj and attempted IcedTea in Nixpkgs in the old days
<civodul>apparently icedtea includes a 'javac' wrapper already
<civodul>it might be simpler to package icedtea rather openjdk
<rekado_>civodul: icedtea7 includes a javac wrapper, but icedtea6 does not. (I'm working on both atm.)
<rekado_>I have packaged gcj and gcj-jdk as well as a couple of dependencies for icedtea6/7 already. The build of IcedTea7 fails after 20 minutes when linking some library with GCJ, so I'm trying to build IcedTea6 first, and then use IcedTea6 to build IcedTea7.
<civodul>well, that's impressive!
*davexunit reads mailing list thread about optional runtime dependencies
<davexunit>civodul: the use-flags example code was similar to something I had in mind.
<davexunit>I don't know how to make that particularly usable, though.
<davexunit>and wouldn't it have effects on our build farm? what use-flags would that use?
<civodul>davexunit: yeah we'd have to specify which combinations should be built by Hydra
<civodul>but obviously, not everything would be built
<civodul>that said, the example i gave is not very nice to read
<civodul>would be nice to come up with extra syntax to simplify that sort of things
*civodul rushes back home