[Nix-dev] Generating desktop files

[Sander van der Burg - EWI]

It could also be possible that we have to generate multiple .desktop files for a single package. How do we cope with this?

Another issue is that some properties in a .desktop file are compulsary to specify, such as the name and a path to an executable. I tried to capture these constraints in a Nix expression.

-----Oorspronkelijk bericht-----
Van: nix-dev-bounces at cs.uu.nl namens Eelco Dolstra
Verzonden: di 12-5-2009 12:43
Aan: Nicolas Pierron
CC: nix-dev at cs.uu.nl; Sander van der Burg - EWI
Onderwerp: Re: [Nix-dev] Generating desktop files
 
Hi,

Nicolas Pierron wrote:

> On Tue, May 12, 2009 at 09:48, Eelco Dolstra <e.dolstra at tudelft.nl> wrote:
>> Sander van der Burg - EWI wrote:
>>
>>> I just created a makeDesktopItem function in Nixpkgs, which you can use
>>> to generate .desktop files for applications that do not include .desktop
>>> files in their tarballs, such as Mozilla Firefox.
>> Maybe it would be nice to have this as a shell function that can be called from
>> postInstall hooks.  That way we wouldn't have to create a wrapper package for
>> everything.
> 
> Adding a function inside setup.sh implies that you will have to
> recompile every package each time you add a support to a new standard.

I wasn't proposing adding it to setup.sh.  Using makeSetupHook you can just add
extensions in buildInputs - see makeWrapper as an example.

> stdenv.mkDerivation {
>   name = "foo-1.2.3";
> 
>   extraSetup = mkDesktopItem;

This is basically what makeSetupHook accomplishes.  It creates a trivial package
containing a setup-hook.sh which gets sourced by setup.sh.

-- 
Eelco Dolstra | http://www.st.ewi.tudelft.nl/~dolstra/
_______________________________________________
nix-dev mailing list
nix-dev at cs.uu.nl
https://mail.cs.uu.nl/mailman/listinfo/nix-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20090512/403f0e92/attachment.html