[prev in list] [next in list] [prev in thread] [next in thread]
List: nix-dev
Subject: Re: [Nix-dev] Fwd: Re: Displaying package parameters
From: Jonn Mostovoy <jm () memorici ! de>
Date: 2016-02-29 10:24:32
Message-ID: CANZXW7+Ueqsvo1YwkRrrwhnuKW9yQoeAn+sNGUecjq9tOoSK9w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Wow, very nice!
Maybe people reporting that it doesn't work weren't patient enough to wait
for it to load the entirety of packages ;)
Regarding feature wishlist — this is good enough for package exploration,
I'm not sure that for developers using this during expression development
anything but a link to the expression (which you already have) is required.
—
Kindest regards,
¬Î£
On Mon, Feb 29, 2016 at 5:27 AM, Fabian Schmitthenner <
nix-dev@schmitthenner.eu> wrote:
> huh? what's the problem?
>
> To be clear, when clicking on a package, some parameters will be shown,
> e. g. asciidoc, qtbase.base have quite some parameters.
> For some packages, "error" "some error happened" is displayed, that
> means that the parameters couldn't be determined because callPackage
> wasn't used in the normal way. Also, currently packages that don't
> succeed are currently shown and the error is displayed in the long
> description.
>
> On 02/29/2016 04:14 AM, Roger Qiu wrote:
>> Demo doesn't seem to be working atm.
>>
>> On 29/02/2016 2:59 PM, Fabian Schmitthenner wrote:
>>> Hi!
>>>
>>> I just wanted to share that I tried displaying package parameters on the
>>> nixos homepage and the current result can be seen here:
>>> http://schmitthenner.eu/nixos-homepage/nixos/packages.html.
>>>
>>> When you click on a package, you hopefully see its parameter. This uses
>>> a heruristic to try to figure out which parameters are packages (and
>>> thus not displayed) and which are not (and thus displayed) that goes
>>> roughly as follows:
>>>
>>> - If the parameter is instantiated - either implicitly or explicitly -
>>> by callPackage, we look at the value and if it's a derivation, or a list
>>> or attrset set of derivations, or a function it's not displayed
>>> - Otherwise, it's displayed
>>>
>>> I think there was a discussion about this a short while ago, but I
>>> couldn't find it.
>>>
>>> Please let me know what you think and if we might want a (more elaborate
>>> version, e. g. also displaying the value of default arguments that
>>> aren't changed by callPackage, which requires an other change to nix
>>> because this info is currently not available, we only know if the
>>> argument is optional or not afaik) of this on our official website.
>>>
>>> Source code can be found on
>>> https://github.com/NixOS/nixos-homepage/compare/master...fkz:master
>>> Technically, I patched nixpkgs customization, so we not only get the
>>> override... functions, but also the original parameters and the original
>>> function.
>>> Furthermore, this uses a patched version of nix which allows catching
>>> errors inside nix (added a primop __catch) that also seems useful more
>>> generally (when polished) (see
>>> https://github.com/fkz/nix/tree/catch-throw).
>>>
>>> Fabian
>>> _______________________________________________
>>> 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
[Attachment #5 (text/html)]
<p dir="ltr">Wow, very nice!<br>
Maybe people reporting that it doesn't work weren't patient enough to wait \
for it to load the entirety of packages ;)</p> <p dir="ltr">Regarding feature \
wishlist — this is good enough for package exploration, I'm not sure that for \
developers using this during expression development anything but a link to the \
expression (which you already have) is required.<br> —<br>
Kindest regards,<br>
¬Î£<br></p>
<p dir="ltr">On Mon, Feb 29, 2016 at 5:27 AM, Fabian Schmitthenner <<a \
href="mailto:nix-dev@schmitthenner.eu">nix-dev@schmitthenner.eu</a>> wrote:<br> \
> huh? what's the problem?<br> ><br>
> To be clear, when clicking on a package, some parameters will be shown,<br>
> e. g. asciidoc, qtbase.base have quite some parameters.<br>
> For some packages, "error" "some error happened" is \
displayed, that<br> > means that the parameters couldn't be determined because \
callPackage<br> > wasn't used in the normal way. Also, currently packages that \
don't<br> > succeed are currently shown and the error is displayed in the \
long<br> > description.<br>
><br>
> On 02/29/2016 04:14 AM, Roger Qiu wrote:<br>
>> Demo doesn't seem to be working atm.<br>
>><br>
>> On 29/02/2016 2:59 PM, Fabian Schmitthenner wrote:<br>
>>> Hi!<br>
>>><br>
>>> I just wanted to share that I tried displaying package parameters on \
the<br> >>> nixos homepage and the current result can be seen here:<br>
>>> <a href="http://schmitthenner.eu/nixos-homepage/nixos/packages.html">http://schmitthenner.eu/nixos-homepage/nixos/packages.html</a>.<br>
>>><br>
>>> When you click on a package, you hopefully see its parameter. This \
uses<br> >>> a heruristic to try to figure out which parameters are packages \
(and<br> >>> thus not displayed) and which are not (and thus displayed) that \
goes<br> >>> roughly as follows:<br>
>>><br>
>>> - If the parameter is instantiated - either implicitly or explicitly \
-<br> >>> by callPackage, we look at the value and if it's a derivation, \
or a list<br> >>> or attrset set of derivations, or a function it's not \
displayed<br> >>> - Otherwise, it's displayed<br>
>>><br>
>>> I think there was a discussion about this a short while ago, but I<br>
>>> couldn't find it.<br>
>>><br>
>>> Please let me know what you think and if we might want a (more \
elaborate<br> >>> version, e. g. also displaying the value of default \
arguments that<br> >>> aren't changed by callPackage, which requires an \
other change to nix<br> >>> because this info is currently not available, we \
only know if the<br> >>> argument is optional or not afaik) of this on our \
official website.<br> >>><br>
>>> Source code can be found on<br>
>>> <a href="https://github.com/NixOS/nixos-homepage/compare/master...fkz:master">https://github.com/NixOS/nixos-homepage/compare/master...fkz:master</a><br>
>>> Technically, I patched nixpkgs customization, so we not only get \
the<br> >>> override... functions, but also the original parameters and the \
original<br> >>> function.<br>
>>> Furthermore, this uses a patched version of nix which allows \
catching<br> >>> errors inside nix (added a primop __catch) that also seems \
useful more<br> >>> generally (when polished) (see<br>
>>> <a href="https://github.com/fkz/nix/tree/catch-throw">https://github.com/fkz/nix/tree/catch-throw</a>).<br>
>>><br>
>>> Fabian<br>
>>> _______________________________________________<br>
>>> nix-dev mailing list<br>
>>> <a href="mailto:nix-dev@lists.science.uu.nl">nix-dev@lists.science.uu.nl</a><br>
>>> <a href="http://lists.science.uu.nl/mailman/listinfo/nix-dev">http://lists.science.uu.nl/mailman/listinfo/nix-dev</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> nix-dev mailing list<br>
> <a href="mailto:nix-dev@lists.science.uu.nl">nix-dev@lists.science.uu.nl</a><br>
> <a href="http://lists.science.uu.nl/mailman/listinfo/nix-dev">http://lists.science.uu.nl/mailman/listinfo/nix-dev</a><br>
</p>
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic