Branch: refs/heads/staging
Home: https://github.com/NixOS/nixpkgs
Commit: 1712366bac9fabd51543545615b1ba3bccdc8776
https://github.com/NixOS/nixpkgs/commit/1712366bac9fabd51543545615b1ba3bccdc8776
Author: Anthony Cowley <acow...@gmail.com>
Date: 2016-12-07 (Wed, 07 De
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 29572c28a39b6c1aec15fccf324cbb6d75228988
https://github.com/NixOS/nixpkgs/commit/29572c28a39b6c1aec15fccf324cbb6d75228988
Author: Anthony Cowley <acow...@gmail.com>
Date: 2016-08-17 (Wed, 17 Au
Peter Simons writes:
> Hi Anthony,
>
> >> [What is] a concrete use case that works for you today but that
> >> won't work after LTS-4 has been dropped?
> >
> > Someone who has a project that works with package versions in LTS-4,
> > but hasn't yet been upgraded to LTS-5 or 6. They can
Peter Simons writes:
> Hi Anthony,
>
> > I draw a distinction between newer minor versions obsoleting old ones
> > for purposes of bug fixes vs. for purposes of freezing packages.
>
> I am sorry, but I don't understand that distinction. In your original
> response you suggested that dropping
Peter Simons writes:
> Fellow Haskell Hackers,
>
> once the LTS 7.x package set comes out, I intend to make the following
> changes in "master":
>
> - All haskell.packages.lts.* package sets will disappear.
>
> - haskellPackages will loosely follow the most recent LTS release,
>
> where
Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: 7b56411fef87d7ab775640117bf461aaeb4a55e1
https://github.com/NixOS/nixpkgs/commit/7b56411fef87d7ab775640117bf461aaeb4a55e1
Author: Anthony Cowley <acow...@gmail.com>
Date: 2016-05-21 (Sat, 21 Ma
> On Feb 20, 2016, at 3:20 PM, Kosyrev Serge <_deepf...@feelingofgreen.ru>
> wrote:
>
> Anthony Cowley <acow...@gmail.com> writes:
>> Bringing together what Thomas and Freddy say here, it seems to me that
>> a rather ideal mixture would be something unst
Bringing together what Thomas and Freddy say here, it seems to me that a rather
ideal mixture would be something unstructured like a wiki with buttons for
readers saying, "This helped me" or "This did not work".
The point being that once a wiki item gets a handful of positive votes, it gets
> On Oct 2, 2015, at 10:26 AM, Daniel Peebles wrote:
>
> If nobody objects, I think we should just switch over. The only people
> interested in maintaining the darwin ecosystem on Nix don't really want to
> have to maintain two parallel stdenvs, and unless someone
into the local sandbox.
Anthony
On Feb 24, 2015 11:57 PM, Mateusz Kowalczyk fuuze...@fuuzetsu.co.uk
wrote:
On 02/25/2015 03:01 AM, Anthony Cowley wrote:
This almost certainly isn't ready for release, but I'd like to avoid
duplicating efforts if other people want to work on it...
Here
This almost certainly isn't ready for release, but I'd like to avoid
duplicating efforts if other people want to work on it...
Here is cabbage https://github.com/acowley/cabbage
It is a tool for doing the obvious thing: use the cabal solver to find
a build plan, then build the specific version
This almost certainly isn't ready for release, but I'd like to avoid
duplicating efforts if other people want to work on it...
Here is cabbage https://github.com/acowley/cabbage
It is a tool for doing the obvious thing: use the cabal solver to find
a build plan, then build the specific version
12 matches
Mail list logo