As far as I know, there is still a lot of churn on pure darwin. Dan, if we wanted to merge pure darwin soon (say, maybe this or next week) could you a) get it ready in time and b) adopt a new workflow where future major changes were made and merged in single-feature chunks? I want to avoid a long-term situation where a lot of unconnected changes come in as a set and switch to a feature branch model once pure-darwin is in.
~Shea > On Feb 3, 2015, at 3:03 PM, Wout Mertens <[email protected]> wrote: > > Ouch. So users on 10.10 should use Zalora and disable hydra binaries? > > Perhaps we should fast-track the pure-darwin builds. It works swimmingly on > my system, and looks like the current Darwin situation is not tenable. So > anything in pure-darwin that breaks Linux would be good to find early. > > On Tue Feb 03 2015 at 4:00:48 PM Shea Levy <[email protected] > <mailto:[email protected]>> wrote: > I’m not sure about butters. Either way a single cache will not do the trick, > as until pure-darwin lands binaries will be specific to the version of OS X > they are compiled for. In particular, the zalora cache builds for 10.10. > >> On Feb 3, 2015, at 2:59 PM, Wout Mertens <[email protected] >> <mailto:[email protected]>> wrote: >> >> I see that the darwin machine butters is online (and idle) in Hydra, does >> that mean the zalora cache is no longer needed for nixpkgs on Darwin? >> >> On Tue Feb 03 2015 at 3:51:47 PM Domen Kožar <[email protected] >> <mailto:[email protected]>> wrote: >> :beers: >> >> On Tue, Feb 3, 2015 at 3:40 PM, Shea Levy <[email protected] >> <mailto:[email protected]>> wrote: >> Hi all, >> >> For a while now, there has been a lot of work to improve darwin support on >> the master branch of joelteon’s nixpkgs fork. With the latest staging merge, >> the core of that work is now on upstream master. The rest of the changes >> available on joelteon’s fork are very disparate, and it is not clear whether >> or why they are all needed, so I’d like to request that those who have been >> working off of the fork test their setups against upstream now. If something >> is still not working, please at least open an issue, but if you can find the >> relevant fix on the fork and port it as a PR that would be greatly >> appreciated. >> >> Hopefully we can soon move on from that fork entirely and have further >> changes (including the ongoing pure-darwin work) done directly against >> upstream master. >> >> Thanks, >> Shea >> _______________________________________________ >> nix-dev mailing list >> [email protected] <mailto:[email protected]> >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> <http://lists.science.uu.nl/mailman/listinfo/nix-dev> >> >> _______________________________________________ >> nix-dev mailing list >> [email protected] <mailto:[email protected]> >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> <http://lists.science.uu.nl/mailman/listinfo/nix-dev> >
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
