[Nix-dev] Software development workflow -- the nix way?

[Kyle Heath]

Hi Nix Folks,

*short version:*
*
*
I would like to enable the following development workflow...

1. I write packages of code containing java, c++, python binary and library
targets (and probably host them on github)
2. I include with each package a build script that will provide all it's
dependencies via nix packages - (either from the official nix repository or
from my own public repository of nix packages)
3. I can release source and binary versions of my packages by tagging them
on github and publishing them to my own nix channel.  After publishing
them, anyone can depend on them from other packages based on the same build
script system.

Has anyone done something like this or have ideas if this could be done?

*long version:*

I'm a graduate student, and write lots of code that I'd love to share with
the world.  I'm learning the hard way that publishing source is easy for
the developer, but hard for potential users while publishing (a matrix) of
binary versions makes it easy for potential users but really hard for the
developer.  I started packaging my code with zeroinstall<http://0install.net/>,
but quickly found that binary portability is hard to pull off and package
dependency resolution based on ad-hoc version numbers is not good enough to
reliably build software from source.  I read the nix papers and
documentation and was very excited about the generality of this approach.
I would love to figure out if nix can be part of a cross-language
cross-platform workflow that eliminates the dependency hell problem.

Cheers,
Kyle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20130815/0c46ee6c/attachment.html