[Nix-commits] [NixOS/nixpkgs] eec577: steam: move libpciaccess as non-runtime dependenci...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: eec5775a4cbe8fec60eb7991129e1f1ae048222f https://github.com/NixOS/nixpkgs/commit/eec5775a4cbe8fec60eb7991129e1f1ae048222f Author: Philipp Steinpass <phil...@xndr.de> Date: 2017-04-11 (Tue, 11 Apr 2017) Changed paths: M pkgs/games/steam/chrootenv.nix M pkgs/games/steam/runtime-wrapped.nix Log Message: --- steam: move libpciaccess as non-runtime dependencies ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 01e5b8: dehydrated: 0.3.1 -> 0.4.0 (#22804)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 01e5b8527dacfb61319dcdc2178ec6aed7f7f3c5 https://github.com/NixOS/nixpkgs/commit/01e5b8527dacfb61319dcdc2178ec6aed7f7f3c5 Author: Philipp <phil...@xndr.de> Date: 2017-02-15 (Wed, 15 Feb 2017) Changed paths: M pkgs/tools/admin/dehydrated/default.nix Log Message: --- dehydrated: 0.3.1 -> 0.4.0 (#22804) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 8f6f46: nginx service: Add missing port toString conversio...
Branch: refs/heads/release-16.09 Home: https://github.com/NixOS/nixpkgs Commit: 8f6f46e8e1c9d1524bee2807ed7dffc18c8b835f https://github.com/NixOS/nixpkgs/commit/8f6f46e8e1c9d1524bee2807ed7dffc18c8b835f Author: Philipp Hausmann <phile...@users.noreply.github.com> Date: 2016-11-22 (Tue, 22 Nov 2016) Changed paths: M nixos/modules/services/web-servers/nginx/default.nix Log Message: --- nginx service: Add missing port toString conversion (#20252) (cherry picked from commit 632282300a9ecbdd8506554aa04c516c64994c84) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 632282: nginx service: Add missing port toString conversio...
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 632282300a9ecbdd8506554aa04c516c64994c84 https://github.com/NixOS/nixpkgs/commit/632282300a9ecbdd8506554aa04c516c64994c84 Author: Philipp Hausmann <phile...@users.noreply.github.com> Date: 2016-11-08 (Tue, 08 Nov 2016) Changed paths: M nixos/modules/services/web-servers/nginx/default.nix Log Message: --- nginx service: Add missing port toString conversion (#20252) ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-commits] [NixOS/nixpkgs] 5c3a6d: Added package for dehydrated. (#19651)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 5c3a6d6802548418539c912a27323d795f33efb0 https://github.com/NixOS/nixpkgs/commit/5c3a6d6802548418539c912a27323d795f33efb0 Author: Philipp <phil...@xndr.de> Date: 2016-10-20 (Thu, 20 Oct 2016) Changed paths: M lib/maintainers.nix A pkgs/tools/admin/dehydrated/default.nix M pkgs/top-level/all-packages.nix Log Message: --- Added package for dehydrated. (#19651) * Added package for dehydrated. ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
[Nix-dev] Hydra Github Status Plugin
Hi, I am using Hydra for CI and I am loving it so far. However, it would be really nice to show the build status on Github. I see that there is a GithubStatus plugin in the Hydra source code, but I couldn't find any examples or documentation on how to use it. Is anybody using the GithubStatus plugin and could give me a hint? How do I configure the plugin? Cheers, Philipp ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] nix-shell and persistent environment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Sep 30, 2016 at 10:30:27AM -0300, Ruben Astudillo wrote:
> hi
>
> nix-shell is great, but when I update the nixpkgs or nix-collect-garbage
> I lose the cache of those packages. I've thinking on do a special profile
> that I could switch to per shell instance with nix-{shell,env}, but I
> also found references to a deprecated buildEnv function for this. What is
> the common alternative for this?
>
The old wiki has a guide for that.
https://nixos.org/wiki/Development_Environments#Making_a_Persistent_nix-shell_Environment
Philipp
-BEGIN PGP SIGNATURE-
iQGcBAEBCAAGBQJX7mwsAAoJENe9N53GUHbvaK4L/An67zN4X+rIdvSGGe014KcR
ImGU4CNKE7QQectbpwXrXZaoWmD4vQHCDCTo/YchdANZmUvhvNUYAg2mjYsGlmyu
pFont8PwT0QuObp1ngPjBb6/fFGEnqQV1gLvxvuv92THTe2pWYN2guC15c4DR/Oc
EVvs9wr1BlMAUwTU3K0eD8/4ZGuMVZgI4TycGg3lnCp2JGziftXmrW7kluXglqKl
e5CpiqLufPmUwd7VAPsYDEZsZ2+/1uWwZ8SsZHI9bfGxgWnUp0Yxp5cL6vm4Xu88
cjYWhzVVPwImQfxq/scR5Xs4NR44tBiveG6Zt+H3qrzynisza6A/Kz2RyIs++OML
pfMWSX58YvaICV/uOvzCQIjsHGLlEChdijrJUNbYMXQIIZyrJPFlHR8//Hsy//lG
9Z+MGpYdQtJvN3IXN2vVqITWY9OBOA02re1LQHlaA82o32tPO9vTJ99c/b7QVgPm
m4l+6rfQEIL+1mG56Et5ftixpAY4XxlLQ2Queq41Wg==
=sE0b
-END PGP SIGNATURE-
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Using Nix as the preferred package manager for a new language
Interestingly enough, we have some of the same questions for the Agda programming language. Currently, Agda doesn't really have any package manager, so there are no backwards-compatibility problems with using Nix. It would be really nice if we could use Nix as the one-and-only package management solution for Agda. However, Nix doesn't support Windows, which means we need a second fallback solution. This is rather unpleasant, but not a show stopper. For Agda, I'm currently leaning towards defining a simple package json format and a very basic build tool and to build Nix support on top of that. Kind of like the Haskell packages. I'm certainly interested in how you're solving this problems and I will keep an eye on it, maybe I can steal some of your work and use it for Agda ;-) Cheers, Philipp > Hi! I've tried to start this discussion a couple times on IRC, but it > hasn't really gotten attention, so: > > I'm one of the developers of Monte, a new programming language. We don't > want to write a package manager, because package managers are hard. (Also > we've been watching npm happen for the past few years.) So we plan to use > Nix. However, we've got some requirements for our package layout, and we > haven't seen anybody else do all of the things we want at once. Here's > what we're thinking: > > * Monte packages shouldn't live in nixpkgs. We use standalone Nix > expressions to build stuff like our runtime, and it makes development very > speedy since we do not have to round-trip our Nix changes through nixpkgs. > We also want to keep Nix expressions for packages close to the packages > themselves (see next point.) Perhaps when our ecosystem has developed > more, we can revisit this. > > * Monte packages should bundle their own Nix expressions. Our reasoning is: > > ** Suppose that we have some "mtpkgs" tree, which is like nixpkgs but only > contains a Nix expression for building some or all of the Monte runtime > and packages. However, now we've decoupled the description of the packages > from the packages themselves, which makes maintaining the package harder, > since changes to the package require a corresponding change to mtpkgs. We > didn't gain anything over just using nixpkgs! > > ** Okay, so instead we make a JSON (or whatever) description of each > package, and ship that with the package. Then, we interpret that > description as a Nix expression, and do Nix things as usual. Except that > this doesn't work, because now the JSON description is a new package > manager format! We didn't want that. > > ** So it seems like packages should ship with a Nix expression. > > * Packages should be easy to cargo-cult. This might sound weird, but my > experience in other ecosystems (especially Python and Perl) has taught me > that most package descriptions are cargo-culted from other similar > packages. We should have a very custom Nix derivation-producing function > which turns a minimal Nix expression into a full Monte package > description. > > So with that in mind, here's where we currently are. We have a runtime and > some packages. There's a terrible terrible Nix function that generates > derivations ( > https://github.com/monte-language/typhon/blob/master/default.nix#L11-L34 > ). An example usage is ( > https://github.com/monte-language/mt-rational/blob/master/default.nix ). > > As you can see, our derivations are not especially good. We don't have a > good way to locate a runtime so that we can call ``montePackage`` easily. > Once our packages start depending on other Monte packages, the problem > will only be worse. We also have this indirect dependency on nixpkgs for > library stuff, which is worse than a direct dependency or no dependency at > all. > > We're seeking any advice on how to make this situation better. As far as > we can tell, nobody else has tried to make Nix their first-class preferred > package management solution for their language, so we are blazing trails > here. > > Thanks! > ~ C. signature.asc Description: OpenPGP digital signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
