Hi,
On 23/06/12 18:13, Antono Vasiljev wrote:
Also, i know that nix is young and multipage policies will be overkill,
but something like README.md in pkgs/data/fonts/ and other dirs could
work.
What do you think?
Documentation is very welcome, and your draft looks great to me. However,
Hi,
On 24/06/12 11:53, Marc Weber wrote:
for nixpkggs the attr path is also very important.
Why? Unless you frequently want to pass all fonts around (like you might pass
xorg as an input), grouping things into a set is not particularly useful.
--
Eelco Dolstra | LogicBlox, Inc. |
Hi,
On 24/06/12 11:10, Kirill Elagin wrote:
Shouldn't we introduce a separate attrset to hold fonts instead of putting
them
into top-level?
Ok, guys, let's be honest. Nix needs something like categories.
Maybe we're talking about different things, but the categories I know from other
Excerpts from Eelco Dolstra's message of Mon Jun 25 17:31:47 +0200 2012:
Why? Unless you frequently want to pass all fonts around (like you might pass
xorg as an input), grouping things into a set is not particularly useful.
Why? Because you can do something like install all fonts by getting
Also, i know that nix is young and multipage policies will be overkill,
but something like README.md in pkgs/data/fonts/ and other dirs could
work.
What do you think?
Shea Levy s...@shealevy.com writes:
I think these are good ideas. More structure and policy in nixpkgs
would probably
On Jun 24, 2012, at 9:18 AM, Antono Vasiljev s...@antono.info wrote:
I created initial draft (really small) for fonts:
https://github.com/antono/nixpkgs/tree/fonts-policy-proposal/pkgs/data/fonts#font-packaging
What do you think? :)
+1 from me.
On Sun, 24 Jun 2012 16:18:08 +0300, Antono Vasiljev s...@antono.info wrote:
Shea Levy s...@shealevy.com writes:
I think these are good ideas. More structure and policy in nixpkgs
would probably be helpful especially to new contributors. The big
question is: Who will do the initial work?
Shouldn't we introduce a separate attrset to hold fonts instead of putting
them into top-level?
Ok, guys, let's be honest. Nix needs something like categories. And, no,
suffixes in package names are not a good solution. And, by the way, nested
attrsets won't work either, because, as I know, after
for nixpkggs the attr path is also very important.
What about also moving everything into
fonts.* attr path?
Same as xserver python-packages etc.
Marc Weber
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
On Sun, 24 Jun 2012 17:53:58 +0200, Marc Weber marco-owe...@gmx.de wrote:
for nixpkggs the attr path is also very important.
What about also moving everything into
fonts.* attr path?
+1
--
Florian Friesdorf f...@chaoflow.net
GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
Ok, guys, let's be honest. Nix needs something like categories.
What if you have a python library which is also a compiler?
Put into category compilers or python-library?
Thus do you want to assign multiple categories to a package?
suffixes in package names are not a good solution.
Depends on
2012/6/24 Marc Weber marco-owe...@gmx.de
Ok, guys, let's be honest. Nix needs something like categories.
What if you have a python library which is also a compiler?
Put into category compilers or python-library?
Well, yeah, this might be a problem, but other package managers solve this
Hi Kirill,
On Sun, 24 Jun 2012 23:32:03 +0400, Kirill Elagin kirela...@gmail.com wrote:
2012/6/24 Marc Weber marco-owe...@gmx.de
Ok, guys, let's be honest. Nix needs something like categories.
What if you have a python library which is also a compiler?
Put into category compilers or
Hello, Guys!
It's my first post here and i'm totally newbie in nix. Currently i use
nix on Ubuntu. I submited my first nix pkg yesterday and it was accepted
:) https://github.com/NixOS/nixpkgs/pull/19
I would like to write small Google Web Fonts[1] importer for NixOs (+500
free ttf fonts).
Hi Antono,
I think these are good ideas. More structure and policy in nixpkgs would
probably be helpful especially to new contributors. The big question is: Who
will do the initial work? Of course suggestions are always welcome, but if you
could put together an actual policy doc and a pull
15 matches
Mail list logo
