But I have to change the libtool expression anyway, since the unpackCmd is not working on OpenBSD. This also triggers an expensive rebuild, since there are many packages that have libtool as build-time dependency. Another option is to create another OpenBSD specific libtool component and use that instead, but I really doubt if this is very useful.
But if I'd make the adaptions to the setup.sh now, everything should be hopefully rebuild by the weekend :-) -----Oorspronkelijk bericht----- Van: Eelco Dolstra [mailto:[email protected]] Verzonden: vr 16-10-2009 19:57 Aan: Sander van der Burg - EWI CC: [email protected] Onderwerp: Re: [Nix-dev] *.tar.lzma archives Hi, Sander van der Burg - EWI wrote: > I noticed that *.tar.lzma tarballs are becoming more common now, so I > thought it would be very useful to add a *.tar.lzma option to the > genericBuilder. I suggest this, because I noticed that certain packages > such as libtool provide their own unpack commands. The libtool unpack > command, however, does not work on OpenBSD since the -f option is not > passed to the tar command (yes, we have more platforms now in the > buildfarm). If you want to do setup.sh changes in the trunk without causing lots of disruption, just clone it and use the overrideSetup function for packages that need it. You can even make it the default for the stdenv on OpenBSD. We can merge the changes back into setup.sh during the next stdenv branch merge. -- Eelco Dolstra | http://www.st.ewi.tudelft.nl/~dolstra/
_______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
