Just FYI: lens 4.x is now the default version, and it's used to build
all packages except 'diagrams', which still requires lens 3.x. According
to https://github.com/diagrams/diagrams-core/issues/56, this is about
to be remedied, though, and then we can drop lens 3.x altogether.
I hope this helps,
Hi,
Thanks Peter, this is great!
Have a nice weekend,
Gergely
On Fri, 28 Feb 2014 20:53:41 +0100, Peter Simons sim...@cryp.to writes:
Just FYI: lens 4.x is now the default version, and it's used to build
all packages except 'diagrams', which still requires lens 3.x. According
to
Hi,
I tried to fix up diagrams-lib today for 2 hours without success. The
lens4 patch from their git doesn't apply cleanly to 1.0 and after fixing
the conflicts it doesn't build with a type error. I tried to track down
the type error, but I failed in the amount of time that I wanted to
spend on
Hi Gergely,
I tried to fix up diagrams-lib today for 2 hours without success. The
lens4 patch from their git doesn't apply cleanly to 1.0 and after fixing
the conflicts it doesn't build with a type error. I tried to track down
the type error, but I failed in the amount of time that I
Hi Gergely,
I applied your patch, but now we've run into pretty much the same
problem with diagrams-lib, too:
http://hydra.cryp.to/build/41431
Are you aware of a simple solution for this?
Take care,
Peter
___
nix-dev mailing list
Hi Gergely,
Can you give me a list of stuff that is currently not building
because diagrams is not building?
I believe that Chart-diagrams and SVGFonts are the only consumers of
diagrams in Nixpkgs.
Another solution is to just wait for diagrams people to upload a new
version to
Hi,
Peter: I saw that you started to upgrade stuff to lens 4, e.g. linear
1.6 requires it and in nixpkgs lens is now correctly overridden to
version 4 for that package.
However I wanted to ask for your transition plan/timeframe regarding
this change? Do you plan to switch over to lens4 as
Excerpts from Gergely Risko's message of Wed Feb 19 10:04:22 + 2014:
Asking this, because having both lens3 and lens4 can cause some
instances to be provided multiple times and that causes some pain. I
just ignored linear for now in my system, but I really would like to
minimize the
Hi,
On Wed, 19 Feb 2014 10:13:22 +, Marc Weber marco-owe...@gmx.de writes:
If this continues to be a problem you can give hack-nix a try which was
written for such cases (there are some other small issues, though).
If you can point me to source of some sample packages I can tell you
You're right, hack-nix assumes that there are too many variations of
building packages, which is why it allows to change flags for
individual targets. You're right, there are no binary caches, but once
a dependency got compiled its likely to be reused for other projects,
most libraries get
Gergely Risko gerg...@risko.hu writes:
Hi,
Peter: I saw that you started to upgrade stuff to lens 4, e.g. linear
1.6 requires it and in nixpkgs lens is now correctly overridden to
version 4 for that package.
However I wanted to ask for your transition plan/timeframe regarding
this change?
On Wed, 19 Feb 2014 12:14:46 +, Marc Weber marco-owe...@gmx.de writes:
You're right, hack-nix assumes that there are too many variations of
building packages, which is why it allows to change flags for
individual targets. You're right, there are no binary caches, but once
a dependency got
Hi Gergely,
I wanted to ask for your transition plan/timeframe regarding this
change? Do you plan to switch over to lens4 as default sometime and
provide overrides for the not forward compatible packages?
I'm running test builds at [1] right now. If those builds succeed (or
fail in a way
Hi Peter,
The build has finished with two failures: Chart and diagrams-core.
For Chart, just changing the dependency to 4.1 instead of 3.11 helped.
For diagrams-core a bit more hackery was needed, attached is a patch to
fix the current issues. I based this work on
14 matches
Mail list logo
