[Nix-dev] Dashes in haskell-packages
Hello. There is a convention to convert haskell packages names to camelCase when they contain dashes. But Nix now can dashes. So what convention should I use when submitting new haskell packages to `nixpkgs`? ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Dashes in haskell-packages
On 10/08/2013 11:24 AM, Daniel Hlynskyi wrote: Hello. There is a convention to convert haskell packages names to camelCase when they contain dashes. But Nix now can dashes. So what convention should I use when submitting new haskell packages to `nixpkgs`? The nixpkgs manual says: Dashes in the package name should be changed to underscores in variable names, rather than to camel case — e.g., module_init_tools instead of moduleInitTools. http://nixos.org/nixpkgs/manual/#idp365984 I guess this is still true, even if nix can handle dashes now. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Dashes in haskell-packages
On 10/08/2013 10:37 AM, Pascal Wittmann wrote: On 10/08/2013 11:24 AM, Daniel Hlynskyi wrote: Hello. There is a convention to convert haskell packages names to camelCase when they contain dashes. But Nix now can dashes. So what convention should I use when submitting new haskell packages to `nixpkgs`? The nixpkgs manual says: Dashes in the package name should be changed to underscores in variable names, rather than to camel case — e.g., module_init_tools instead of moduleInitTools. http://nixos.org/nixpkgs/manual/#idp365984 That might be the case for nixpkgs in general, but it's not the case for Haskell packaging. Daniel, I would suggest carrying on with camelCase for Haskell packages for consistency. If we want to use dash naming and be equivalent to Hackage, then I think this should be done in a single commit. - ocharles 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
Re: [Nix-dev] Dashes in haskell-packages
Hi, On 08/10/13 11:37, Pascal Wittmann wrote: On 10/08/2013 11:24 AM, Daniel Hlynskyi wrote: Hello. There is a convention to convert haskell packages names to camelCase when they contain dashes. But Nix now can dashes. So what convention should I use when submitting new haskell packages to `nixpkgs`? The nixpkgs manual says: Dashes in the package name should be changed to underscores in variable names, rather than to camel case — e.g., module_init_tools instead of moduleInitTools. http://nixos.org/nixpkgs/manual/#idp365984 This is outdated, I'll fix it. In fact, you should use dashes for new packages so that the attribute name matches the package name (e.g. module-init-tools). -- Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Dashes in haskell-packages
Oliver Charles writes: I would suggest carrying on with camelCase for Haskell packages for consistency. If we want to use dash naming and be equivalent to Hackage, then I think this should be done in a single commit. yes, exactly. When cabal2nix generates the 'buildDepends' field for a package, it assumes that the camelCase naming style is used, so it's important that all Haskell packages follow that convention for the time being. We can convert the entire haskell-packages.nix set to the new dashy style in one commit later (and I probably will in the foreseeable future). Take care, Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Dashes in haskell-packages
That would be great! Ok, I'll be using camelCase. Thanks all! 2013/10/8 Peter Simons sim...@cryp.to Oliver Charles writes: I would suggest carrying on with camelCase for Haskell packages for consistency. If we want to use dash naming and be equivalent to Hackage, then I think this should be done in a single commit. yes, exactly. When cabal2nix generates the 'buildDepends' field for a package, it assumes that the camelCase naming style is used, so it's important that all Haskell packages follow that convention for the time being. We can convert the entire haskell-packages.nix set to the new dashy style in one commit later (and I probably will in the foreseeable future). Take care, Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Mesa-9.2
On 10/02/2013 07:13 PM, Baptist BENOIST wrote: As I have finished my Qt 5.1.1 packaging, I will make a pull request on nixpkgs containing the fix (on the current mesa version used, not the latest) soon. I am also planning to push the fix upstream ;-) Due to another demand (from Carles Pagès page.li...@gmail.com) I added the GLES support by default, as the libs are really tiny. Just notifying, in case it's useful for Qt5 as well after all. Currently it's just in [my nixpkgs] repo, because I don't want to make Hydra an almost-full rebuild for every small change. [my nixpkgs] https://github.com/vcunat/nixpkgs/commits/x-updates Vlada smime.p7s Description: S/MIME Cryptographic Signature ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
