Hello, I'm trying to theme mouse cursor globally so that it's consistent across lightdm, xmonad, applications. I'm looking for the equivalent of creating a /usr/share/icons/default/index.theme file with an Inherits line to my cursor theme of choice. But I'm still a bit new to NixOS and not sure how to get that to work in /run/current-system/sw/share/icons? Someone mentioned the need to write a derivation to modify that directory.
Any help would be very much appreciated. Thank you, Austin Erlandson > On Feb 8, 2017, at 05:00, nix-dev-requ...@lists.science.uu.nl wrote: > > Send nix-dev mailing list submissions to > nix-dev@lists.science.uu.nl > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.science.uu.nl/mailman/listinfo/nix-dev > or, via email, send a message with subject or body 'help' to > nix-dev-requ...@lists.science.uu.nl > > You can reach the person managing the list at > nix-dev-ow...@lists.science.uu.nl > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of nix-dev digest..." > > > Today's Topics: > > 1. Re: nix-bundle: Bundle Nix derivations to run anywhere > (Arnold Krille) > 2. Re: nix-bundle: Bundle Nix derivations to run anywhere (Roger Qiu) > 3. Re: -realise: mounting /proc: Operation not permitted > (Nikolay Amiantov) > 4. Re: where is grep? (Azul) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 7 Feb 2017 21:45:41 +0100 > From: Arnold Krille <arn...@arnoldarts.de> > To: nix-dev@lists.science.uu.nl > Subject: Re: [Nix-dev] nix-bundle: Bundle Nix derivations to run > anywhere > Message-ID: <20170207214541.650eb...@xingu.arnoldarts.de> > Content-Type: text/plain; charset="us-ascii" > > On Mon, 6 Feb 2017 18:33:19 -0600 Matthew Bauer <mjbaue...@gmail.com> > wrote: >> GitHub page: https://github.com/matthewbauer/nix-bundle >> > > Send nix-dev mailing list submissions to > nix-dev@lists.science.uu.nl > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.science.uu.nl/mailman/listinfo/nix-dev > or, via email, send a message with subject or body 'help' to > nix-dev-requ...@lists.science.uu.nl > > You can reach the person managing the list at > nix-dev-ow...@lists.science.uu.nl > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of nix-dev digest..." > > > Today's Topics: > > 1. Re: nix-bundle: Bundle Nix derivations to run anywhere > (Arnold Krille) > 2. Re: nix-bundle: Bundle Nix derivations to run anywhere (Roger Qiu) > 3. Re: -realise: mounting /proc: Operation not permitted > (Nikolay Amiantov) > 4. Re: where is grep? (Azul) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 7 Feb 2017 21:45:41 +0100 > From: Arnold Krille <arn...@arnoldarts.de> > To: nix-dev@lists.science.uu.nl > Subject: Re: [Nix-dev] nix-bundle: Bundle Nix derivations to run > anywhere > Message-ID: <20170207214541.650eb...@xingu.arnoldarts.de> > Content-Type: text/plain; charset="us-ascii" > > On Mon, 6 Feb 2017 18:33:19 -0600 Matthew Bauer <mjbaue...@gmail.com> > wrote: >> GitHub page: https://github.com/matthewbauer/nix-bundle >> >> I just wanted to post about a little project I've been working on. I'm >> calling it "nix-bundle". >> >> Basically, what it does is: take a Nix closure, compress it into a >> tarball, and turn that tarball into an executable using "Arx". The >> final result looks like a plain shell script, but actually has a >> tarball closure appended to it. When you run that script, Arx will >> execute "nix-user-chroot" (which is included in the closure) which >> will setup a /nix/ directory, then execute a target executable. All of >> this should work "out of the box" for any Nix derivation folder with a >> valid executable. >> >> For example, to generate a "hello" bundle: >> >> ./nix-bundle.sh hello /bin/hello >> >> "hello" specifies pkgs.hello and /bin/hello specifies the file >> ${pkgs.helloi}/bin/hello to be executed. The output file will just be >> called "hello". >> >> The result is a "bundle" that can run without Nix being installed! No >> external dependencies are needed because they are all contained within >> the Nix closure. > > So instead of pushing docker images around to bring an app into > non-nix-production, we can just push around a tar'ed nix tree? Nice. > > - Arnold > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 230 bytes > Desc: not available > URL: > <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20170207/2321a350/attachment-0001.sig> > > ------------------------------ > > Message: 2 > Date: Wed, 8 Feb 2017 08:37:15 +1100 > From: Roger Qiu <roger....@matrix.ai> > To: Arnold Krille <arn...@arnoldarts.de> > Cc: Nix Dev <nix-dev@lists.science.uu.nl> > Subject: Re: [Nix-dev] nix-bundle: Bundle Nix derivations to run > anywhere > Message-ID: > <CA+HLvX=ggzutaxh+h+qjpq7l2tjxuf49nqzqwlnfidjf0fw...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > When I exported a docker image to take look at what it is, it was also just > a compressed set of tar'ed file trees. > On 08/02/2017 7:46 AM, "Arnold Krille" <arn...@arnoldarts.de> wrote: > >> On Mon, 6 Feb 2017 18:33:19 -0600 Matthew Bauer <mjbaue...@gmail.com> >> wrote: >>> GitHub page: https://github.com/matthewbauer/nix-bundle >>> >>> I just wanted to post about a little project I've been working on. I'm >>> calling it "nix-bundle". >>> >>> Basically, what it does is: take a Nix closure, compress it into a >>> tarball, and turn that tarball into an executable using "Arx". The >>> final result looks like a plain shell script, but actually has a >>> tarball closure appended to it. When you run that script, Arx will >>> execute "nix-user-chroot" (which is included in the closure) which >>> will setup a /nix/ directory, then execute a target executable. All of >>> this should work "out of the box" for any Nix derivation folder with a >>> valid executable. >>> >>> For example, to generate a "hello" bundle: >>> >>> ./nix-bundle.sh hello /bin/hello >>> >>> "hello" specifies pkgs.hello and /bin/hello specifies the file >>> ${pkgs.helloi}/bin/hello to be executed. The output file will just be >>> called "hello". >>> >>> The result is a "bundle" that can run without Nix being installed! No >>> external dependencies are needed because they are all contained within >>> the Nix closure. >> >> So instead of pushing docker images around to bring an app into >> non-nix-production, we can just push around a tar'ed nix tree? Nice. >> >> - Arnold >> >> _______________________________________________ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> http://lists.science.uu.nl/mailman/listinfo/nix-dev >> >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20170208/d91eb8f9/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Wed, 8 Feb 2017 00:41:46 +0300 > From: Nikolay Amiantov <a...@fmap.me> > To: Marc Weber <marco-owe...@gmx.de>, nix-...@cs.uu.nl > Subject: Re: [Nix-dev] -realise: mounting /proc: Operation not > permitted > Message-ID: <4eb360c0-e8a9-138f-74ed-32d1a9a10...@fmap.me> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi, > >> On 02/07/2017 02:04 PM, Marc Weber wrote: >> What might be causing this? >> >> Nix-daemon nix version is the same which gets activated by the command >> below: >> >> >> /nix/store/jsfa19hfkrpg39njl7msrnsgfaxjvi3c-nix-1.12pre4997_1351b0d/bin/nix-store >> --realise >> /nix/store/kbw4v0hm7srarljkf5idk7ahspd59lp9-system-path.drv/nix/store/kbw4v0hm7srarljkf5idk7ahspd59lp9-system-path.drv >> >> these derivations will be built: >> >> /nix/store/pq24b3zvyx2fdajsy530vma0n3fgbiv1-NVIDIA-Linux-x86_64-375.26.run.drv >> /nix/store/msddw7c9wnjjmzwg8j9fmcm5gpgp2sgz-nvidia-x11-375.26-4.9.8.drv >> /nix/store/kbw4v0hm7srarljkf5idk7ahspd59lp9-system-path.drv >> building path(s) >> ?/nix/store/r3219a23idwsvx8dw6zln2mlg34m0jdm-NVIDIA-Linux-x86_64-375.26.run? >> error: while setting up the build environment: mounting /proc: Operation not >> permitted > > It may be caused by https://github.com/NixOS/nix/issues/1112. For > example, I have: > > error: while setting up the build environment: unable to make filesystem > ?/run/user/1000/gvfs? private: Permission denied > > These are not completely same errors though, so not sure. I workaround > it by unmounting this filesystem, but obviously it's a bad idea to do > this with `/proc`... > >> >> Marc Weber >> _______________________________________________ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> http://lists.science.uu.nl/mailman/listinfo/nix-dev > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20170208/6f9f05db/attachment-0001.html> > > ------------------------------ > > Message: 4 > Date: Wed, 8 Feb 2017 10:42:56 +0000 > From: Azul <m...@azulinho.com> > To: Profpatsch <m...@profpatsch.de> > Cc: nix-dev <nix-dev@lists.science.uu.nl> > Subject: Re: [Nix-dev] where is grep? > Message-ID: > <CAMP=owiaeekse6cafwgbrsvh5n7nxipt8j+z6q4k0psiuc7...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I just understood where it all went wrong: > > azul ? /safe/home-azul ? 130 ? killall ssh > The program ?killall? is currently not installed. It is provided by > several packages. You can install it by typing one of the following: > nix-env -iA nixos.busybox > nix-env -iA nixos.psmisc > > > >> On 15 November 2016 at 13:18, Profpatsch <m...@profpatsch.de> wrote: >> >>> On 16-11-15 11:14am, Azul wrote: >>> "If you put busybox into your systemPackages, it will likely shadow many >>> other utilities" <-- kaboom, zing, slash, boooOOOmmm >>> >>> killed, gone >> >> There?s also a pretty long list of default packages >> which afaik cannot be shadowed by other >> environment.systemPackages entries: >> https://github.com/NixOS/nixpkgs/blob/master/nixos/ >> modules/config/system-path.nix#L10 >> >> >> -- >> Proudly written in Mutt with Vim on NixOS. >> Q: Why is this email five sentences or less? >> A: http://five.sentenc.es >> May take up to five days to read your message. If it?s urgent, call me. >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20170208/c4d4ed28/attachment-0001.html> > > ------------------------------ > > _______________________________________________ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > > > End of nix-dev Digest, Vol 140, Issue 20 > **************************************** > _______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
